The kernel calls deny_write_access() to prevent a file already opened
for write from being executed and also prevents files being executed
from being opened for write. For some reason this does not extend to
files being mmap'ed execute.
This patch prevents allowing a file in policy, already
Igor Zhbanov's "Should mprotect(..., PROT_EXEC) be checked by IMA?"
thread raised concerns about IMA's handling of mmap/mprotect. [1] The
kernel calls deny_write_access() to prevent a file already opened for
write from being executed and also prevents files being executed from
being opened for
The most obvious syscall to add support for the new LOOKUP_* scoping
flags would be openat(2) (along with the required execveat(2) change
included in this series). However, there are a few reasons to not do
this:
* The new LOOKUP_* flags are intended to be security features, and
openat(2)
Previously, path_init's handling of *at(dfd, ...) was only done once,
but with O_BENEATH (and O_THISROOT) we have to parse the initial
nd->path at different times (before or after absolute path handling)
depending on whether we have been asked to scope resolution within a
root.
Signed-off-by:
On 05/03, Peter Zijlstra wrote:
>
> -static void lockdep_sb_freeze_release(struct super_block *sb)
> -{
> - int level;
> -
> - for (level = SB_FREEZE_LEVELS - 1; level >= 0; level--)
> - percpu_rwsem_release(sb->s_writers.rw_sem + level, 0,
> _THIS_IP_);
> -}
> -
> -/*
> - *
On Fri, May 03, 2019 at 01:13:44PM -0400, Alan Stern wrote:
> The description of smp_mb__before_atomic() and smp_mb__after_atomic()
> in Documentation/atomic_t.txt is slightly terse and misleading. It
> does not clearly state which other instructions are ordered by these
> barriers.
>
> This
Thanks for the quick feedback Greg!
+static const struct attribute_group sdw_master_node_group = {
+ .attrs = master_node_attrs,
+};
+
+static const struct attribute_group *sdw_master_node_groups[] = {
+ _master_node_group,
+ NULL
+};
Minor nit, you can use the
On Mon, May 06, 2019 at 05:57:52AM -0700, Christoph Hellwig wrote:
> > However, similar to the (1), when the driver will support the devices with
> > hardware based passthrough, it will have to dedicate a bunch of queues to
> > the
> > guest, configure them with the appropriate PASID, and then
On 5/6/19 11:22 AM, Vinod Koul wrote:
On 06-05-19, 17:19, Greg KH wrote:
On Mon, May 06, 2019 at 09:42:35AM -0500, Pierre-Louis Bossart wrote:
+
+int sdw_sysfs_slave_init(struct sdw_slave *slave)
+{
+ struct sdw_slave_sysfs *sysfs;
+ unsigned int src_dpns, sink_dpns, i, j;
+
On Mon, May 06, 2019 at 05:46:56PM +0200, Esben Haabendal wrote:
> Andy Shevchenko writes:
> >> > On Wed, May 01, 2019 at 09:17:37AM +0200, Esben Haabendal wrote:
> >> >> Andy Shevchenko writes:
> As an example, the sm501.c driver, the only driver in drivers/mfd/ which
> uses serial8250 driver,
On 06-05-19, 09:48, Pierre-Louis Bossart wrote:
> > > +struct dentry *sdw_bus_debugfs_get_root(struct sdw_bus_debugfs *d)
> > > +{
> > > + if (d)
> > > + return d->fs;
> > > + return NULL;
> > > +}
> > > +EXPORT_SYMBOL(sdw_bus_debugfs_get_root);
> >
> > _GPL()?
>
> Oops, that's a big
Hi Nicolas,
Am 06.05.19 um 17:59 schrieb Nicolas Saenz Julienne:
> Hi Dan, thanks for reviewing.
>
> On Mon, 2019-05-06 at 18:20 +0300, Dan Carpenter wrote:
>> On Mon, May 06, 2019 at 04:40:29PM +0200, Nicolas Saenz Julienne wrote:
>>> @@ -1740,7 +1740,8 @@ parse_rx_slots(struct vchiq_state
On Mon, May 6, 2019 at 9:17 AM Linus Torvalds
wrote:
>
> So what is it that doesn't actually work? I've looked at the patch
> even more, and I can't for the life of me see how it wouldn't work.
And I do still react to PeterZ's
arch/x86/entry/entry_32.S| 150
On 03-05-19, 20:00, Pierre-Louis Bossart wrote:
> The description is directly derived from the MIPI DisCo specification.
>
> Credits: this patch is based on an earlier internal contribution by
> Vinod Koul, Sanyog Kale, Shreyas Nc and Hardik Shah.
>
> Signed-off-by: Pierre-Louis Bossart
> ---
>
On 06-05-19, 17:19, Greg KH wrote:
> On Mon, May 06, 2019 at 09:42:35AM -0500, Pierre-Louis Bossart wrote:
> > > > +
> > > > +int sdw_sysfs_slave_init(struct sdw_slave *slave)
> > > > +{
> > > > + struct sdw_slave_sysfs *sysfs;
> > > > + unsigned int src_dpns, sink_dpns, i, j;
> > > >
On Fri, May 3, 2019 at 7:03 PM Catalin Marinas wrote:
>
> On Tue, Apr 30, 2019 at 03:25:09PM +0200, Andrey Konovalov wrote:
> > This patch is a part of a series that extends arm64 kernel ABI to allow to
> > pass tagged user pointers (with the top byte set to something else other
> > than 0x00) as
On Mon, May 6, 2019 at 6:56 AM Steven Rostedt wrote:
>
> I can test this too. I was hoping to get this in by this merge window.
> I spent 3 hours yesterday trying to get Linus's version working on
> i386 with no success. Not sure how much time Linus will have to look at
> this, as he just opened
On 5/6/19 4:50 AM, Ingo Molnar wrote:
> Linus,
>
> Please pull the latest locking-core-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> locking-core-for-linus
>
># HEAD: d671002be6bdd7f77a771e23bf3e95d1f16775e6 locking/lockdep: Remove
> unnecessary
Doug said:
> > > > I'd propose that these three patches:
> > > >
> > > > 95047b0519c1 pstore: Refactor compression initialization
> > > > 416031653eb5 pstore: Allocate compression during late_initcall()
> > > > cb095afd4476 pstore: Centralize init/exit routines
Okay, confirmed. These look
On Mon, May 06, 2019 at 08:19:01AM +, eugen.hris...@microchip.com wrote:
>
>
> On 04.05.2019 02:58, Raag Jadav wrote:
>
> > On Thu, May 02, 2019 at 04:01:16PM +0200, Ludovic Desroches wrote:
> >> On Tue, Apr 30, 2019 at 04:03:32AM +0530, Raag Jadav wrote:
> >>> External E-Mail
> >>>
> >>>
>
On Wed, May 1, 2019 at 7:52 PM Kamal Dasu wrote:
>
> If mtd_oops is in progress switch to polling for nand command completion
> interrupts and use PIO mode wihtout DMA so that the mtd_oops buffer can
> be completely written in the assinged nand partition. This is needed in
> cases where the panic
On Mon, 6 May 2019 16:33:17 +0100
Qais Yousef wrote:
> On 05/06/19 10:46, Steven Rostedt wrote:
> > On Mon, 6 May 2019 15:42:00 +0100
> > Qais Yousef wrote:
> >
> > > I can control that for the wrappers I'm introducing. But the actual
> > > tracepoint
> > > get the 'trace_' part prepended
Hi Dan, thanks for reviewing.
On Mon, 2019-05-06 at 18:20 +0300, Dan Carpenter wrote:
> On Mon, May 06, 2019 at 04:40:29PM +0200, Nicolas Saenz Julienne wrote:
> > @@ -1740,7 +1740,8 @@ parse_rx_slots(struct vchiq_state *state)
> > >bulk_rx : >bulk_tx;
> >
>
BUG: unable to handle kernel paging request at a016a270
PGD 3270067 P4D 3270067 PUD 3271063 PMD 230bbd067 PTE 0
Oops: [#1
CPU: 0 PID: 6134 Comm: modprobe Not tainted 5.1.0+ #33
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
There is currently no easy and architecture-independent way to find the
lowest unusable virtual address available to a process without
brute-force calculation. This patch allows a user to easily retrieve
this value via /proc//status.
Using this patch, any program that previously needed to waste
On Mon, 18 Mar 2019 15:43:52 +0900
Masami Hiramatsu wrote:
> +.. _user_mem_access:
> +User Memory Access
> +--
> +Kprobe events supports user-space memory access. For that purpose, you can
> use
> +either user-space dereference syntax or 'ustring' type.
> +
> +The user-space
On 5/6/19 10:40 AM, Hans de Goede wrote:
Hi,
On 05-05-19 09:51, Takashi Iwai wrote:
On Sat, 04 May 2019 17:16:52 +0200,
Nariman wrote:
From: Jordy Ubink
The snprintf calls filling byt_rt5651_cpu_dai_name /
byt_rt5651_cpu_dai_name always fill them with the same string
(ssp0-port" resp
On 06-05-19, 18:34, Sameer Pujar wrote:
>
> On 5/4/2019 3:53 PM, Vinod Koul wrote:
> > On 02-05-19, 18:59, Sameer Pujar wrote:
> > > On 5/2/2019 5:55 PM, Vinod Koul wrote:
> > > > On 02-05-19, 16:23, Sameer Pujar wrote:
> > > > > On 5/2/2019 11:34 AM, Vinod Koul wrote:
> > > > > > On 30-04-19,
On 5/6/19 10:43 AM, Hans de Goede wrote:
Hi Pierre-Louis,
Nariman and the author authors of these patches are a group of students
doing
some kernel work for me and this is a warm-up assignment for them to get
used
to the kernel development process.
On 06-05-19 17:21, Pierre-Louis Bossart
Hi,
On 06-05-19 17:24, Pierre-Louis Bossart wrote:
On 5/4/19 10:16 AM, Nariman wrote:
From: Damian van Soelen
The snprintf calls filling cht_rt5645_cpu_dai_name / cht_rt5645_codec_aif_name
always fill them with the same string ("ssp0-port" resp "rt5645-aif2") so
instead of keeping these
On Sun, Apr 28, 2019 at 05:25:51PM -0400, Waiman Long wrote:
> diff --git a/kernel/locking/rwsem.c b/kernel/locking/rwsem.c
> index 6b11dce3139d..62fcb8bacfab 100644
> --- a/kernel/locking/rwsem.c
> +++ b/kernel/locking/rwsem.c
> @@ -56,7 +61,9 @@
> * a rwsem, but the overhead is simply too
On Sun, Apr 21, 2019 at 07:47:27PM +0800, Fuqian Huang wrote:
> Pointers should be printed with %p or %px rather than
> cast to unsigned long type and printed with %lx.
> Change %lx to %p to print the pointers.
>
> Signed-off-by: Fuqian Huang
Applied to cgroup/for-5.2.
Thanks.
--
tejun
Andy Shevchenko writes:
>> > On Wed, May 01, 2019 at 09:17:37AM +0200, Esben Haabendal wrote:
>> >> Andy Shevchenko writes:
>> >
>> >> > Hmm... Currently it's done inside individual port drivers, like
>> >> > 8250_dw.c.
>> >> > Each of the drivers can do it differently, for example 8250_lpss.c
Hi Pierre-Louis,
Nariman and the author authors of these patches are a group of students doing
some kernel work for me and this is a warm-up assignment for them to get used
to the kernel development process.
On 06-05-19 17:21, Pierre-Louis Bossart wrote:
static int
On Mon, May 06, 2019 at 05:58:59PM +0300, Andrey Ryabinin wrote:
>
>
> On 5/6/19 5:32 PM, Greg Kroah-Hartman wrote:
> > From: Arnd Bergmann
> >
> > commit e7c52b84fb18f08ce49b6067ae6285aca79084a8 upstream.
> >
>
> This is a fix/workaround for the previous patch c5caf21ab0cf "kasan: turn on
On Mon, May 06, 2019 at 06:36:45PM +0300, Andrey Ryabinin wrote:
>
>
> On 5/6/19 6:10 PM, Greg Kroah-Hartman wrote:
> > On Mon, May 06, 2019 at 05:55:54PM +0300, Andrey Ryabinin wrote:
> >>
> >>
> >> On 5/6/19 5:32 PM, Greg Kroah-Hartman wrote:
> >>> From: Andrey Ryabinin
> >>>
> >>> commit
Hi,
On 05-05-19 09:51, Takashi Iwai wrote:
On Sat, 04 May 2019 17:16:52 +0200,
Nariman wrote:
From: Jordy Ubink
The snprintf calls filling byt_rt5651_cpu_dai_name / byt_rt5651_cpu_dai_name always fill them
with the same string (ssp0-port" resp "rt5651-aif2"). So instead of keeping
these
On Fri, Apr 26, 2019 at 10:59:43AM -0700, Roman Gushchin wrote:
> Hi, Tejun!
>
> Please, pull these two follow-up patches for the cgroup v2 freezer.
>
> These are a fix for a spurious state transition, which could happen
> due to a race condition, and a cleanup of some dead code. Both patches
>
On Tue, 7 May 2019 00:22:03 +0900
Masami Hiramatsu wrote:
> Hi Steve,
>
> It seems I missed this message...
No problem. The number of times I missed messages... ugh.
>
> >
> > I'm curious, what interrupt handler are kprobes executing in that needs
> > random user space addresses?
>
>
On Mon, May 6, 2019 at 8:16 AM Doug Anderson wrote:
>
> On Sun, May 5, 2019 at 6:16 AM Greg KH wrote:
> >
> > On Fri, May 03, 2019 at 11:37:51AM -0700, Douglas Anderson wrote:
> > >
> > > On Thu, Oct 18, 2018 at 11:56 AM Kees Cook wrote:
> > > >
> > > > From: "Joel Fernandes (Google)"
> > > >
On 5/6/19 6:10 PM, Greg Kroah-Hartman wrote:
> On Mon, May 06, 2019 at 05:55:54PM +0300, Andrey Ryabinin wrote:
>>
>>
>> On 5/6/19 5:32 PM, Greg Kroah-Hartman wrote:
>>> From: Andrey Ryabinin
>>>
>>> commit c5caf21ab0cf884ef15b25af234f620e4a233139 upstream.
>>>
>>> In the upcoming gcc7
On 05/06/19 10:46, Steven Rostedt wrote:
> On Mon, 6 May 2019 15:42:00 +0100
> Qais Yousef wrote:
>
> > I can control that for the wrappers I'm introducing. But the actual
> > tracepoint
> > get the 'trace_' part prepended automatically by the macros.
> >
> > ie DECLARE_TRACE(pelt_rq, ...)
The following changes since commit 01aa9d518eae8a4d75cd3049defc6ed0b6d0a658:
Merge tag 'docs-4.20' of git://git.lwn.net/linux (2018-10-24 18:01:11 +0100)
are available in the Git repository at:
git://github.com/kleikamp/linux-shaggy.git tags/jfs-5.2
for you to fetch changes up to
Support receiving IPMB requests on a Satellite MC from the BMC.
Once a response is ready, this driver will send back a response
to the BMC via the IPMB channel.
Signed-off-by: Asmaa Mnebhi
---
Documentation/IPMB.txt | 103 ++
drivers/char/ipmi/Kconfig| 8 +
Hi Vadim,
I have addressed your comments:
1) removed typecasting and replaced it with a macro to get the 8 bit
address. I think it is more readable this way.
2) added space
Thank you for your feedback!
Asmaa Mnebhi (1):
Add support for IPMB driver
Documentation/IPMB.txt | 103
On 5/5/19 11:40 PM, Mark Brown wrote:
On Fri, May 03, 2019 at 09:32:53AM -0500, Pierre-Louis Bossart wrote:
As I mentioned it'll compile the bus even if there is no user for it, but
it's your call: alignment or optimization.
You can have both. Alignment is a requirement. If you want to
Change strcat to strcpy in the "None" case as it is never valid to append
"None" to any other message. It may also overflow char message[5], in a
race condition on cinode if cinode->oplock is unset by another thread
after "RHW" or "RH" had been written to message.
Signed-off-by: Christoph Probst
On 5/4/19 10:16 AM, Nariman wrote:
From: Jordy Ubink
The snprintf calls filling byt_rt5651_cpu_dai_name / byt_rt5651_cpu_dai_name always fill them
with the same string (ssp0-port" resp "rt5651-aif2"). So instead of keeping
these buffers around and making the cpu_dai_name / codec_dai_name
On Mon, May 06, 2019 at 08:38:13AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: ba26c41d985d7c66c6198e0e22cd287434d83a3e ("rcutorture: Fix
> stutter_wait() return value and freelist checks")
>
On 5/4/19 10:16 AM, Nariman wrote:
From: Damian van Soelen
The snprintf calls filling cht_rt5645_cpu_dai_name / cht_rt5645_codec_aif_name
always fill them with the same string ("ssp0-port" resp "rt5645-aif2") so
instead of keeping these buffers around and making the cpu_dai_name /
> On Mon 06-05-19 22:06:38, Zhiqiang Liu wrote:
>> From: Kai Shen
>>
>> spinlock recursion happened when do LTP test:
>> #!/bin/bash
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>>
>> The dtor returned
Hi Steve,
It seems I missed this message...
On Thu, 21 Mar 2019 22:46:02 -0400
Steven Rostedt wrote:
> On Mon, 18 Mar 2019 15:43:17 +0900
> Masami Hiramatsu wrote:
>
> > WARN_ON_IN_IRQ() assumes that the access_ok() and following
> > user memory access can sleep. But this assumption is not
>
static int byt_rt5640_suspend(struct snd_soc_card *card)
@@ -1268,28 +1266,12 @@ static int snd_byt_rt5640_mc_probe(struct
platform_device *pdev)
log_quirks(>dev);
if ((byt_rt5640_quirk & BYT_RT5640_SSP2_AIF2) ||
- (byt_rt5640_quirk & BYT_RT5640_SSP0_AIF2)) {
-
-
On Mon, May 06, 2019 at 04:40:29PM +0200, Nicolas Saenz Julienne wrote:
> @@ -1740,7 +1740,8 @@ parse_rx_slots(struct vchiq_state *state)
> >bulk_rx : >bulk_tx;
>
> DEBUG_TRACE(PARSE_LINE);
> - if
On Mon, May 06, 2019 at 09:42:35AM -0500, Pierre-Louis Bossart wrote:
> > > +
> > > +int sdw_sysfs_slave_init(struct sdw_slave *slave)
> > > +{
> > > + struct sdw_slave_sysfs *sysfs;
> > > + unsigned int src_dpns, sink_dpns, i, j;
> > > + int err;
> > > +
> > > + if (slave->sysfs) {
> > > +
"Enrico Weigelt, metux IT consult" writes:
> On 30.04.19 16:04, Esben Haabendal wrote:
>> Allow getting memory resource (mapbase or iobase) as well as irq from
>> platform_device resources.
>>
>> The UPF_DEV_RESOURCES flag must be set for devices where platform_device
>> resources are to be
On 5/6/19 9:15 AM, Greg KH wrote:
On Mon, May 06, 2019 at 08:47:15AM -0600, Shuah Khan wrote:
On 5/5/19 3:13 AM, Greg KH wrote:
On Thu, May 02, 2019 at 01:47:40PM -0600, Shuah Khan wrote:
Add a sleep between detach and check for exportable devices to avoid
the following segfault from
On 4/23/19 9:36 AM, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add the Stratix10 SDMMC EDAC node.
>
> Signed-off-by: Thor Thayer
> ---
> arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
Hi Carmeli,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1 next-20190506]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On 4/23/19 9:36 AM, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add the OCRAM ECC node with Stratix10 compatible string.
>
> Signed-off-by: Thor Thayer
> ---
> arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 8
> 1 file changed, 8 insertions(+)
>
> diff --git
On Mon, 6 May 2019 17:03:20 +0300, Jarkko Nikula wrote:
> On 5/6/19 4:16 PM, Jean Delvare wrote:
> > Some EE1004 implementations will not properly ack page selection
> > commands. They still set the page correctly, so there is no actual
> > error. Deal with this case gracefully by checking the
On Sat, May 04, 2019 at 04:59:12PM +1000, Nicholas Piggin wrote:
> Frederic Weisbecker's on May 4, 2019 10:27 am:
> > On Fri, May 03, 2019 at 10:47:37AM -0700, tip-bot for Nicholas Piggin wrote:
> >> Commit-ID: 9219565aa89033a9cfdae788c1940473a1253d6c
> >> Gitweb:
> >>
On 5/6/19 6:55 AM, Suwan Kim wrote:
When hcd resumes, hcd_bus_resume() calls vhci_bus_resume() which sets
hcd->state as HC_STATE_RUNNING. But after calling vhci_bus_resume(),
hcd_bus_resume() also sets hcd->state as HC_STATE_RUNNING. So, setting
hcd->state in vhci_hcd_resume() is unnecessary.
On Mon, May 06, 2019 at 08:47:15AM -0600, Shuah Khan wrote:
> On 5/5/19 3:13 AM, Greg KH wrote:
> > On Thu, May 02, 2019 at 01:47:40PM -0600, Shuah Khan wrote:
> > > Add a sleep between detach and check for exportable devices to avoid
> > > the following segfault from libc-2.27.so
> > >
> > > [
Hi,
On Sun, May 5, 2019 at 6:16 AM Greg KH wrote:
>
> On Fri, May 03, 2019 at 11:37:51AM -0700, Douglas Anderson wrote:
> > Hi,
> >
> > On Thu, Oct 18, 2018 at 11:56 AM Kees Cook wrote:
> > >
> > > From: "Joel Fernandes (Google)"
> > >
> > > ramoops's call of pstore_register() was recently
On Thu, May 02, 2019 at 11:02:40AM -0700, Linus Torvalds wrote:
> On Thu, May 2, 2019 at 9:21 AM Peter Zijlstra wrote:
> >
> > TL;DR, on x86_32 kernel->kernel IRET frames are only 3 entries and do
> > not include ESP/SS, so not only wasn't regs->sp setup, if you changed it
> > it wouldn't be
Add new table rate for BPLL for Exynos5422 SoC supporting Dynamic Memory
Controller frequencies for driver's DRAM timings.
Signed-off-by: Lukasz Luba
---
drivers/clk/samsung/clk-exynos5420.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git
On Mon, May 06, 2019 at 05:55:54PM +0300, Andrey Ryabinin wrote:
>
>
> On 5/6/19 5:32 PM, Greg Kroah-Hartman wrote:
> > From: Andrey Ryabinin
> >
> > commit c5caf21ab0cf884ef15b25af234f620e4a233139 upstream.
> >
> > In the upcoming gcc7 release, the -fsanitize=kernel-address option at
> >
In order get the clock by phandle and use it with regmap it needs to be
compatible with syscon. The DMC driver uses two registers from clock
register set and needs the regmap of them.
Signed-off-by: Lukasz Luba
---
arch/arm/boot/dts/exynos5800.dtsi | 2 +-
1 file changed, 1 insertion(+), 1
From: Charles Keepax
commit 639e5eb3c7d67e407f2a71fccd95323751398f6f upstream.
Previously support was added to allow streams to be stopped and
started again without the DSP being power cycled and this was done
by clearing the buffer state in trigger start. Another supported
use-case is using
USB 2.0 specification chapter 11.17.5 says "as part of endpoint halt
processing for full-/low-speed endpoints connected via a TT, the host
software must use the Clear_TT_Buffer request to the TT to ensure
that the buffer is not in the busy state".
In our case, a full-speed speaker (ConferenceCam)
[ Upstream commit 1cb1d2c64e812928fe0a40b8f7e74523d0283dbe ]
Blacklist "Universal Xport" LUN. It's used for in-band storage array
management. Also add model to the rdac dh family.
Cc: Martin Wilck
Cc: Hannes Reinecke
Cc: NetApp RDAC team
Cc: Christophe Varoqui
Cc: James E.J. Bottomley
Cc:
From: Nicolas Le Bayon
commit c86da50cfd840edf223a242580913692acddbcf6 upstream.
It conforms with Reference Manual I2C timing section.
Fixes: aeb068c57214 ("i2c: i2c-stm32f7: add driver")
Signed-off-by: Nicolas Le Bayon
Signed-off-by: Bich Hemon
Reviewed-by: Pierre-Yves MORDRET
Hi Angus,
On Mon, May 6, 2019 at 11:10 AM Angus Ainslie (Purism) wrote:
>
> If the fault status register doesn't get cleared then
> the ptn5110 interrupt gets stuck on. As the fault register gets
> set everytime the ptn5110 powers on the interrupt is always stuck.
>
> Signed-off-by: Angus
From: Anson Huang
commit a329bbe707cee2cf8c660890ef2ad0d00ec7e8a3 upstream.
On i.MX8MQ platform, clock driver uses platform driver
model and it is probed after GPIO driver, so when GPIO
driver fails to get clock, it should check the error type
to decide whether to return defer probe or just
This is the start of the stable review cycle for the 5.0.14 release.
There are 122 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed 08 May 2019 02:29:09 PM UTC.
Anything
[ Upstream commit cef0d4948cb0a02db37ebfdc320e127c77ab1637 ]
There is a race condition that could happen if hid_debug_rdesc_show()
is running while hdev is in the process of going away (device removal,
system suspend, etc) which could result in NULL pointer dereference:
BUG: unable to
[ Upstream commit 882c5e552ffd06856de42261460f46e18319d259 ]
The DA9063AD doesn't support alarms on any seconds and its granularity is
the minute. Set uie_unsupported in that case.
Reported-by: Wolfram Sang
Reported-by: Geert Uytterhoeven
Reviewed-by: Wolfram Sang
Tested-by: Wolfram Sang
From: Rajneesh Bhardwaj
commit d6827015e671cd17871c9b7a0fabe06c044f7470 upstream.
For Cannonlake and Icelake, the IP name for Res_6 should be SPF i.e.
South Port F. No functional change is intended other than just renaming
the IP appropriately.
Cc: "David E. Box"
Cc: Srinivas Pandruvada
From: Kailang Yang
commit 0700d3d117a7f110bd83873e13652f69c54b upstream.
Fixed Dell AIO speaker noise.
spec->gen.auto_mute_via_amp = 1, this option was solved speaker white
noise at boot.
codec->power_save_node = 0, this option was solved speaker noise at
resume back.
Fixes: 9226665159f0
[ Upstream commit 58b6e5e8f1addd44583d61b0a03c0f5519527e35 ]
When mknod is used to create a block special file in hugetlbfs, it will
allocate an inode and kmalloc a 'struct resv_map' via resv_map_alloc().
inode->i_mapping->private_data will point the newly allocated resv_map.
However, when the
[ Upstream commit 972c9be784e077bc56472c78243e0326e525b689 ]
Ratelimit RX error logs.
Signed-off-by: Aaro Koskinen
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin (Microsoft)
---
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 14 --
1 file changed, 8 insertions(+),
Hello Martin.
On Tue, Apr 30, 2019 at 11:16:21PM +0200, Martin Blumenstingl wrote:
> Hello Serge,
>
> On Mon, Apr 29, 2019 at 11:12 PM Serge Semin wrote:
> [...]
> > > > > Apparently the current config_init method doesn't support RXID
> > > > > setting.
> > > > > The patch introduced current
From: Sean Christopherson
commit b904cb8dff824b79233e82c078837627ebd52717 upstream.
...to avoid dereferencing a null pointer when querying the per-vCPU
timer advance.
Fixes: 39497d7660d98 ("KVM: lapic: Track lapic timer advance per vCPU")
Reported-by:
[ Upstream commit eca4a928585ac08147e5cc8e2111ecbc6279ee31 ]
Traditionally, the PF (Physical Function) which resides on vport 0 was
the E-switch manager. Since the ECPF (Embedded CPU Physical Function),
which resides on vport 0xfffe, was introduced as the E-Switch manager,
the assumption that the
[ Upstream commit cef0d4948cb0a02db37ebfdc320e127c77ab1637 ]
There is a race condition that could happen if hid_debug_rdesc_show()
is running while hdev is in the process of going away (device removal,
system suspend, etc) which could result in NULL pointer dereference:
BUG: unable to
From: Johannes Berg
commit 517879147493a5e1df6b89a50f708f1133fcaddb upstream.
We need to dereference the directory to get its parent to
be able to rename it, so it's clearly not safe to try to
do this with ERR_PTR() pointers. Skip in this case.
It seems that this is most likely what was
From: Jeffrey Hugo
commit 0c8ff62504e3a667387e87889a259632c3199a86 upstream.
The usb30_master_clk supports a 60Mhz frequency, but that is missing from
the table of supported frequencies. Add it.
Fixes: b5f5f525c547 (clk: qcom: Add MSM8998 Global Clock Control (GCC) driver)
Signed-off-by:
[ Upstream commit cef0d4948cb0a02db37ebfdc320e127c77ab1637 ]
There is a race condition that could happen if hid_debug_rdesc_show()
is running while hdev is in the process of going away (device removal,
system suspend, etc) which could result in NULL pointer dereference:
BUG: unable to
[ Upstream commit cef0d4948cb0a02db37ebfdc320e127c77ab1637 ]
There is a race condition that could happen if hid_debug_rdesc_show()
is running while hdev is in the process of going away (device removal,
system suspend, etc) which could result in NULL pointer dereference:
BUG: unable to
The patch adds AC timings information needed to support LPDDR3 and memory
controllers. The structure is used in of_memory and currently in Exynos
5422 DMC. Add parsing data needed for LPDDR3 support.
It is currently used in Exynos5422 Dynamic Memory Controller.
Signed-off-by: Lukasz Luba
---
[ Upstream commit 426b046b748d1f47e096e05bdcc6fb4172791307 ]
When compiling with -Wformat, clang emits the following warnings:
drivers/vfio/pci/vfio_pci.c:1601:5: warning: format specifies type
'unsigned short' but the argument has type 'unsigned int' [-Wformat]
From: Alan Stern
commit c2b71462d294cf517a0bc6e4fd6424d7cee5596f upstream.
The syzkaller fuzzer reported a bug in the USB hub driver which turned
out to be caused by a negative runtime-PM usage counter. This allowed
a hub to be runtime suspended at a time when the driver did not expect
it.
Hi,
On 06-05-19 16:59, Andy Shevchenko wrote:
On Mon, May 6, 2019 at 5:47 PM Hans de Goede wrote:
Hi,
On 06-05-19 14:38, Andy Shevchenko wrote:
On Mon, Apr 29, 2019 at 6:01 PM Hans de Goede wrote:
The Lex 3I380D industrial PC has 4 ethernet controllers on board
which need pmc_plt_clk0 -
From: Daniel Jurgens
commit d60667fc398ed34b3c7456b020481c55c760e503 upstream.
If the notifier runs after the security context is freed an access of
freed memory can occur.
Fixes: 47a2b338fe63 ("IB/core: Enforce security on management datagrams")
Signed-off-by: Daniel Jurgens
Reviewed-by:
From: Douglas Anderson
commit b82d6c1f8f8288f744a9dcc16cd3085d535decca upstream.
The commit fc3a2fcaa1ba ("mwifiex: use atomic bitops to represent
adapter status variables") had a fairly straightforward bug in it. It
contained this bit of diff:
- if (!adapter->is_suspended) {
+ if
From: Alan Stern
commit c114944d7d67f24e71562fcfc18d550ab787e4d4 upstream.
The syzkaller USB fuzzer spotted a slab-out-of-bounds bug in the
ds2490 driver. This bug is caused by improper use of the altsetting
array in the usb_interface structure (the array's entries are not
always stored in
Hi all,
This is v7 of the patch set which adds support of Dynamic Memory Controller
for Exynos5422 SoC.
The driver supports Dynamic Voltage and Frequency Scalling
for the DMC and DRAM. It also provides needed timings for different
speed operations of the DRAM memory.
There is also new generic
This patch provides support for clocks needed for Dynamic Memory Controller
in Exynos5422 SoC. It adds CDREX base register addresses, new DIV, MUX and
GATE entries.
Signed-off-by: Lukasz Luba
---
drivers/clk/samsung/clk-exynos5420.c | 58 +---
1 file changed, 54
The patch adds description for DT binding for a new Exynos5422 Dynamic
Memory Controller device.
Signed-off-by: Lukasz Luba
---
.../bindings/memory-controllers/exynos5422-dmc.txt | 74 ++
1 file changed, 74 insertions(+)
create mode 100644
501 - 600 of 1279 matches
Mail list logo
