[PATCH] cciss: switch to pci_irq_alloc_vectors

Simple cleanup to use the new APIs. Signed-off-by: Christoph Hellwig --- drivers/block/cciss.c | 54 ++- drivers/block/cciss.h | 6 ++ 2 files changed, 17 insertions(+), 43 deletions(-) diff --git a/drivers/block/cciss.c

[PATCH] cciss: switch to pci_irq_alloc_vectors

Simple cleanup to use the new APIs. Signed-off-by: Christoph Hellwig --- drivers/block/cciss.c | 54 ++- drivers/block/cciss.h | 6 ++ 2 files changed, 17 insertions(+), 43 deletions(-) diff --git a/drivers/block/cciss.c

Re: [PATCH net-next v2 1/3] tools: Sync {,tools/}include/uapi/linux/bpf.h

Again, I need to see a proper "[PATCH net-next v2 0/3]" header posting explaining this series. Thanks.

Re: [PATCH net-next v2 1/3] tools: Sync {,tools/}include/uapi/linux/bpf.h

Again, I need to see a proper "[PATCH net-next v2 0/3]" header posting explaining this series. Thanks.

Re: [PATCH] [PATCH] Input: synaptics-rmi4 - select 'SERIO' when needed

On Tue, Feb 07, 2017 at 02:13:28PM +0100, Arnd Bergmann wrote: > With CONFIG_SERIO=m, we get a build error for the rmi4-f03 driver, > added in linux-4.10: > > warning: (HID_RMI) selects RMI4_F03 which has unmet direct dependencies (!UML > && INPUT && RMI4_CORE && (SERIO=y || RMI4_CORE=SERIO)) >

Re: [PATCH] [PATCH] Input: synaptics-rmi4 - select 'SERIO' when needed

On Tue, Feb 07, 2017 at 02:13:28PM +0100, Arnd Bergmann wrote: > With CONFIG_SERIO=m, we get a build error for the rmi4-f03 driver, > added in linux-4.10: > > warning: (HID_RMI) selects RMI4_F03 which has unmet direct dependencies (!UML > && INPUT && RMI4_CORE && (SERIO=y || RMI4_CORE=SERIO)) >

Re: [PATCH v2 1/5] bpf: Add missing header to the library

I don't see a proper "[PATCH v2 0/5] ..." posting, and I can't tell what tree you are targetting this series at.

Re: [PATCH v2 1/5] bpf: Add missing header to the library

I don't see a proper "[PATCH v2 0/5] ..." posting, and I can't tell what tree you are targetting this series at.

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 7, 2017 at 6:37 PM, James Bottomley wrote: > On Tue, 2017-02-07 at 01:19 -0800, Christoph Hellwig wrote: >> On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote: >> > This allows any subtree to be uid/gid shifted and bound elsewhere.

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 7, 2017 at 6:37 PM, James Bottomley wrote: > On Tue, 2017-02-07 at 01:19 -0800, Christoph Hellwig wrote: >> On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote: >> > This allows any subtree to be uid/gid shifted and bound elsewhere. >> > It does this by operating simlarly

Re: [PATCH 1/2] sierra_net: Add support for IPv6 and Dual-Stack Link Sense Indications

From: Stefan Brüns Date: Mon, 6 Feb 2017 21:20:33 +0100 > > /* Validate the protocol - only support UMTS for now */ > - if (lsi->protocol != SIERRA_NET_PROTOCOL_UMTS) { > + if (lsi->protocol == SIERRA_NET_PROTOCOL_UMTS) { ... > + } else if

Re: [PATCH 1/2] sierra_net: Add support for IPv6 and Dual-Stack Link Sense Indications

From: Stefan Brüns Date: Mon, 6 Feb 2017 21:20:33 +0100 > > /* Validate the protocol - only support UMTS for now */ > - if (lsi->protocol != SIERRA_NET_PROTOCOL_UMTS) { > + if (lsi->protocol == SIERRA_NET_PROTOCOL_UMTS) { ... > + } else if (lsi->protocol ==

[PATCH v2 2/4] ARM: pwm: sun4i: selectable prescaler table for support sun6i.

From: Siarhei Volkau This patch not introduce new features, just prepare code for adding sun6i PWM driver in next commit. A31 SoC have a different set of prescalers than others ASoCs, but its position and count in the control register are the same. This patch make the table

[PATCH v2 2/4] ARM: pwm: sun4i: selectable prescaler table for support sun6i.

From: Siarhei Volkau This patch not introduce new features, just prepare code for adding sun6i PWM driver in next commit. A31 SoC have a different set of prescalers than others ASoCs, but its position and count in the control register are the same. This patch make the table of prescalers

[PATCH v2 3/4] ARM: pwm: sun6i: add support the Allwinner A31 PWM.

From: Siarhei Volkau This patch introduce the sun6i PWM driver itself: - sun6i register operations, - sun6i prescaler table, - DT bindings for A31 SoC, - documentation update. Signed-off-by: Siarhei Volkau --- .../devicetree/bindings/pwm/pwm-sun4i.txt

[PATCH v2 3/4] ARM: pwm: sun6i: add support the Allwinner A31 PWM.

From: Siarhei Volkau This patch introduce the sun6i PWM driver itself: - sun6i register operations, - sun6i prescaler table, - DT bindings for A31 SoC, - documentation update. Signed-off-by: Siarhei Volkau --- .../devicetree/bindings/pwm/pwm-sun4i.txt | 3 +-

Re: [kernel-hardening] Re: [PATCH 4/4] refcount: Report failures through CHECK_DATA_CORRUPTION

On Tue, Feb 07, 2017 at 06:30:36PM +0100, Peter Zijlstra wrote: > On Tue, Feb 07, 2017 at 04:03:01PM +, Mark Rutland wrote: > > For x86 it's a little painful due to '%' in the register names, but it looks > > possible. The below appears to do the mangling correctly (then screams due > > to >

Re: [kernel-hardening] Re: [PATCH 4/4] refcount: Report failures through CHECK_DATA_CORRUPTION

On Tue, Feb 07, 2017 at 06:30:36PM +0100, Peter Zijlstra wrote: > On Tue, Feb 07, 2017 at 04:03:01PM +, Mark Rutland wrote: > > For x86 it's a little painful due to '%' in the register names, but it looks > > possible. The below appears to do the mangling correctly (then screams due > > to >

[PATCH v2 0/4] Add the Allwinner A31/A31s PWM driver

From: Siarhei Volkau First of all im sorry for accidentally sent old patch, please ignore them. This is the second version of the sun6i PWM patchset. - added missing documentation changes - dts changes in separate patch Thanks to Julian Calaby for tips.

[PATCH v2 0/4] Add the Allwinner A31/A31s PWM driver

From: Siarhei Volkau First of all im sorry for accidentally sent old patch, please ignore them. This is the second version of the sun6i PWM patchset. - added missing documentation changes - dts changes in separate patch Thanks to Julian Calaby for tips. -- This

Re: [PATCH v3 03/14] mm: use pmd lock instead of racy checks in zap_pmd_range()

On Tue, Feb 07, 2017 at 11:14:56AM -0600, Zi Yan wrote: > > > Kirill A. Shutemov wrote: > > On Tue, Feb 07, 2017 at 09:11:05AM -0600, Zi Yan wrote: > This causes memory leak or kernel crashing, if VM_BUG_ON() is enabled. > >>> The problem is that numabalancing calls change_huge_pmd() under

Re: [PATCH v3 03/14] mm: use pmd lock instead of racy checks in zap_pmd_range()

On Tue, Feb 07, 2017 at 11:14:56AM -0600, Zi Yan wrote: > > > Kirill A. Shutemov wrote: > > On Tue, Feb 07, 2017 at 09:11:05AM -0600, Zi Yan wrote: > This causes memory leak or kernel crashing, if VM_BUG_ON() is enabled. > >>> The problem is that numabalancing calls change_huge_pmd() under

[PATCH v2 4/4] ARM: dts: sun6i: Add the PWM block to the A31/A31s.

From: Siarhei Volkau Signed-off-by: Siarhei Volkau --- arch/arm/boot/dts/sun6i-a31.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi b/arch/arm/boot/dts/sun6i-a31.dtsi index ee1eb6d..fcba129 100644 ---

[PATCH v2 4/4] ARM: dts: sun6i: Add the PWM block to the A31/A31s.

From: Siarhei Volkau Signed-off-by: Siarhei Volkau --- arch/arm/boot/dts/sun6i-a31.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi b/arch/arm/boot/dts/sun6i-a31.dtsi index ee1eb6d..fcba129 100644 --- a/arch/arm/boot/dts/sun6i-a31.dtsi +++

Re: [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 01/24/2017 11:23 AM, Juergen Gross wrote: > On 24/01/17 14:47, Boris Ostrovsky wrote: >> On 01/23/2017 01:59 PM, Boris Ostrovsky wrote: >>> On 01/23/2017 05:09 AM, Juergen Gross wrote: Handling of multiple concurrent Xenstore accesses through xenbus driver either from the kernel or

Re: [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 01/24/2017 11:23 AM, Juergen Gross wrote: > On 24/01/17 14:47, Boris Ostrovsky wrote: >> On 01/23/2017 01:59 PM, Boris Ostrovsky wrote: >>> On 01/23/2017 05:09 AM, Juergen Gross wrote: Handling of multiple concurrent Xenstore accesses through xenbus driver either from the kernel or

Re: [PATCH v3 0/9] PVH v2 support (domU)

On 02/06/2017 12:00 PM, Boris Ostrovsky wrote: > PVHv2 support for unprivileged guests. > > Changes in v3: > * See patches 4 and 5 > Applied to for-linus-4.11 -boris

Re: [PATCH v3 0/9] PVH v2 support (domU)

On 02/06/2017 12:00 PM, Boris Ostrovsky wrote: > PVHv2 support for unprivileged guests. > > Changes in v3: > * See patches 4 and 5 > Applied to for-linus-4.11 -boris

[PATCH] ARC: [arcompact] brown paper bag bug in unaligned access delay slot fixup

Reported-by: Jo-Philipp Wich Fixes: 9aed02feae57bf7 ("ARC: [arcompact] handle unaligned access delay slot") Cc: linux-kernel@vger.kernel.org Cc: linux-snps-...@lists.infradead.org Cc: sta...@vger.kernel.org Signed-off-by: Vineet Gupta ---

[PATCH] ARC: [arcompact] brown paper bag bug in unaligned access delay slot fixup

Reported-by: Jo-Philipp Wich Fixes: 9aed02feae57bf7 ("ARC: [arcompact] handle unaligned access delay slot") Cc: linux-kernel@vger.kernel.org Cc: linux-snps-...@lists.infradead.org Cc: sta...@vger.kernel.org Signed-off-by: Vineet Gupta --- arch/arc/kernel/unaligned.c | 2 +- 1 file changed, 1

Re: rtlwifi: rtl8192c_common: "BUG: KASAN: slab-out-of-bounds"

On 07.02.2017 20:22, Tobias Guggenmos wrote: > Am Sonntag, 5. Februar 2017, 11:30:30 CET schrieb Larry Finger: >> On 02/05/2017 05:34 AM, Dmitry Osipenko wrote: >>> BTW, I have an issue with the 8192cu: WiFi stops to work after a while >>> (3-15 minutes) if I enable WMM QoS on the AP. There is

Re: rtlwifi: rtl8192c_common: "BUG: KASAN: slab-out-of-bounds"

On 07.02.2017 20:22, Tobias Guggenmos wrote: > Am Sonntag, 5. Februar 2017, 11:30:30 CET schrieb Larry Finger: >> On 02/05/2017 05:34 AM, Dmitry Osipenko wrote: >>> BTW, I have an issue with the 8192cu: WiFi stops to work after a while >>> (3-15 minutes) if I enable WMM QoS on the AP. There is

Re: [PATCH 1/6] KVM: vmx: clear pending interrupts on KVM_SET_LAPIC

2016-12-19 17:17+0100, Paolo Bonzini: > Pending interrupts might be in the PI descriptor when the > LAPIC is restored from an external state; we do not want > them to be injected. > > Signed-off-by: Paolo Bonzini > --- Reviewed-by: Radim Krčmář >

Re: [PATCH 1/6] KVM: vmx: clear pending interrupts on KVM_SET_LAPIC

2016-12-19 17:17+0100, Paolo Bonzini: > Pending interrupts might be in the PI descriptor when the > LAPIC is restored from an external state; we do not want > them to be injected. > > Signed-off-by: Paolo Bonzini > --- Reviewed-by: Radim Krčmář > arch/x86/kvm/lapic.c | 3 +-- >

[PATCH] Add the Allwinner A31/A31s PWM driver.

From: Siarhei Volkau A31 SoC have a different map of PWM registers than others Allwinner SoCs, so the operation of access to the registers reworked for all existing in driver SoCs. Tested on Onda V972 (a31) and Marsboard A20, but only PWM channel 0, because other channels

[PATCH] Add the Allwinner A31/A31s PWM driver.

From: Siarhei Volkau A31 SoC have a different map of PWM registers than others Allwinner SoCs, so the operation of access to the registers reworked for all existing in driver SoCs. Tested on Onda V972 (a31) and Marsboard A20, but only PWM channel 0, because other channels pins are not routed or

[PATCH] bfq-mq: cause deadlock by executing exit_icq body immediately

Hi, this patch is meant to show that, if the body of the hook exit_icq is executed from inside that hook, and not as deferred work, then a circular deadlock occurs. It happens if, on a CPU - the body of icq_exit takes the scheduler lock, - it does so from inside the exit_icq hook, which is

[PATCH] bfq-mq: cause deadlock by executing exit_icq body immediately

Hi, this patch is meant to show that, if the body of the hook exit_icq is executed from inside that hook, and not as deferred work, then a circular deadlock occurs. It happens if, on a CPU - the body of icq_exit takes the scheduler lock, - it does so from inside the exit_icq hook, which is

Re: [PATCH RESEND v7 2/2] Add support for OV5647 sensor.

Hi Ramiro, On Mon, Feb 06, 2017 at 11:38:28AM +, Ramiro Oliveira wrote: ... > >> + ret = ov5647_write_array(sd, ov5647_640x480, > >> + ARRAY_SIZE(ov5647_640x480)); > >> + if (ret < 0) { > >> + dev_err(>dev, "write sensor_default_regs error\n"); > >>

Re: [PATCH RESEND v7 2/2] Add support for OV5647 sensor.

Hi Ramiro, On Mon, Feb 06, 2017 at 11:38:28AM +, Ramiro Oliveira wrote: ... > >> + ret = ov5647_write_array(sd, ov5647_640x480, > >> + ARRAY_SIZE(ov5647_640x480)); > >> + if (ret < 0) { > >> + dev_err(>dev, "write sensor_default_regs error\n"); > >>

Re: [kernel-hardening] Re: [PATCH 4/4] refcount: Report failures through CHECK_DATA_CORRUPTION

On Tue, Feb 07, 2017 at 04:03:01PM +, Mark Rutland wrote: > For x86 it's a little painful due to '%' in the register names, but it looks > possible. The below appears to do the mangling correctly (then screams due to > the mangled result being nonexistent). > asm( > " .macro

Re: [kernel-hardening] Re: [PATCH 4/4] refcount: Report failures through CHECK_DATA_CORRUPTION

On Tue, Feb 07, 2017 at 04:03:01PM +, Mark Rutland wrote: > For x86 it's a little painful due to '%' in the register names, but it looks > possible. The below appears to do the mangling correctly (then screams due to > the mangled result being nonexistent). > asm( > " .macro

Re: memfill

Matthew Wilcox wrote: > You've misunderstood the purpose of memfill. memfill allows the caller > to specify a pattern which is not a single byte in size, eg memfill(addr, > 0x12345678, 64) would result in 0x12345678 being reproduced 16 times. > memset(addr, 0x12345678, 64)

Re: memfill

Matthew Wilcox wrote: > You've misunderstood the purpose of memfill. memfill allows the caller > to specify a pattern which is not a single byte in size, eg memfill(addr, > 0x12345678, 64) would result in 0x12345678 being reproduced 16 times. > memset(addr, 0x12345678, 64) would result in 0x78

Re: [PATCH v3 16/18] drivers/fsi: Add documentation for GPIO based FSI master

On Wed, Feb 01, 2017 at 10:53:56AM -0600, Christopher Bostic wrote: > From: Chris Bostic > > Define the device tree bindings for the GPIO master type. > > Signed-off-by: Chris Bostic > --- > .../devicetree/bindings/fsi/fsi-master-gpio.txt| 71 >

Re: [PATCH 7/8] mq-deadline: add blk-mq adaptation of the deadline IO scheduler

> Il giorno 02 feb 2017, alle ore 22:32, Jens Axboe ha scritto: > > On 02/02/2017 02:15 PM, Paolo Valente wrote: >> >>> Il giorno 02 feb 2017, alle ore 16:30, Jens Axboe ha scritto: >>> >>> On 02/02/2017 02:19 AM, Paolo Valente wrote: The scheme is clear.

Re: [PATCH v3 16/18] drivers/fsi: Add documentation for GPIO based FSI master

On Wed, Feb 01, 2017 at 10:53:56AM -0600, Christopher Bostic wrote: > From: Chris Bostic > > Define the device tree bindings for the GPIO master type. > > Signed-off-by: Chris Bostic > --- > .../devicetree/bindings/fsi/fsi-master-gpio.txt| 71 > ++ > 1 file changed,

Re: [PATCH 7/8] mq-deadline: add blk-mq adaptation of the deadline IO scheduler

> Il giorno 02 feb 2017, alle ore 22:32, Jens Axboe ha scritto: > > On 02/02/2017 02:15 PM, Paolo Valente wrote: >> >>> Il giorno 02 feb 2017, alle ore 16:30, Jens Axboe ha scritto: >>> >>> On 02/02/2017 02:19 AM, Paolo Valente wrote: The scheme is clear. One comment, in case it could

Re: [PATCH] arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling

On 06/02/17 22:21, Baicar, Tyler wrote: Hello Punit, On 2/3/2017 9:17 AM, Punit Agrawal wrote: Tyler Baicar writes: From: "Jonathan (Zhixiong) Zhang" Add VM_FAULT_HWPOISON[_LARGE] handling to the arm64 page fault handler. Handling of

Re: [PATCH] arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling

On 06/02/17 22:21, Baicar, Tyler wrote: Hello Punit, On 2/3/2017 9:17 AM, Punit Agrawal wrote: Tyler Baicar writes: From: "Jonathan (Zhixiong) Zhang" Add VM_FAULT_HWPOISON[_LARGE] handling to the arm64 page fault handler. Handling of VM_FAULT_HWPOISON[_LARGE] is very similar to

[WIP PATCHSET 2/4] Move thinktime from bic to bfqq

Prep change to make it possible to protect this field with a scheduler lock. Signed-off-by: Paolo Valente --- block/bfq-mq-iosched.c | 28 ++-- block/bfq-mq.h | 30 -- 2 files changed, 30 insertions(+), 28

[WIP PATCHSET 2/4] Move thinktime from bic to bfqq

Prep change to make it possible to protect this field with a scheduler lock. Signed-off-by: Paolo Valente --- block/bfq-mq-iosched.c | 28 ++-- block/bfq-mq.h | 30 -- 2 files changed, 30 insertions(+), 28 deletions(-) diff --git

[WIP PATCHSET 0/4] WIP branch for bfq-mq

Hi, I have finally pushed here [1] the current WIP branch of bfq for blk-mq, which I have tentatively named bfq-mq. This branch *IS NOT* meant for merging into mainline and contain code that mau easily violate code style, and not only, in many places. Commits implement the following main steps:

[WIP PATCHSET 0/4] WIP branch for bfq-mq

Hi, I have finally pushed here [1] the current WIP branch of bfq for blk-mq, which I have tentatively named bfq-mq. This branch *IS NOT* meant for merging into mainline and contain code that mau easily violate code style, and not only, in many places. Commits implement the following main steps:

[WIP PATCHSET 3/4] Embed bfq-ioc.c and add locking on request queue

The version of bfq-ioc.c for bfq-iosched.c is not correct any more for bfq-mq, because, in bfq-mq, the request queue lock is not being held when bfq_bic_lookup is invoked. That function must then take that look on its own. This commit removes the inclusion of bfq-ioc.c, copies the content of

[WIP PATCHSET 3/4] Embed bfq-ioc.c and add locking on request queue

The version of bfq-ioc.c for bfq-iosched.c is not correct any more for bfq-mq, because, in bfq-mq, the request queue lock is not being held when bfq_bic_lookup is invoked. That function must then take that look on its own. This commit removes the inclusion of bfq-ioc.c, copies the content of

[WIP PATCHSET 4/4] Modify interface and operation to comply with blk-mq-sched

As for modifications of the operation, the major changes are the introduction of a scheduler lock, and the moving to deferred work of the body of the hook exit_icq. The latter change has been made to avoid deadlocks caused by the combination of the following facts: 1) such a body takes the

[WIP PATCHSET 4/4] Modify interface and operation to comply with blk-mq-sched

As for modifications of the operation, the major changes are the introduction of a scheduler lock, and the moving to deferred work of the body of the hook exit_icq. The latter change has been made to avoid deadlocks caused by the combination of the following facts: 1) such a body takes the

[WIP PATCHSET 1/4] blk-mq: pass bio to blk_mq_sched_get_rq_priv

bio is used in bfq-mq's get_rq_priv, to get the request group. We could pass directly the group here, but I thought that passing the bio was more general, giving the possibility to get other pieces of information if needed. Signed-off-by: Paolo Valente ---

[WIP PATCHSET 1/4] blk-mq: pass bio to blk_mq_sched_get_rq_priv

bio is used in bfq-mq's get_rq_priv, to get the request group. We could pass directly the group here, but I thought that passing the bio was more general, giving the possibility to get other pieces of information if needed. Signed-off-by: Paolo Valente --- block/blk-mq-sched.c | 8 +---

Re: [PATCH v3 15/18] drivers/fsi: Add FSI bus documentation

On Wed, Feb 01, 2017 at 10:53:55AM -0600, Christopher Bostic wrote: > From: Chris Bostic > > Add details on the basic functions of the FSI serial bus. > > Signed-off-by: Chris Bostic > --- > Documentation/devicetree/bindings/fsi/fsi.txt | 54 >

Re: [PATCH v3 15/18] drivers/fsi: Add FSI bus documentation

On Wed, Feb 01, 2017 at 10:53:55AM -0600, Christopher Bostic wrote: > From: Chris Bostic > > Add details on the basic functions of the FSI serial bus. > > Signed-off-by: Chris Bostic > --- > Documentation/devicetree/bindings/fsi/fsi.txt | 54 > +++ > 1 file changed,

Re: [PATCH v2 0/6] KVM: x86: cleanup and speedup for APICv

On 19/12/2016 17:17, Paolo Bonzini wrote: > These are the fixed patches that now pass vmx.flat. The issue in > "KVM: x86: do not scan IRR twice on APICv vmentry" was that, > in v1 of the patches, kvm_cpu_get_interrupt did not scan IRR > at all if it found PIR.ON=0. This is now fixed in patches

Re: [PATCH v2 0/6] KVM: x86: cleanup and speedup for APICv

On 19/12/2016 17:17, Paolo Bonzini wrote: > These are the fixed patches that now pass vmx.flat. The issue in > "KVM: x86: do not scan IRR twice on APICv vmentry" was that, > in v1 of the patches, kvm_cpu_get_interrupt did not scan IRR > at all if it found PIR.ON=0. This is now fixed in patches

Re: memfill

On Tue, Feb 07, 2017 at 09:40:04AM +, David Howells wrote: > Matthew Wilcox wrote: > > > [adding linux-arch to see if anyone there wants to do an optimised > > version of memfill for their CPU] > > For mn10300, this is superfluous since the memset() implementation will

Re: memfill

On Tue, Feb 07, 2017 at 09:40:04AM +, David Howells wrote: > Matthew Wilcox wrote: > > > [adding linux-arch to see if anyone there wants to do an optimised > > version of memfill for their CPU] > > For mn10300, this is superfluous since the memset() implementation will do > optimised

Re: rtlwifi: rtl8192c_common: "BUG: KASAN: slab-out-of-bounds"

Am Sonntag, 5. Februar 2017, 11:30:30 CET schrieb Larry Finger: > On 02/05/2017 05:34 AM, Dmitry Osipenko wrote: > > BTW, I have an issue with the 8192cu: WiFi stops to work after a while > > (3-15 minutes) if I enable WMM QoS on the AP. There is nothing suspicious > > in KMSG, connection is up

Re: rtlwifi: rtl8192c_common: "BUG: KASAN: slab-out-of-bounds"

Am Sonntag, 5. Februar 2017, 11:30:30 CET schrieb Larry Finger: > On 02/05/2017 05:34 AM, Dmitry Osipenko wrote: > > BTW, I have an issue with the 8192cu: WiFi stops to work after a while > > (3-15 minutes) if I enable WMM QoS on the AP. There is nothing suspicious > > in KMSG, connection is up

Re: [PATCH] kvm: vmx: Use the hardware provided GPA instead of page walk

On 27/01/2017 19:34, Paolo Bonzini wrote: > As in the SVM patch, the guest physical address is passed by > VMX to x86_emulate_instruction already, so mark the GPA as available > in vcpu->arch. > > Signed-off-by: Paolo Bonzini > --- > arch/x86/kvm/vmx.c | 3 +++ > 1 file

Re: [PATCH] kvm: vmx: Use the hardware provided GPA instead of page walk

On 27/01/2017 19:34, Paolo Bonzini wrote: > As in the SVM patch, the guest physical address is passed by > VMX to x86_emulate_instruction already, so mark the GPA as available > in vcpu->arch. > > Signed-off-by: Paolo Bonzini > --- > arch/x86/kvm/vmx.c | 3 +++ > 1 file changed, 3 insertions(+)

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Mon, Feb 06 2017 at 9:49pm -0500, Kent Overstreet wrote: > On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote: > > On Mon, Feb 06, 2017 at 01:53:09PM +0100, Pavel Machek wrote: > > > Still there on v4.9, 36 threads on nokia n900 cellphone. > > > > > >

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Mon, Feb 06 2017 at 9:49pm -0500, Kent Overstreet wrote: > On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote: > > On Mon, Feb 06, 2017 at 01:53:09PM +0100, Pavel Machek wrote: > > > Still there on v4.9, 36 threads on nokia n900 cellphone. > > > > > > So.. what needs to be done

Re: a simple replacement for setuid and confinement systems

On 2/7/2017 5:09 AM, Peter Grandi wrote: > This message is "for the public record" so if in the future > someone tries to patent something like the below mechanism this > message can be cited as prior art. > > The mechanism would be to add to each process, along with its > "effective" id

Re: a simple replacement for setuid and confinement systems

On 2/7/2017 5:09 AM, Peter Grandi wrote: > This message is "for the public record" so if in the future > someone tries to patent something like the below mechanism this > message can be cited as prior art. > > The mechanism would be to add to each process, along with its > "effective" id

Re: [PATCH v3 03/14] mm: use pmd lock instead of racy checks in zap_pmd_range()

Kirill A. Shutemov wrote: > On Tue, Feb 07, 2017 at 09:11:05AM -0600, Zi Yan wrote: This causes memory leak or kernel crashing, if VM_BUG_ON() is enabled. >>> The problem is that numabalancing calls change_huge_pmd() under >>> down_read(mmap_sem), not down_write(mmap_sem) as the rest of

Re: [PATCH v3 03/14] mm: use pmd lock instead of racy checks in zap_pmd_range()

Kirill A. Shutemov wrote: > On Tue, Feb 07, 2017 at 09:11:05AM -0600, Zi Yan wrote: This causes memory leak or kernel crashing, if VM_BUG_ON() is enabled. >>> The problem is that numabalancing calls change_huge_pmd() under >>> down_read(mmap_sem), not down_write(mmap_sem) as the rest of

Re: [PATCH] mm, slab: rename kmalloc-node cache to kmalloc-

Hi Vlastimil, [auto build test WARNING on mmotm/master] [also build test WARNING on v4.10-rc7 next-20170207] [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/commits/Vlastimil-Babka/mm-slab-rename

Re: [PATCH] mm, slab: rename kmalloc-node cache to kmalloc-

Hi Vlastimil, [auto build test WARNING on mmotm/master] [also build test WARNING on v4.10-rc7 next-20170207] [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/commits/Vlastimil-Babka/mm-slab-rename

Re: rtlwifi: rtl8192c_common: "BUG: KASAN: slab-out-of-bounds"

On 07.02.2017 19:45, Tobias Guggenmos wrote: > Am Montag, 6. Februar 2017, 09:45:31 CET schrieb Larry Finger: >> On 02/06/2017 04:29 AM, Johannes Berg wrote: >>> On Sat, 2017-02-04 at 12:41 -0600, Larry Finger wrote: On 02/04/2017 10:58 AM, Dmitry Osipenko wrote: > Seems the problem is

Re: rtlwifi: rtl8192c_common: "BUG: KASAN: slab-out-of-bounds"

On 07.02.2017 19:45, Tobias Guggenmos wrote: > Am Montag, 6. Februar 2017, 09:45:31 CET schrieb Larry Finger: >> On 02/06/2017 04:29 AM, Johannes Berg wrote: >>> On Sat, 2017-02-04 at 12:41 -0600, Larry Finger wrote: On 02/04/2017 10:58 AM, Dmitry Osipenko wrote: > Seems the problem is

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Tue, Feb 07, 2017 at 09:02:51AM -0800, James Bottomley wrote: > On Tue, 2017-02-07 at 07:59 +0100, Willy Tarreau wrote: > > Hi James, > > > > On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > > > On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: > > (...) > > > > We

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Tue, Feb 07, 2017 at 09:02:51AM -0800, James Bottomley wrote: > On Tue, 2017-02-07 at 07:59 +0100, Willy Tarreau wrote: > > Hi James, > > > > On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > > > On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: > > (...) > > > > We

Re: [PATCH] slub: make sysfs directories for memcg sub-caches optional

Hello, Andrew. On Mon, Feb 06, 2017 at 04:22:13PM -0800, Andrew Morton wrote: > > #ifdef CONFIG_MEMCG > > - if (is_root_cache(s)) { > > + if (is_root_cache(s) && memcg_sysfs_enabled) { > > This could be turned on and off after bootup but I guess the result > could be pretty confusing. > >

Re: [PATCH] slub: make sysfs directories for memcg sub-caches optional

Hello, Andrew. On Mon, Feb 06, 2017 at 04:22:13PM -0800, Andrew Morton wrote: > > #ifdef CONFIG_MEMCG > > - if (is_root_cache(s)) { > > + if (is_root_cache(s) && memcg_sysfs_enabled) { > > This could be turned on and off after bootup but I guess the result > could be pretty confusing. > >

Re: [PATCH -next] tpm_tis: fix the error handling of init_tis()

On Tue, Feb 07, 2017 at 03:51:47PM +, Wei Yongjun wrote: > From: Wei Yongjun > > Add the missing platform_driver_unregister() and remove the duplicate > platform_device_unregister(force_pdev) in the error handling case. > > Fixes: 00194826e6be ("tpm_tis: Clean up the

Re: [PATCH -next] tpm_tis: fix the error handling of init_tis()

On Tue, Feb 07, 2017 at 03:51:47PM +, Wei Yongjun wrote: > From: Wei Yongjun > > Add the missing platform_driver_unregister() and remove the duplicate > platform_device_unregister(force_pdev) in the error handling case. > > Fixes: 00194826e6be ("tpm_tis: Clean up the force=1 module

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Tue, 2017-02-07 at 07:59 +0100, Willy Tarreau wrote: > Hi James, > > On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > > On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: > (...) > > > We don't have the referenced commit above in 3.10 so we should be > > > safe.

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Tue, 2017-02-07 at 07:59 +0100, Willy Tarreau wrote: > Hi James, > > On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > > On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: > (...) > > > We don't have the referenced commit above in 3.10 so we should be > > > safe.

Re: mm: deadlock between get_online_cpus/pcpu_alloc

Hello, Sorry about the delay. On Tue, Feb 07, 2017 at 04:34:59PM +0100, Michal Hocko wrote: > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index c3358d4f7932..b6411816787a 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -2343,7 +2343,16 @@ void drain_local_pages(struct zone

Re: mm: deadlock between get_online_cpus/pcpu_alloc

Hello, Sorry about the delay. On Tue, Feb 07, 2017 at 04:34:59PM +0100, Michal Hocko wrote: > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index c3358d4f7932..b6411816787a 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -2343,7 +2343,16 @@ void drain_local_pages(struct zone

Re: ARM imx.6 SATA speed regression

Thankfully there is an archive of older Arch ARM packages which should reduce the amount amount of bisection / compiling I may need to do and they have packages for most stable kernels between 4.9.0 and 4.9.8 http://tardis.tiny-vps.com/aarm/packages/l/linux-armv7/ On Tue, Feb 7, 2017 at 3:45 PM,

Re: ARM imx.6 SATA speed regression

Thankfully there is an archive of older Arch ARM packages which should reduce the amount amount of bisection / compiling I may need to do and they have packages for most stable kernels between 4.9.0 and 4.9.8 http://tardis.tiny-vps.com/aarm/packages/l/linux-armv7/ On Tue, Feb 7, 2017 at 3:45 PM,

Re: [PATCH v2 1/2] mfd: lpc_ich: Enable watchdog on Intel Apollo Lake PCH

On Sat, 28 Jan 2017, Andy Shevchenko wrote: > From: Tan Jui Nee > > Assign iTCO_version which effectively enables watchdog device on > Intel Apollo Lake PCH. > > Signed-off-by: Tan Jui Nee > Signed-off-by: Andy Shevchenko

Re: [PATCH v2 1/2] mfd: lpc_ich: Enable watchdog on Intel Apollo Lake PCH

On Sat, 28 Jan 2017, Andy Shevchenko wrote: > From: Tan Jui Nee > > Assign iTCO_version which effectively enables watchdog device on > Intel Apollo Lake PCH. > > Signed-off-by: Tan Jui Nee > Signed-off-by: Andy Shevchenko > --- > drivers/mfd/lpc_ich.c | 1 + > 1 file changed, 1 insertion(+)

[PATCH] perf stat: balance opening and closing of events

In create_perf_stat_counter(), we open events on a potentially per-cpu or per-thread basis, depending on if we have a target CPU list. The number of FDs we allocate depends on whether we're in per-thread or per-cpu mode. Subsequently, we close events using perf_evlist__close(), which assumes that

[PATCH] perf stat: balance opening and closing of events

In create_perf_stat_counter(), we open events on a potentially per-cpu or per-thread basis, depending on if we have a target CPU list. The number of FDs we allocate depends on whether we're in per-thread or per-cpu mode. Subsequently, we close events using perf_evlist__close(), which assumes that

Re: [PATCH v2 2/2] mfd: lpc_ich: Remove useless comments in core part

On Sat, 28 Jan 2017, Andy Shevchenko wrote: > First of all, remove stalled references to datasheets. If someone knows > the document numbers, it would be added later. > > Second, remove FSF snail address since it's subject to change. Actual > information can be found on FSF site on the internet.

Re: [PATCH v2 2/2] mfd: lpc_ich: Remove useless comments in core part

On Sat, 28 Jan 2017, Andy Shevchenko wrote: > First of all, remove stalled references to datasheets. If someone knows > the document numbers, it would be added later. > > Second, remove FSF snail address since it's subject to change. Actual > information can be found on FSF site on the internet.

Re: [RFC PATCH 1/2] mm, vmscan: account the number of isolated pages per zone

On Tue, Feb 07, 2017 at 07:30:54PM +0900, Tetsuo Handa wrote: > Brian Foster wrote: > > > The workload is to write to a single file on XFS from 10 processes > > > demonstrated at > > > http://lkml.kernel.org/r/201512052133.iae00551.lsoqftmffvo...@i-love.sakura.ne.jp > > > using "while :; do

Re: [RFC PATCH 1/2] mm, vmscan: account the number of isolated pages per zone

On Tue, Feb 07, 2017 at 07:30:54PM +0900, Tetsuo Handa wrote: > Brian Foster wrote: > > > The workload is to write to a single file on XFS from 10 processes > > > demonstrated at > > > http://lkml.kernel.org/r/201512052133.iae00551.lsoqftmffvo...@i-love.sakura.ne.jp > > > using "while :; do

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