[PATCH] proc: save decrement during lookup/readdir in /proc/$PID

Comparison for "<" works equally well as comparison for "<=" but one SUB/LEA is saved (no, it is not optimised away, at least here). Signed-off-by: Alexey Dobriyan --- fs/proc/base.c |8 1 file changed, 4 insertions(+), 4 deletions(-) --- a/fs/proc/base.c +++

[PATCH] proc: save decrement during lookup/readdir in /proc/$PID

Comparison for "<" works equally well as comparison for "<=" but one SUB/LEA is saved (no, it is not optimised away, at least here). Signed-off-by: Alexey Dobriyan --- fs/proc/base.c |8 1 file changed, 4 insertions(+), 4 deletions(-) --- a/fs/proc/base.c +++ b/fs/proc/base.c @@

Re: [PATCH 2/2] virtio_ring: fix complaint by sparse

On Tue, 22 Nov 2016 13:51:50 +0800 Gonglei wrote: > # make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/ > > drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment > (different base types) > drivers/virtio/virtio_ring.c:423:19:expected unsigned

Re: [PATCH 2/2] virtio_ring: fix complaint by sparse

On Tue, 22 Nov 2016 13:51:50 +0800 Gonglei wrote: > # make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/ > > drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment > (different base types) > drivers/virtio/virtio_ring.c:423:19:expected unsigned int [unsigned] >

Re: linux-next: manual merge of the userns tree with Linus' tree

Stephen Rothwell writes: > Hi Eric, > > Today's linux-next merge of the userns tree got conflicts in: > > arch/alpha/kernel/ptrace.c > arch/blackfin/kernel/ptrace.c > arch/cris/arch-v32/kernel/ptrace.c > arch/ia64/kernel/ptrace.c > arch/mips/kernel/ptrace32.c >

Re: linux-next: manual merge of the userns tree with Linus' tree

Stephen Rothwell writes: > Hi Eric, > > Today's linux-next merge of the userns tree got conflicts in: > > arch/alpha/kernel/ptrace.c > arch/blackfin/kernel/ptrace.c > arch/cris/arch-v32/kernel/ptrace.c > arch/ia64/kernel/ptrace.c > arch/mips/kernel/ptrace32.c >

Re: [PATCH] misc: sram: remove useless #ifdef

Hi Arnd, On 11/22/2016 04:30 PM, Arnd Bergmann wrote: A recent patch added a new function that is now unused whenever CONFIG_OF is disabled: drivers/misc/sram.c:342:12: error: 'atmel_securam_wait' defined but not used [-Werror=unused-function] There is actually no reason for the #ifdef,

Re: [PATCH] clk: bcm: Fix unmet Kconfig dependencies for CLK_BCM_63XX

Hi Florian, On 11/22/2016 9:43 AM, Florian Fainelli wrote: > With commit f4e871509959 ("clk: iproc: Make clocks visible options"), > COMMON_CLK_IPROC gained a dependency on ARCH_BCM_IPROC, yet CLK_BCM_63XX > also selects that option, this causes the following Kconfig warning: > > warning:

Re: [PATCH] misc: sram: remove useless #ifdef

Hi Arnd, On 11/22/2016 04:30 PM, Arnd Bergmann wrote: A recent patch added a new function that is now unused whenever CONFIG_OF is disabled: drivers/misc/sram.c:342:12: error: 'atmel_securam_wait' defined but not used [-Werror=unused-function] There is actually no reason for the #ifdef,

Re: [PATCH] clk: bcm: Fix unmet Kconfig dependencies for CLK_BCM_63XX

Hi Florian, On 11/22/2016 9:43 AM, Florian Fainelli wrote: > With commit f4e871509959 ("clk: iproc: Make clocks visible options"), > COMMON_CLK_IPROC gained a dependency on ARCH_BCM_IPROC, yet CLK_BCM_63XX > also selects that option, this causes the following Kconfig warning: > > warning:

Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on

On Tue, Nov 22, 2016 at 12:25 AM, Laurent Pinchart wrote: > On Monday 21 Nov 2016 16:37:31 John Stultz wrote: >> Secton 4.1 of the adv7511 programming guide advises one waits >> 200ms after powering on the chip before trying to communicate >> with it via i2c.

Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on

On Tue, Nov 22, 2016 at 12:25 AM, Laurent Pinchart wrote: > On Monday 21 Nov 2016 16:37:31 John Stultz wrote: >> Secton 4.1 of the adv7511 programming guide advises one waits >> 200ms after powering on the chip before trying to communicate >> with it via i2c. Not doing so can cause reliability

Re: Linux 4.4.34

. > > I was wondering if we shouldn't just cap all cases? > > It seems like this could potentially return a value greater than skb- >>len in the "good" case since things like IP header length isn't > validated other then making sure it meets the minimum value, and if > there isn't a recognized L4

Re: Linux 4.4.34

. > > I was wondering if we shouldn't just cap all cases? > > It seems like this could potentially return a value greater than skb- >>len in the "good" case since things like IP header length isn't > validated other then making sure it meets the minimum value, and if > there isn't a recognized L4

[patch 2/6] hwmon/coretemp: Simplify sibling management

The coretemp driver provides a sysfs interface per physical core. If hyperthreading is enabled and one of the siblings goes offline the sysfs interface is removed and then immeditately created again for the sibling. The only difference of them is the target cpu for the rdmsr_on_cpu() in the sysfs

[patch 4/6] [PREEMPT-RT] hwmon/coretemp: Convert to hotplug state machine

Install the callbacks via the state machine. Setup and teardown are handled by the hotplug core. Signed-off-by: Sebastian Andrzej Siewior Cc: linux-hw...@vger.kernel.org Cc: Fenghua Yu Cc: Jean Delvare Cc: r...@linuxtronix.de Cc:

[patch 6/6] hwmon/coretemp: Simplify package management

Keeping track of the per package platform devices requires an extra object, which is held in a linked list. The maximum number of packages is known at init() time. So the extra object and linked list management can be replaced by an array of platform device pointers in which the per package

[patch 2/6] hwmon/coretemp: Simplify sibling management

The coretemp driver provides a sysfs interface per physical core. If hyperthreading is enabled and one of the siblings goes offline the sysfs interface is removed and then immeditately created again for the sibling. The only difference of them is the target cpu for the rdmsr_on_cpu() in the sysfs

[patch 4/6] [PREEMPT-RT] hwmon/coretemp: Convert to hotplug state machine

Install the callbacks via the state machine. Setup and teardown are handled by the hotplug core. Signed-off-by: Sebastian Andrzej Siewior Cc: linux-hw...@vger.kernel.org Cc: Fenghua Yu Cc: Jean Delvare Cc: r...@linuxtronix.de Cc: Guenter Roeck Link:

[patch 6/6] hwmon/coretemp: Simplify package management

Keeping track of the per package platform devices requires an extra object, which is held in a linked list. The maximum number of packages is known at init() time. So the extra object and linked list management can be replaced by an array of platform device pointers in which the per package

Re: [PATCH 2/2] PCI: iproc: avoid maybe-uninitialized warning

Hi Arnd, On 11/22/2016 6:17 AM, Arnd Bergmann wrote: > gcc notices that calling iproc_pcie_setup_ib with ib->nr_regions==0 > would result in an uninitialized return value: > > drivers/pci/host/pcie-iproc.c: In function 'iproc_pcie_setup_ib': > drivers/pci/host/pcie-iproc.c:894:6: error: 'ret'

Re: [PATCH 2/2] PCI: iproc: avoid maybe-uninitialized warning

Hi Arnd, On 11/22/2016 6:17 AM, Arnd Bergmann wrote: > gcc notices that calling iproc_pcie_setup_ib with ib->nr_regions==0 > would result in an uninitialized return value: > > drivers/pci/host/pcie-iproc.c: In function 'iproc_pcie_setup_ib': > drivers/pci/host/pcie-iproc.c:894:6: error: 'ret'

[patch 1/6] hwmon/coretemp: Fixup target cpu for package when cpu is offlined

When a CPU is offlined nothing checks whether it is the target CPU for the package temperature sysfs interface. As a consequence all future readouts of the package temperature return crap: # cat temp1_input 9 which is Tjmax of that package. Check whether the outgoing CPU is the target for

[patch 0/6] hwmon/coretemp: Hotplug fixes, cleanups and state machine conversion

After the first attempt to convert the coretemp driver to the hotplug state machine failed, we had a deeper look and went a bit farther. The driver has quite some interesting concepts vs. the package, core and sysfs file management and a bug in the package temperature sysfs interface vs. cpu

[patch 1/6] hwmon/coretemp: Fixup target cpu for package when cpu is offlined

When a CPU is offlined nothing checks whether it is the target CPU for the package temperature sysfs interface. As a consequence all future readouts of the package temperature return crap: # cat temp1_input 9 which is Tjmax of that package. Check whether the outgoing CPU is the target for

[patch 0/6] hwmon/coretemp: Hotplug fixes, cleanups and state machine conversion

After the first attempt to convert the coretemp driver to the hotplug state machine failed, we had a deeper look and went a bit farther. The driver has quite some interesting concepts vs. the package, core and sysfs file management and a bug in the package temperature sysfs interface vs. cpu

[patch 5/6] hwmon/coretemp: Use proper error codes in cpu online callback

The cpu online callback returns success unconditionally even when the device has no support, micro code mismatches or device allocation fails. Only if CPU_HOTPLUG is disabled, the init function checks whether the device list is empty and removes the driver. This does not make sense. If CPU

[patch 3/6] hwmon/coretemp: Avoid redundant lookups

No point in looking up the same thing over and over. Signed-off-by: Thomas Gleixner --- drivers/hwmon/coretemp.c | 19 ++- 1 file changed, 6 insertions(+), 13 deletions(-) --- a/drivers/hwmon/coretemp.c +++ b/drivers/hwmon/coretemp.c @@ -533,21 +533,14 @@

[patch 5/6] hwmon/coretemp: Use proper error codes in cpu online callback

The cpu online callback returns success unconditionally even when the device has no support, micro code mismatches or device allocation fails. Only if CPU_HOTPLUG is disabled, the init function checks whether the device list is empty and removes the driver. This does not make sense. If CPU

[patch 3/6] hwmon/coretemp: Avoid redundant lookups

No point in looking up the same thing over and over. Signed-off-by: Thomas Gleixner --- drivers/hwmon/coretemp.c | 19 ++- 1 file changed, 6 insertions(+), 13 deletions(-) --- a/drivers/hwmon/coretemp.c +++ b/drivers/hwmon/coretemp.c @@ -533,21 +533,14 @@ static int

Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

On Tue, Nov 22, 2016 at 9:38 AM, Laurent Pinchart wrote: > Hi John, > > On Tuesday 22 Nov 2016 09:25:22 John Stultz wrote: >> On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote: >> > On Monday 21 Nov 2016 16:37:30 John Stultz wrote: >> @@ -545,24 +554,13

Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

On Tue, Nov 22, 2016 at 9:38 AM, Laurent Pinchart wrote: > Hi John, > > On Tuesday 22 Nov 2016 09:25:22 John Stultz wrote: >> On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote: >> > On Monday 21 Nov 2016 16:37:30 John Stultz wrote: >> @@ -545,24 +554,13 @@ static int

[PATCH] clk: bcm: Fix unmet Kconfig dependencies for CLK_BCM_63XX

With commit f4e871509959 ("clk: iproc: Make clocks visible options"), COMMON_CLK_IPROC gained a dependency on ARCH_BCM_IPROC, yet CLK_BCM_63XX also selects that option, this causes the following Kconfig warning: warning: (CLK_BCM_63XX) selects COMMON_CLK_IPROC which has unmet direct dependencies

[PATCH] clk: bcm: Fix unmet Kconfig dependencies for CLK_BCM_63XX

With commit f4e871509959 ("clk: iproc: Make clocks visible options"), COMMON_CLK_IPROC gained a dependency on ARCH_BCM_IPROC, yet CLK_BCM_63XX also selects that option, this causes the following Kconfig warning: warning: (CLK_BCM_63XX) selects COMMON_CLK_IPROC which has unmet direct dependencies

Re: [PATCH v2] kvm: x86: don't print warning messages for unimplemented msrs

2016-11-15 01:36-0500, Bandan Das: > > Change unimplemented msrs messages to use pr_debug. > If CONFIG_DYNAMIC_DEBUG is set, then these messages can be > enabled at run time or else -DDEBUG can be used at compile > time to enable them. These messages will still be printed if > ignore_msrs=1. > >

Re: [PATCH v2] kvm: x86: don't print warning messages for unimplemented msrs

2016-11-15 01:36-0500, Bandan Das: > > Change unimplemented msrs messages to use pr_debug. > If CONFIG_DYNAMIC_DEBUG is set, then these messages can be > enabled at run time or else -DDEBUG can be used at compile > time to enable them. These messages will still be printed if > ignore_msrs=1. > >

Re: Linux 4.4.34

On Tue, 2016-11-22 at 09:14 -0800, Eric Dumazet wrote: > On Tue, Nov 22, 2016 at 9:06 AM, Greg KH wrote: > > > > On Tue, Nov 22, 2016 at 05:59:12PM +0100, Andre Noll wrote: > > > > > > On Mon, Nov 21, 10:28, Greg KH wrote > > > > > > > > I'm announcing the release

Re: Linux 4.4.34

On Tue, 2016-11-22 at 09:14 -0800, Eric Dumazet wrote: > On Tue, Nov 22, 2016 at 9:06 AM, Greg KH wrote: > > > > On Tue, Nov 22, 2016 at 05:59:12PM +0100, Andre Noll wrote: > > > > > > On Mon, Nov 21, 10:28, Greg KH wrote > > > > > > > > I'm announcing the release of the 4.4.34 kernel. > > > >

Re: [PATCH 1/2] PCI: iproc: fix 32-bit build

On 11/22/2016 6:17 AM, Arnd Bergmann wrote: > The newly added code to setup the inbound ranges causes a link error > on 32-bit machines from a 32-bit division: > > drivers/pci/host/pcie-iproc.o: In function `iproc_pcie_setup_ib': > pcie-iproc.c:(.text.iproc_pcie_setup_ib+0x14c): undefined

Re: [PATCH 1/2] PCI: iproc: fix 32-bit build

On 11/22/2016 6:17 AM, Arnd Bergmann wrote: > The newly added code to setup the inbound ranges causes a link error > on 32-bit machines from a 32-bit division: > > drivers/pci/host/pcie-iproc.o: In function `iproc_pcie_setup_ib': > pcie-iproc.c:(.text.iproc_pcie_setup_ib+0x14c): undefined

Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

Hi John, On Tuesday 22 Nov 2016 09:25:22 John Stultz wrote: > On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote: > > On Monday 21 Nov 2016 16:37:30 John Stultz wrote: > @@ -545,24 +554,13 @@ static int adv7511_get_modes(struct adv7511 *adv7511, > >> unsigned int count; > >> >

Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

Hi John, On Tuesday 22 Nov 2016 09:25:22 John Stultz wrote: > On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote: > > On Monday 21 Nov 2016 16:37:30 John Stultz wrote: > @@ -545,24 +554,13 @@ static int adv7511_get_modes(struct adv7511 *adv7511, > >> unsigned int count; > >> >

Re: net/can: use-after-free in bcm_rx_thr_flush

On Tue, Nov 22, 2016 at 6:29 PM, Oliver Hartkopp wrote: > Hi Andrey, > > thanks for the report. > > Although I can't see the issue in the code ... > > On 11/22/2016 10:22 AM, Andrey Konovalov wrote: > >> == >>

Re: net/can: use-after-free in bcm_rx_thr_flush

On Tue, Nov 22, 2016 at 6:29 PM, Oliver Hartkopp wrote: > Hi Andrey, > > thanks for the report. > > Although I can't see the issue in the code ... > > On 11/22/2016 10:22 AM, Andrey Konovalov wrote: > >> == >> BUG: KASAN:

[PATCH v2] powernv: Handle wakeup from idle due to SRESET

From: "Gautham R. Shenoy" The existing code doesn't handle the case when CPU which was in a hardware-idle state (nap,sleep,winkle on POWER8 and various stop states on POWER9) gets woken up due to a System Reset interrupt. This patch checks if the CPU was woken up due to

[PATCH v2] powernv: Handle wakeup from idle due to SRESET

From: "Gautham R. Shenoy" The existing code doesn't handle the case when CPU which was in a hardware-idle state (nap,sleep,winkle on POWER8 and various stop states on POWER9) gets woken up due to a System Reset interrupt. This patch checks if the CPU was woken up due to System Reset, in which

RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

> Here are a couple of additional questions: > > - When the network interface is created, there is no IP address > assigned (or negotiated ?) on the Linux side. But it is done on the > MacOS side. And in the Linux kernel logs I can also read the message: > "ready for ThunderboltIP

RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

> Here are a couple of additional questions: > > - When the network interface is created, there is no IP address > assigned (or negotiated ?) on the Linux side. But it is done on the > MacOS side. And in the Linux kernel logs I can also read the message: > "ready for ThunderboltIP

[PATCH] [hv] storvsc: Payload buffer incorrectly sized for 32 bit kernels.

On a 32 bit kernel sizeof(void *) is not 64 bits as hv_mpb_array requires. Also the buffer needs to be cleared or the upper bytes could contain junk. Suggested-by: Vitaly Kuznets Signed-off-by: Cathy Avery --- drivers/scsi/storvsc_drv.c | 3 ++- 1 file

[PATCH] [hv] storvsc: Payload buffer incorrectly sized for 32 bit kernels.

On a 32 bit kernel sizeof(void *) is not 64 bits as hv_mpb_array requires. Also the buffer needs to be cleared or the upper bytes could contain junk. Suggested-by: Vitaly Kuznets Signed-off-by: Cathy Avery --- drivers/scsi/storvsc_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function.

On Tue, Nov 22, 2016 at 12:31 PM, Ville Syrjälä wrote: > On Tue, Nov 22, 2016 at 12:23:59PM -0500, Rob Clark wrote: >> On Tue, Nov 22, 2016 at 11:50 AM, Ville Syrjälä >> wrote: >> > On Tue, Nov 22, 2016 at 04:41:06PM +, Liviu

Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function.

On Tue, Nov 22, 2016 at 12:31 PM, Ville Syrjälä wrote: > On Tue, Nov 22, 2016 at 12:23:59PM -0500, Rob Clark wrote: >> On Tue, Nov 22, 2016 at 11:50 AM, Ville Syrjälä >> wrote: >> > On Tue, Nov 22, 2016 at 04:41:06PM +, Liviu Dudau wrote: >> >> drm_get_format_name() de-references the buf

Re: [PATCH][V4] nbd: add multi-connection support

Hi Josef, [cc to nbd-general added] On Thu, Nov 17, 2016 at 03:27:30PM -0500, Josef Bacik wrote: > NBD can become contended on its single connection. We have to serialize all > writes and we can only process one read response at a time. Fix this by > allowing userspace to provide multiple

Re: [PATCH][V4] nbd: add multi-connection support

Hi Josef, [cc to nbd-general added] On Thu, Nov 17, 2016 at 03:27:30PM -0500, Josef Bacik wrote: > NBD can become contended on its single connection. We have to serialize all > writes and we can only process one read response at a time. Fix this by > allowing userspace to provide multiple

[PATCH] thermal: hwmon: Properly report critical temperature in sysfs

In the critical sysfs entry the thermal hwmon was returning wrong temperature to the user-space. It was reporting the temperature of the first trip point instead of the temperature of critical trip point. For example: /sys/class/hwmon/hwmon0/temp1_crit:5

[PATCH] thermal: hwmon: Properly report critical temperature in sysfs

In the critical sysfs entry the thermal hwmon was returning wrong temperature to the user-space. It was reporting the temperature of the first trip point instead of the temperature of critical trip point. For example: /sys/class/hwmon/hwmon0/temp1_crit:5

[PATCH] driver core: add CLASS_ATTR_WO()

Some class subsystems are open-coding CLASS_ATTR_WO because the driver core never provided it. Add the macro to device.h so that we can go around and fix up the individual subsystems as needed. Signed-off-by: Greg Kroah-Hartman --- include/linux/device.h |2 ++

Re: net/can: use-after-free in bcm_rx_thr_flush

Hi Andrey, thanks for the report. Although I can't see the issue in the code ... On 11/22/2016 10:22 AM, Andrey Konovalov wrote: == BUG: KASAN: use-after-free in bcm_rx_thr_flush+0x284/0x2b0 Read of size 1 at addr

[PATCH] driver core: add CLASS_ATTR_WO()

Some class subsystems are open-coding CLASS_ATTR_WO because the driver core never provided it. Add the macro to device.h so that we can go around and fix up the individual subsystems as needed. Signed-off-by: Greg Kroah-Hartman --- include/linux/device.h |2 ++ 1 file changed, 2

Re: net/can: use-after-free in bcm_rx_thr_flush

Hi Andrey, thanks for the report. Although I can't see the issue in the code ... On 11/22/2016 10:22 AM, Andrey Konovalov wrote: == BUG: KASAN: use-after-free in bcm_rx_thr_flush+0x284/0x2b0 Read of size 1 at addr

Re: [PATCH 0/2] mmc: sdhci-pci: Use ACPI to set max frequency of sdio host

On 22 November 2016 at 17:37, Zach Brown wrote: > On Tue, Nov 22, 2016 at 09:27:29AM +0100, Ulf Hansson wrote: >> >> Please try to not forget to bump the version number and to provide a >> history of the what changes between revisions. It makes life easier >> when reviewing and

Re: [PATCH 5/10] dt: bindings: Add bindings for Marvell Xenon SD Host Controller

Hi Rob, On jeu., nov. 10 2016, Ziji Hu wrote: [...] >>> + >>> +- reg: >>> + * For "marvell,xenon-sdhci", one register area for Xenon IP. >>> + >>> + * For "marvell,armada-3700-sdhci", two register areas. >>> +The first one for Xenon IP register. The second one for

Re: What exactly do 32-bit x86 exceptions push on the stack in the CS slot?

On Tue, Nov 22, 2016 at 12:30 AM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> On Sun, Nov 20, 2016 at 11:13 PM, Ingo Molnar wrote: >> > >> > So I have applied your fix that addresses the worst fallout directly: >> > >> >

Re: [PATCH 0/2] mmc: sdhci-pci: Use ACPI to set max frequency of sdio host

On 22 November 2016 at 17:37, Zach Brown wrote: > On Tue, Nov 22, 2016 at 09:27:29AM +0100, Ulf Hansson wrote: >> >> Please try to not forget to bump the version number and to provide a >> history of the what changes between revisions. It makes life easier >> when reviewing and when I am about to

Re: [PATCH 5/10] dt: bindings: Add bindings for Marvell Xenon SD Host Controller

Hi Rob, On jeu., nov. 10 2016, Ziji Hu wrote: [...] >>> + >>> +- reg: >>> + * For "marvell,xenon-sdhci", one register area for Xenon IP. >>> + >>> + * For "marvell,armada-3700-sdhci", two register areas. >>> +The first one for Xenon IP register. The second one for the Armada >>> 3700

Re: What exactly do 32-bit x86 exceptions push on the stack in the CS slot?

On Tue, Nov 22, 2016 at 12:30 AM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> On Sun, Nov 20, 2016 at 11:13 PM, Ingo Molnar wrote: >> > >> > So I have applied your fix that addresses the worst fallout directly: >> > >> > fc0e81b2bea0 x86/traps: Ignore high word of regs->cs in >> >

Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function.

On Tue, Nov 22, 2016 at 12:23:59PM -0500, Rob Clark wrote: > On Tue, Nov 22, 2016 at 11:50 AM, Ville Syrjälä > wrote: > > On Tue, Nov 22, 2016 at 04:41:06PM +, Liviu Dudau wrote: > >> drm_get_format_name() de-references the buf parameter without checking > >> if

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

On Tue, Nov 08, 2016 at 12:07:55PM -0700, Stephen Warren wrote: > On 11/02/2016 04:48 AM, Suresh Mangipudi wrote: > > Add GPIO driver for T186 based platforms. > > Adds support for MAIN and AON GPIO's from T186. > > I'm not sure how you/Thierry will approach merging this with the other GPIO >

Re: [PATCH] x86: fix kaslr and memmap collision

[ replying for Dave since he's offline today and tomorrow ] On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote: > > * Dave Jiang wrote: > >> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address. >> However it does not take into account the

Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function.

On Tue, Nov 22, 2016 at 12:23:59PM -0500, Rob Clark wrote: > On Tue, Nov 22, 2016 at 11:50 AM, Ville Syrjälä > wrote: > > On Tue, Nov 22, 2016 at 04:41:06PM +, Liviu Dudau wrote: > >> drm_get_format_name() de-references the buf parameter without checking > >> if the pointer was not NULL.

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

On Tue, Nov 08, 2016 at 12:07:55PM -0700, Stephen Warren wrote: > On 11/02/2016 04:48 AM, Suresh Mangipudi wrote: > > Add GPIO driver for T186 based platforms. > > Adds support for MAIN and AON GPIO's from T186. > > I'm not sure how you/Thierry will approach merging this with the other GPIO >

Re: [PATCH] x86: fix kaslr and memmap collision

[ replying for Dave since he's offline today and tomorrow ] On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote: > > * Dave Jiang wrote: > >> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address. >> However it does not take into account the memmap= parameter passed in from >> the

Re: Linux 4.4.34

On Tue, Nov 22, 2016 at 06:22:47PM +0100, Andre Noll wrote: > On Tue, Nov 22, 18:06, Greg KH wrote > > On Tue, Nov 22, 2016 at 05:59:12PM +0100, Andre Noll wrote: > > > On Mon, Nov 21, 10:28, Greg KH wrote > > > > I'm announcing the release of the 4.4.34 kernel. > > > > > > > > All users of the

Applied "ASoC: samsung: Enable COMPILE_TEST for entire Samsung ASoc" to the asoc tree

The patch ASoC: samsung: Enable COMPILE_TEST for entire Samsung ASoc has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Is it a possible memory leak in CFQ?

Hi folks, When I create some big file (i.e. dd if=/dev/zero of=/home/test/big_file bs=1024k count=10240, then run sync, umount) with kmemleak enabled, kmemleak may report some memory leak occasionally. I would say it happens randomly. Please see the below log: unreferenced object

Re: Linux 4.4.34

On Tue, Nov 22, 2016 at 06:22:47PM +0100, Andre Noll wrote: > On Tue, Nov 22, 18:06, Greg KH wrote > > On Tue, Nov 22, 2016 at 05:59:12PM +0100, Andre Noll wrote: > > > On Mon, Nov 21, 10:28, Greg KH wrote > > > > I'm announcing the release of the 4.4.34 kernel. > > > > > > > > All users of the

Applied "ASoC: samsung: Enable COMPILE_TEST for entire Samsung ASoc" to the asoc tree

The patch ASoC: samsung: Enable COMPILE_TEST for entire Samsung ASoc has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Is it a possible memory leak in CFQ?

Hi folks, When I create some big file (i.e. dd if=/dev/zero of=/home/test/big_file bs=1024k count=10240, then run sync, umount) with kmemleak enabled, kmemleak may report some memory leak occasionally. I would say it happens randomly. Please see the below log: unreferenced object

Applied "ASoC: samsung: Remove non-existing MACH dependencies" to the asoc tree

The patch ASoC: samsung: Remove non-existing MACH dependencies has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: samsung: Enable COMPILE_TEST for SmartQ and WM8580" to the asoc tree

The patch ASoC: samsung: Enable COMPILE_TEST for SmartQ and WM8580 has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "spi: spi-fsl-dspi: Fix incorrect freeing of DMA allocated buffers" to the spi tree

The patch spi: spi-fsl-dspi: Fix incorrect freeing of DMA allocated buffers has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "spi: spi-fsl-dspi: Fix continuous selection format" to the spi tree

The patch spi: spi-fsl-dspi: Fix continuous selection format has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "spi: use sg_next for walking through the allocated scatterlist table" to the spi tree

The patch spi: use sg_next for walking through the allocated scatterlist table has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Re: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Fri, Nov 18, 2016 at 12:20:07PM +0100, Simon Guinot wrote: > On Fri, Nov 18, 2016 at 08:48:36AM +, Levy, Amir (Jer) wrote: > > On Tue, Nov 15 2016, 12:59 PM, Simon Guinot wrote: > > > On Wed, Nov 09, 2016 at 03:42:53PM +, Levy, Amir (Jer) wrote: > > > > On Wed, Nov 9 2016, 04:36 PM,

Re: [RFC][PATCH] x86: Verify access_ok() context

On Tue, Nov 22, 2016 at 1:57 AM, Peter Zijlstra wrote: > > I recently encountered wreckage because access_ok() was used where it > should not be, add an explicit WARN when access_ok() is used wrongly. > > Signed-off-by: Peter Zijlstra (Intel) > --- >

Re: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Fri, Nov 18, 2016 at 12:20:07PM +0100, Simon Guinot wrote: > On Fri, Nov 18, 2016 at 08:48:36AM +, Levy, Amir (Jer) wrote: > > On Tue, Nov 15 2016, 12:59 PM, Simon Guinot wrote: > > > On Wed, Nov 09, 2016 at 03:42:53PM +, Levy, Amir (Jer) wrote: > > > > On Wed, Nov 9 2016, 04:36 PM,

Applied "ASoC: samsung: Remove non-existing MACH dependencies" to the asoc tree

The patch ASoC: samsung: Remove non-existing MACH dependencies has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: samsung: Enable COMPILE_TEST for SmartQ and WM8580" to the asoc tree

The patch ASoC: samsung: Enable COMPILE_TEST for SmartQ and WM8580 has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "spi: spi-fsl-dspi: Fix incorrect freeing of DMA allocated buffers" to the spi tree

The patch spi: spi-fsl-dspi: Fix incorrect freeing of DMA allocated buffers has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "spi: spi-fsl-dspi: Fix continuous selection format" to the spi tree

The patch spi: spi-fsl-dspi: Fix continuous selection format has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "spi: use sg_next for walking through the allocated scatterlist table" to the spi tree

The patch spi: use sg_next for walking through the allocated scatterlist table has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Re: [RFC][PATCH] x86: Verify access_ok() context

On Tue, Nov 22, 2016 at 1:57 AM, Peter Zijlstra wrote: > > I recently encountered wreckage because access_ok() was used where it > should not be, add an explicit WARN when access_ok() is used wrongly. > > Signed-off-by: Peter Zijlstra (Intel) > --- > arch/x86/include/asm/uaccess.h | 7 +--

Re: Linux 4.4.34

On Tue, Nov 22, 2016 at 9:22 AM, Andre Noll wrote: > On Tue, Nov 22, 18:06, Greg KH wrote >> On Tue, Nov 22, 2016 at 05:59:12PM +0100, Andre Noll wrote: >> > On Mon, Nov 21, 10:28, Greg KH wrote >> > > I'm announcing the release of the 4.4.34 kernel. >> > > >> > > All users

Applied "spi: spi-fsl-dspi: Fix incorrect DMA setup" to the spi tree

The patch spi: spi-fsl-dspi: Fix incorrect DMA setup has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "spi: spi-topcliff-pch: Remove some dead code" to the spi tree

The patch spi: spi-topcliff-pch: Remove some dead code has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH] usb: gadget: uvc: fix returnvar.cocci warnings

Hi Andrzej and Julia, Could one of you please submit a patch to fix this ? On Thursday 17 Sep 2015 13:18:04 Andrzej Pietrasiewicz wrote: > Hi Julia, > > W dniu 17.09.2015 o 10:57, Julia Lawall pisze: > > Coccinelle suggests the following patch. But the code is curious. Is the > > function

Applied "ASoC: wm_adsp: Remove unused wm_coeff_ctl.kcontrol" to the asoc tree

The patch ASoC: wm_adsp: Remove unused wm_coeff_ctl.kcontrol has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: samsung: smdk_wm8580: Remove old platforms and drop mach-types usage" to the asoc tree

The patch ASoC: samsung: smdk_wm8580: Remove old platforms and drop mach-types usage has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in

Re: [PATCH v12 6/7] x86/arch_prctl: Add ARCH_[GET|SET]_CPUID

On Nov 21, 2016 12:27 AM, "Ingo Molnar" wrote: > > > * Thomas Gleixner wrote: > > > On Fri, 18 Nov 2016, Ingo Molnar wrote: > > > * Kyle Huey wrote: > > > > + if (test_tsk_thread_flag(prev_p, TIF_NOCPUID) ^ > > > > +

Applied "ASoC: samsung: smdk_wm8580: Remove old platforms and drop mach-types usage" to the asoc tree

The patch ASoC: samsung: smdk_wm8580: Remove old platforms and drop mach-types usage has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in

<    4   5   6   7   8   9   10   11   12   13   >