[PATCH 0/6] Use build registers for getting numbers of interrupts

A summary: * Use build registers for getting numbers of interrupts both for core interrupt controller and for IDU interrupt controller. * Set a default priority for all core interrupt to prevent unexpected switching of banks of registers. * Remove option for setting number of

[PATCH 4/6] ARCv2: IRQ: Remove option for setting number of interrupts

When you set a value of ARC_NUMBER_OF_INTERRUPTS option it affects only a size of the interrupts table but macros for number of virtual interrupts (NR_IRQS) and for number of hardware interrupts (NR_CPU_IRQS) remain unchanged. Moreover usage of ARC_NUMBER_OF_INTERRUPTS is bad for portability since

[PATCH 6/6] ARCv2: IRQ: Set a default priority for all core interrupts

After reset all interrupts in the core interrupt controller has the highest priority P0. If the platform supports Fast IRQs and has more than 1 banks of registers then CPU automatically switch banks of registers when P0 interrupt comes. The problem is that the kernel expects that by default

[PATCH 6/6] ARCv2: IRQ: Set a default priority for all core interrupts

After reset all interrupts in the core interrupt controller has the highest priority P0. If the platform supports Fast IRQs and has more than 1 banks of registers then CPU automatically switch banks of registers when P0 interrupt comes. The problem is that the kernel expects that by default

[PATCH 2/6] ARCv2: MCIP: Add structure for build register of IDU

This structure is necessary for retrieving of supported number of common interrupts in IDU interrupt controller. Signed-off-by: Yuriy Kolerov --- include/soc/arc/mcip.h | 17 + 1 file changed, 17 insertions(+) diff --git a/include/soc/arc/mcip.h

[PATCH 2/6] ARCv2: MCIP: Add structure for build register of IDU

This structure is necessary for retrieving of supported number of common interrupts in IDU interrupt controller. Signed-off-by: Yuriy Kolerov --- include/soc/arc/mcip.h | 17 + 1 file changed, 17 insertions(+) diff --git a/include/soc/arc/mcip.h b/include/soc/arc/mcip.h index

Re: [PATCH 1/1] percpu-refcount: fix reference leak during percpu-atomic transition

I'd like to request this be flagged for "stable". Thanks, Doug On 01/27/2017 02:59 PM, Douglas Miller wrote: percpu_ref_tryget() and percpu_ref_tryget_live() should return "true" IFF they acquire a reference. But the return value from atomic_long_inc_not_zero() is a long and may have high

[PATCH 5/6] ARCv2: IRQ: Use build registers for getting numbers of interrupts

This enhancement allows to mask all available common interrupts in IDU interrupt controller in boot time since the kernel can discover a number of them from the build register. Also now there is no need to specify in device tree a list of used core interrupts by IDU. E.g. before: idu_intc:

Re: [PATCH v4] net: ethernet: faraday: To support device tree usage.

On Wed, Jan 25, 2017 at 10:09:20PM +0100, Arnd Bergmann wrote: > On Wed, Jan 25, 2017 at 6:34 PM, David Miller wrote: > > From: Greentime Hu > > Date: Tue, 24 Jan 2017 16:46:14 +0800 > >> We also use the same binding document to describe the same faraday

Re: [PATCH 1/1] percpu-refcount: fix reference leak during percpu-atomic transition

I'd like to request this be flagged for "stable". Thanks, Doug On 01/27/2017 02:59 PM, Douglas Miller wrote: percpu_ref_tryget() and percpu_ref_tryget_live() should return "true" IFF they acquire a reference. But the return value from atomic_long_inc_not_zero() is a long and may have high

[PATCH 5/6] ARCv2: IRQ: Use build registers for getting numbers of interrupts

This enhancement allows to mask all available common interrupts in IDU interrupt controller in boot time since the kernel can discover a number of them from the build register. Also now there is no need to specify in device tree a list of used core interrupts by IDU. E.g. before: idu_intc:

Re: [PATCH v4] net: ethernet: faraday: To support device tree usage.

On Wed, Jan 25, 2017 at 10:09:20PM +0100, Arnd Bergmann wrote: > On Wed, Jan 25, 2017 at 6:34 PM, David Miller wrote: > > From: Greentime Hu > > Date: Tue, 24 Jan 2017 16:46:14 +0800 > >> We also use the same binding document to describe the same faraday ethernet > >> controller and add faraday

[PATCH] docs: Convert the regulator docbook to RST

A fairly straightforward conversion to RST; the document is then added to the driver-api manual. Of course, this document has seen no substantive changes since 2008, so chances are it needs work in other areas as well. Cc: Mark Brown Signed-off-by: Jonathan Corbet

[PATCH] docs: Convert the regulator docbook to RST

A fairly straightforward conversion to RST; the document is then added to the driver-api manual. Of course, this document has seen no substantive changes since 2008, so chances are it needs work in other areas as well. Cc: Mark Brown Signed-off-by: Jonathan Corbet --- The formatted version of

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, 2017-01-27 at 16:35 -0700, Jason Gunthorpe wrote: > On Fri, Jan 27, 2017 at 02:04:59PM -0800, James Bottomley wrote: > > > if I look at the code I've written, I don't know what the session > > number is, I just save sessionHandle in a variable for later use > > (lets say to v1). If I

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, 2017-01-27 at 16:35 -0700, Jason Gunthorpe wrote: > On Fri, Jan 27, 2017 at 02:04:59PM -0800, James Bottomley wrote: > > > if I look at the code I've written, I don't know what the session > > number is, I just save sessionHandle in a variable for later use > > (lets say to v1). If I

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, Jan 27, 2017 at 02:04:59PM -0800, James Bottomley wrote: > if I look at the code I've written, I don't know what the session > number is, I just save sessionHandle in a variable for later use (lets > say to v1). If I got the same session number returned at a later time > and placed it in

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, Jan 27, 2017 at 02:04:59PM -0800, James Bottomley wrote: > if I look at the code I've written, I don't know what the session > number is, I just save sessionHandle in a variable for later use (lets > say to v1). If I got the same session number returned at a later time > and placed it in

Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.

Hi, On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > Ok, I can try. But so far even -rc1 is a lot of fun. But... I consider > phone calls core feature of a phone. I'd very much like to get that to > work. Unfortunately, that means real-time audio, and a lot of > fun. Plus, as it is

Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.

Hi, On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > Ok, I can try. But so far even -rc1 is a lot of fun. But... I consider > phone calls core feature of a phone. I'd very much like to get that to > work. Unfortunately, that means real-time audio, and a lot of > fun. Plus, as it is

Re: [PATCH v8 09/12] dt-bindings: mux-adg792a: document devicetree bindings for ADG792A/G mux

On 2017-01-27 20:50, Rob Herring wrote: > On Wed, Jan 18, 2017 at 04:57:12PM +0100, Peter Rosin wrote: >> Analog Devices ADG792A/G is a triple 4:1 mux. >> >> Acked-by: Jonathan Cameron >> Signed-off-by: Peter Rosin >> --- >>

Re: [PATCH v8 09/12] dt-bindings: mux-adg792a: document devicetree bindings for ADG792A/G mux

On 2017-01-27 20:50, Rob Herring wrote: > On Wed, Jan 18, 2017 at 04:57:12PM +0100, Peter Rosin wrote: >> Analog Devices ADG792A/G is a triple 4:1 mux. >> >> Acked-by: Jonathan Cameron >> Signed-off-by: Peter Rosin >> --- >> .../devicetree/bindings/mux/mux-adg792a.txt| 79 >>

Re: net: suspicious RCU usage in nf_hook

On Fri, 2017-01-27 at 22:15 +0100, Dmitry Vyukov wrote: > Hello, > > I've got the following report while running syzkaller fuzzer on > fd694aaa46c7ed811b72eb47d5eb11ce7ab3f7f1: > > [ INFO: suspicious RCU usage. ] > 4.10.0-rc5+ #192 Not tainted > --- >

Re: net: suspicious RCU usage in nf_hook

On Fri, 2017-01-27 at 22:15 +0100, Dmitry Vyukov wrote: > Hello, > > I've got the following report while running syzkaller fuzzer on > fd694aaa46c7ed811b72eb47d5eb11ce7ab3f7f1: > > [ INFO: suspicious RCU usage. ] > 4.10.0-rc5+ #192 Not tainted > --- >

Re: ibmvtpm byteswapping inconsistency

On 01/27/2017 11:58 AM, Benjamin Herrenschmidt wrote: > On Fri, 2017-01-27 at 10:02 -0800, Tyrel Datwyler wrote: >>> The problem is that we are packing an in-memory structure into 2 >>> registers and it's expected that this structure is laid out in the >>> registers as if it had been loaded by a

Re: ibmvtpm byteswapping inconsistency

On 01/27/2017 11:58 AM, Benjamin Herrenschmidt wrote: > On Fri, 2017-01-27 at 10:02 -0800, Tyrel Datwyler wrote: >>> The problem is that we are packing an in-memory structure into 2 >>> registers and it's expected that this structure is laid out in the >>> registers as if it had been loaded by a

Re: [PATCH V3 net-next 02/14] net/ena: fix error handling when probe fails

Hi, On 26.01.2017 23:18, Netanel Belgazal wrote: When driver fails in probe, it will release all resources, including adapter. In case of probe failure, ena_remove should not try to free the adapter resources. Signed-off-by: Netanel Belgazal ---

Re: [PATCH V3 net-next 02/14] net/ena: fix error handling when probe fails

Hi, On 26.01.2017 23:18, Netanel Belgazal wrote: When driver fails in probe, it will release all resources, including adapter. In case of probe failure, ena_remove should not try to free the adapter resources. Signed-off-by: Netanel Belgazal --- drivers/net/ethernet/amazon/ena/ena_netdev.c |

Re: net: suspicious RCU usage in nf_hook

On Fri, Jan 27, 2017 at 3:22 PM, Cong Wang wrote: > On Fri, Jan 27, 2017 at 1:15 PM, Dmitry Vyukov wrote: >> stack backtrace: >> CPU: 2 PID: 23111 Comm: syz-executor14 Not tainted 4.10.0-rc5+ #192 >> Hardware name: QEMU Standard PC (i440FX + PIIX,

Re: net: suspicious RCU usage in nf_hook

On Fri, Jan 27, 2017 at 3:22 PM, Cong Wang wrote: > On Fri, Jan 27, 2017 at 1:15 PM, Dmitry Vyukov wrote: >> stack backtrace: >> CPU: 2 PID: 23111 Comm: syz-executor14 Not tainted 4.10.0-rc5+ #192 >> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 >> Call Trace: >>

[PATCH] x86: Improve documentation for low-level device I/O functions

Add kerneldoc comments for memcpy_{to,from}io() and memset_io(). The existing documentation for ioremap() was distant from the definition, causing kernel-doc to miss it; move it appropriately. Signed-off-by: Jonathan Corbet --- arch/x86/include/asm/io.h | 47

[PATCH] x86: Improve documentation for low-level device I/O functions

Add kerneldoc comments for memcpy_{to,from}io() and memset_io(). The existing documentation for ioremap() was distant from the definition, causing kernel-doc to miss it; move it appropriately. Signed-off-by: Jonathan Corbet --- arch/x86/include/asm/io.h | 47

[PATCH] Convert the deviceio template to RST

Convert deviceiobook.tmpl to RST and incorporate it into the driver API manual. Like the rest of our documentation, this one could use some work. There's no mention of ioremap() and friends, no mention of io_read*() and friends. But we have nice documentation for all those folks writing new

[PATCH] Convert the deviceio template to RST

Convert deviceiobook.tmpl to RST and incorporate it into the driver API manual. Like the rest of our documentation, this one could use some work. There's no mention of ioremap() and friends, no mention of io_read*() and friends. But we have nice documentation for all those folks writing new

Re: net: suspicious RCU usage in nf_hook

On Fri, Jan 27, 2017 at 1:15 PM, Dmitry Vyukov wrote: > stack backtrace: > CPU: 2 PID: 23111 Comm: syz-executor14 Not tainted 4.10.0-rc5+ #192 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:15

Re: net: suspicious RCU usage in nf_hook

On Fri, Jan 27, 2017 at 1:15 PM, Dmitry Vyukov wrote: > stack backtrace: > CPU: 2 PID: 23111 Comm: syz-executor14 Not tainted 4.10.0-rc5+ #192 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:15 [inline] >

ATENCIÓN

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

ATENCIÓN

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

[PATCH v2 5/5] userfaultfd_copy: return -ENOSPC in case mm has gone

In the non-cooperative userfaultfd case, the process exit may race with outstanding mcopy_atomic called by the uffd monitor. Returning -ENOSPC instead of -EINVAL when mm is already gone will allow uffd monitor to distinguish this case from other error conditions. Signed-off-by: Mike Rapoport

[PATCH v2 5/5] userfaultfd_copy: return -ENOSPC in case mm has gone

In the non-cooperative userfaultfd case, the process exit may race with outstanding mcopy_atomic called by the uffd monitor. Returning -ENOSPC instead of -EINVAL when mm is already gone will allow uffd monitor to distinguish this case from other error conditions. Signed-off-by: Mike Rapoport

Re: [PATCH 1/2] dt-bindings: Document the VC4 DSI module nodes.

Need to cc DT list if you want it in my queue. On Mon, Jan 23, 2017 at 6:38 PM, Eric Anholt wrote: > These are part of the vc4 display pipeline. > > Signed-off-by: Eric Anholt > --- > .../devicetree/bindings/display/brcm,bcm-vc4.txt | 35 >

Re: [PATCH 1/2] dt-bindings: Document the VC4 DSI module nodes.

Need to cc DT list if you want it in my queue. On Mon, Jan 23, 2017 at 6:38 PM, Eric Anholt wrote: > These are part of the vc4 display pipeline. > > Signed-off-by: Eric Anholt > --- > .../devicetree/bindings/display/brcm,bcm-vc4.txt | 35 > ++ > 1 file changed, 35

Re: [PATCH] wd719x: add check for dma mapping errors

On Sat, 2017-01-28 at 01:30 +0300, Alexey Khoroshilov wrote: > wd719x_queuecommand() doesn't check if mapping dma memory succeed. > The patch adds the check and failure handling. > > Found by Linux Driver Verification project (linuxtesting.org). > > Signed-off-by: Alexey Khoroshilov

Re: [PATCH] wd719x: add check for dma mapping errors

On Sat, 2017-01-28 at 01:30 +0300, Alexey Khoroshilov wrote: > wd719x_queuecommand() doesn't check if mapping dma memory succeed. > The patch adds the check and failure handling. > > Found by Linux Driver Verification project (linuxtesting.org). > > Signed-off-by: Alexey Khoroshilov > --- >

[PATCH v2 4/5] userfaultfd: mcopy_atomic: return -ENOENT when no compatible VMA found

The memory mapping of a process may change between #PF event and the call to mcopy_atomic that comes to resolve the page fault. In such case, there will be no VMA covering the range passed to mcopy_atomic or the VMA will not have userfaultfd context. To allow uffd monitor to distinguish those case

[PATCH v2 4/5] userfaultfd: mcopy_atomic: return -ENOENT when no compatible VMA found

The memory mapping of a process may change between #PF event and the call to mcopy_atomic that comes to resolve the page fault. In such case, there will be no VMA covering the range passed to mcopy_atomic or the VMA will not have userfaultfd context. To allow uffd monitor to distinguish those case

[PATCH v2 1/5] mm: call vm_munmap in munmap syscall instead of using open coded version

The commit dc0ef0df7b6a (mm: make mmap_sem for write waits killable for mm syscalls) replaced call to vm_munmap in munmap syscall with open coded version to allow different waits on mmap_sem in munmap syscall and vm_munmap. Now both functions use down_write_killable, so we can restore the call to

[PATCH v2 1/5] mm: call vm_munmap in munmap syscall instead of using open coded version

The commit dc0ef0df7b6a (mm: make mmap_sem for write waits killable for mm syscalls) replaced call to vm_munmap in munmap syscall with open coded version to allow different waits on mmap_sem in munmap syscall and vm_munmap. Now both functions use down_write_killable, so we can restore the call to

Re: [PATCH] prctl.2: Document new PR_SET_CHILD_SUBREAPER semantics

Hello Pavel, On 27 January 2017 at 23:11, Pavel Tikhomirov wrote: > old semantics was non deterministic and worked differently > depending on the external factors, but nothing changes if > process first sets itself subreaper and only after forks When did the kernel

Re: [PATCH] prctl.2: Document new PR_SET_CHILD_SUBREAPER semantics

Hello Pavel, On 27 January 2017 at 23:11, Pavel Tikhomirov wrote: > old semantics was non deterministic and worked differently > depending on the external factors, but nothing changes if > process first sets itself subreaper and only after forks When did the kernel behavior change? Cheers,

Extra messages from Makefile.sphinx

On a sphinx-free Ubuntu system with 4.10-rc5, make installmandocs works just fine, but the garrulous Makefile.sphinx twice tells me I don't have sphinx-build installed: Documentation/Makefile.sphinx:22: The 'sphinx-build' command was not found. Make sure you have Sphinx installed and in PATH, or

Extra messages from Makefile.sphinx

On a sphinx-free Ubuntu system with 4.10-rc5, make installmandocs works just fine, but the garrulous Makefile.sphinx twice tells me I don't have sphinx-build installed: Documentation/Makefile.sphinx:22: The 'sphinx-build' command was not found. Make sure you have Sphinx installed and in PATH, or

Re: [PATCH v2 1/2] Documentation: mtk-quadspi: update DT bindings

On Wed, Jan 25, 2017 at 11:38:34AM +0800, Guochun Mao wrote: > Add "mediatek,mt2701-nor" for nor flash node's compatible. > > Signed-off-by: Guochun Mao > --- > .../devicetree/bindings/mtd/mtk-quadspi.txt|8 +++- > 1 file changed, 7 insertions(+), 1

Re: [PATCH v2 1/2] Documentation: mtk-quadspi: update DT bindings

On Wed, Jan 25, 2017 at 11:38:34AM +0800, Guochun Mao wrote: > Add "mediatek,mt2701-nor" for nor flash node's compatible. > > Signed-off-by: Guochun Mao > --- > .../devicetree/bindings/mtd/mtk-quadspi.txt|8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) Acked-by: Rob

Re: [REGRESSION] EFI mixed mode patch triggers boot failure

On Mon, 24 Oct, at 12:54:11PM, Laura Abbott wrote: > > Was out for a few days, reporter says the below patch does not work. > There was some confusion with secure boot so I've asked them to re-test > with efi=old_map and secure boot off. FYI, you may want to ask the reporter to try out Jiri's

Re: [REGRESSION] EFI mixed mode patch triggers boot failure

On Mon, 24 Oct, at 12:54:11PM, Laura Abbott wrote: > > Was out for a few days, reporter says the below patch does not work. > There was some confusion with secure boot so I've asked them to re-test > with efi=old_map and secure boot off. FYI, you may want to ask the reporter to try out Jiri's

[PATCH] wd719x: add check for dma mapping errors

wd719x_queuecommand() doesn't check if mapping dma memory succeed. The patch adds the check and failure handling. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/scsi/wd719x.c | 6 ++ 1 file changed, 6

[PATCH] wd719x: add check for dma mapping errors

wd719x_queuecommand() doesn't check if mapping dma memory succeed. The patch adds the check and failure handling. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/scsi/wd719x.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [PATCH v9 1/3] doc: dt: add cyclone-ps-spi binding document

On Tue, Jan 24, 2017 at 02:19:32PM -0800, Joshua Clayton wrote: > Describe a cyclone-ps-spi devicetree entry, required features > > Signed-off-by: Joshua Clayton > --- > .../bindings/fpga/altera-passive-serial.txt| 29 > ++ > 1 file

Re: [PATCH v9 1/3] doc: dt: add cyclone-ps-spi binding document

On Tue, Jan 24, 2017 at 02:19:32PM -0800, Joshua Clayton wrote: > Describe a cyclone-ps-spi devicetree entry, required features > > Signed-off-by: Joshua Clayton > --- > .../bindings/fpga/altera-passive-serial.txt| 29 > ++ > 1 file changed, 29 insertions(+) >

Re: [PATCH 6/6] staging: bcm2835-v4l2: Apply spelling fixes from checkpatch.

On Fri, 2017-01-27 at 13:55 -0800, Eric Anholt wrote: > Generated with checkpatch.pl --fix-inplace and git add -p out of the > results. Maybe another. > diff --git a/drivers/staging/media/platform/bcm2835/mmal-vchiq.c > b/drivers/staging/media/platform/bcm2835/mmal-vchiq.c [] > @@ -239,7 +239,7

Re: [PATCH 6/6] staging: bcm2835-v4l2: Apply spelling fixes from checkpatch.

On Fri, 2017-01-27 at 13:55 -0800, Eric Anholt wrote: > Generated with checkpatch.pl --fix-inplace and git add -p out of the > results. Maybe another. > diff --git a/drivers/staging/media/platform/bcm2835/mmal-vchiq.c > b/drivers/staging/media/platform/bcm2835/mmal-vchiq.c [] > @@ -239,7 +239,7

[PATCH] x86/efi: Always map first physical page into EFI pagetables

From: Jiri Kosina Commit 129766708 ("x86/efi: Only map RAM into EFI page tables if in mixed-mode") stopped creating 1:1 mapping for all RAM in case of running in native 64bit mode. It turns out though that there are 64bit EFI implementations in the wild (this particular problem

[PATCH] x86/efi: Always map first physical page into EFI pagetables

From: Jiri Kosina Commit 129766708 ("x86/efi: Only map RAM into EFI page tables if in mixed-mode") stopped creating 1:1 mapping for all RAM in case of running in native 64bit mode. It turns out though that there are 64bit EFI implementations in the wild (this particular problem has been

[GIT PULL] ARC updates for 4.10-rc6

Hi Linus, Hopefully last set of changes for ARC for 4.10. Please pull. Thx, -Vineet ---> The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36: Linux 4.10-rc5 (2017-01-22 12:54:15 -0800) are available in the git repository at:

[GIT PULL] ARC updates for 4.10-rc6

Hi Linus, Hopefully last set of changes for ARC for 4.10. Please pull. Thx, -Vineet ---> The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36: Linux 4.10-rc5 (2017-01-22 12:54:15 -0800) are available in the git repository at:

Re: [PATCH 1/1] percpu-refcount: fix reference leak during percpu-atomic transition

On 01/27/2017 01:59 PM, Douglas Miller wrote: > percpu_ref_tryget() and percpu_ref_tryget_live() should return > "true" IFF they acquire a reference. But the return value from > atomic_long_inc_not_zero() is a long and may have high bits set, > e.g. PERCPU_COUNT_BIAS, and the return value of the

Re: [PATCH 1/1] percpu-refcount: fix reference leak during percpu-atomic transition

On 01/27/2017 01:59 PM, Douglas Miller wrote: > percpu_ref_tryget() and percpu_ref_tryget_live() should return > "true" IFF they acquire a reference. But the return value from > atomic_long_inc_not_zero() is a long and may have high bits set, > e.g. PERCPU_COUNT_BIAS, and the return value of the

Re: [PATCH v3 fpga 3/4] fpga: Add scatterlist based programming

On Mon, Jan 09, 2017 at 04:13:38PM -0600, Alan Tull wrote: > On Mon, Jan 9, 2017 at 10:12 AM, Jason Gunthorpe > wrote: > > On Mon, Jan 09, 2017 at 10:04:36AM -0600, Alan Tull wrote: > > > >> > diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c > >> >

Re: [PATCH v3 fpga 3/4] fpga: Add scatterlist based programming

On Mon, Jan 09, 2017 at 04:13:38PM -0600, Alan Tull wrote: > On Mon, Jan 9, 2017 at 10:12 AM, Jason Gunthorpe > wrote: > > On Mon, Jan 09, 2017 at 10:04:36AM -0600, Alan Tull wrote: > > > >> > diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c > >> > index

Re: [PATCH 1/4] efi/x86: make efi_memmap_reserve only insert into boot mem areas

On 27 January 2017 at 22:13, Matt Fleming wrote: > On Fri, 27 Jan, at 05:04:50PM, Ard Biesheuvel wrote: >> On 27 January 2017 at 14:48, Matt Fleming wrote: >> > On Fri, 13 Jan, at 05:29:52AM, Dave Young wrote: >> >> >> >> It sounds reasonable

Re: [PATCH 1/4] efi/x86: make efi_memmap_reserve only insert into boot mem areas

On 27 January 2017 at 22:13, Matt Fleming wrote: > On Fri, 27 Jan, at 05:04:50PM, Ard Biesheuvel wrote: >> On 27 January 2017 at 14:48, Matt Fleming wrote: >> > On Fri, 13 Jan, at 05:29:52AM, Dave Young wrote: >> >> >> >> It sounds reasonable though I'm still not sure about EFI_LOADER*. >> >> >>

Re: [PATCH 1/1] percpu-refcount: fix reference leak during percpu-atomic transition

Hello, Douglas. On Fri, Jan 27, 2017 at 02:59:08PM -0600, Douglas Miller wrote: > @@ -212,7 +212,7 @@ static inline bool percpu_ref_tryget(struct percpu_ref > *ref) > this_cpu_inc(*percpu_count); > ret = true; > } else { > - ret =

Re: [PATCH 1/1] percpu-refcount: fix reference leak during percpu-atomic transition

Hello, Douglas. On Fri, Jan 27, 2017 at 02:59:08PM -0600, Douglas Miller wrote: > @@ -212,7 +212,7 @@ static inline bool percpu_ref_tryget(struct percpu_ref > *ref) > this_cpu_inc(*percpu_count); > ret = true; > } else { > - ret =

Re: [PATCH V6 4/5] LPC: Support the device-tree LPC host on Hip06/Hip07

On Tue, Jan 24, 2017 at 03:05:24PM +0800, zhichang.yuan wrote: > The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in > I/O port addresses. This patch implements the LPC host controller driver which > perform the I/O operations on the underlying hardware. > We don't want to

Re: [PATCH V6 4/5] LPC: Support the device-tree LPC host on Hip06/Hip07

On Tue, Jan 24, 2017 at 03:05:24PM +0800, zhichang.yuan wrote: > The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in > I/O port addresses. This patch implements the LPC host controller driver which > perform the I/O operations on the underlying hardware. > We don't want to

Re: [PATCH 1/4] efi/x86: make efi_memmap_reserve only insert into boot mem areas

On Fri, 27 Jan, at 05:04:50PM, Ard Biesheuvel wrote: > On 27 January 2017 at 14:48, Matt Fleming wrote: > > On Fri, 13 Jan, at 05:29:52AM, Dave Young wrote: > >> > >> It sounds reasonable though I'm still not sure about EFI_LOADER*. > >> > >> The main purpose of this

Re: [PATCH 1/4] efi/x86: make efi_memmap_reserve only insert into boot mem areas

On Fri, 27 Jan, at 05:04:50PM, Ard Biesheuvel wrote: > On 27 January 2017 at 14:48, Matt Fleming wrote: > > On Fri, 13 Jan, at 05:29:52AM, Dave Young wrote: > >> > >> It sounds reasonable though I'm still not sure about EFI_LOADER*. > >> > >> The main purpose of this patch is to address the

net: suspicious RCU usage in nf_hook

Hello, I've got the following report while running syzkaller fuzzer on fd694aaa46c7ed811b72eb47d5eb11ce7ab3f7f1: [ INFO: suspicious RCU usage. ] 4.10.0-rc5+ #192 Not tainted --- ./include/linux/rcupdate.h:561 Illegal context switch in RCU read-side critical section!

net: suspicious RCU usage in nf_hook

Hello, I've got the following report while running syzkaller fuzzer on fd694aaa46c7ed811b72eb47d5eb11ce7ab3f7f1: [ INFO: suspicious RCU usage. ] 4.10.0-rc5+ #192 Not tainted --- ./include/linux/rcupdate.h:561 Illegal context switch in RCU read-side critical section!

[PATCH v2] net: adaptec: starfire: add checks for dma mapping errors

init_ring(), refill_rx_ring() and start_tx() don't check if mapping dma memory succeed. The patch adds the checks and failure handling. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov ---

[PATCH v2] net: adaptec: starfire: add checks for dma mapping errors

init_ring(), refill_rx_ring() and start_tx() don't check if mapping dma memory succeed. The patch adds the checks and failure handling. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/net/ethernet/adaptec/starfire.c | 45

[GIT PULL] EFI urgent fix

Folks, please pull the below fix from Jiri which fixes a triple fault affecting the Lenovo Yogas since v4.8. The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36: Linux 4.10-rc5 (2017-01-22 12:54:15 -0800) are available in the git repository at:

[GIT PULL] EFI urgent fix

Folks, please pull the below fix from Jiri which fixes a triple fault affecting the Lenovo Yogas since v4.8. The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36: Linux 4.10-rc5 (2017-01-22 12:54:15 -0800) are available in the git repository at:

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, 2017-01-27 at 16:20 -0500, Ken Goldman wrote: > On 1/19/2017 7:41 AM, Jarkko Sakkinen wrote: > > > > I actually think that the very best solution would be such that > > sessions would be *always* lease based. So when you create a > > session you would always loose within a time limit. > >

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, 2017-01-27 at 16:20 -0500, Ken Goldman wrote: > On 1/19/2017 7:41 AM, Jarkko Sakkinen wrote: > > > > I actually think that the very best solution would be such that > > sessions would be *always* lease based. So when you create a > > session you would always loose within a time limit. > >

[PATCH v6 4/5] fs/pstore: fs/squashfs: Change usage of LZ4 to work with new LZ4 version

This patch updates fs/pstore and fs/squashfs to use the updated functions from the new LZ4 module. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- fs/pstore/platform.c | 22 +- fs/squashfs/lz4_wrapper.c | 12 ++-- 2 files changed, 19

[PATCH v6 4/5] fs/pstore: fs/squashfs: Change usage of LZ4 to work with new LZ4 version

This patch updates fs/pstore and fs/squashfs to use the updated functions from the new LZ4 module. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- fs/pstore/platform.c | 22 +- fs/squashfs/lz4_wrapper.c | 12 ++-- 2 files changed, 19

[PATCH v6 1/5] lib: Update LZ4 compressor module

This patch updates LZ4 kernel module to LZ4 v1.7.3 by Yann Collet. The kernel module is inspired by the previous work by Chanho Min. The updated LZ4 module will not break existing code since the patchset contains appropriate changes. API changes: New method LZ4_compress_fast which differs from

[PATCH v6 1/5] lib: Update LZ4 compressor module

This patch updates LZ4 kernel module to LZ4 v1.7.3 by Yann Collet. The kernel module is inspired by the previous work by Chanho Min. The updated LZ4 module will not break existing code since the patchset contains appropriate changes. API changes: New method LZ4_compress_fast which differs from

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, 2017-01-27 at 16:42 -0500, Ken Goldman wrote: > On 1/18/2017 3:48 PM, James Bottomley wrote: > > In a TPM2, sessions can be globally exhausted once there are > > TPM_PT_ACTIVE_SESSION_MAX of them (even if they're all context > > saved). > > The Strategy for handling this is to keep a

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Fri, 2017-01-27 at 16:42 -0500, Ken Goldman wrote: > On 1/18/2017 3:48 PM, James Bottomley wrote: > > In a TPM2, sessions can be globally exhausted once there are > > TPM_PT_ACTIVE_SESSION_MAX of them (even if they're all context > > saved). > > The Strategy for handling this is to keep a

[PATCH v6 3/5] crypto: Change LZ4 modules to work with new LZ4 module version

This patch updates the crypto modules using LZ4 compression to work with the new LZ4 module version. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- crypto/lz4.c | 21 - crypto/lz4hc.c | 21 - 2 files changed, 16 insertions(+), 26

[PATCH v6 3/5] crypto: Change LZ4 modules to work with new LZ4 module version

This patch updates the crypto modules using LZ4 compression to work with the new LZ4 module version. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- crypto/lz4.c | 21 - crypto/lz4hc.c | 21 - 2 files changed, 16 insertions(+), 26

[PATCH 5/6] staging: bcm2835-v4l2: Apply many whitespace fixes from checkpatch.

Generated with checkpatch.pl --fix-inplace, some manual fixes for cases where checkpatch fixed one out of multiple lines of mis-indented function parameters, and then git add -p out of the results. I skipped some fixes that should probably instead be replaced with the BIT() macro. Signed-off-by:

[PATCH 5/6] staging: bcm2835-v4l2: Apply many whitespace fixes from checkpatch.

Generated with checkpatch.pl --fix-inplace, some manual fixes for cases where checkpatch fixed one out of multiple lines of mis-indented function parameters, and then git add -p out of the results. I skipped some fixes that should probably instead be replaced with the BIT() macro. Signed-off-by:

[PATCH v6 5/5] lib/lz4: Remove back-compat wrappers

This patch removes the functions introduced as wrappers for providing backwards compatibility to the prior LZ4 version. They're not needed anymore since there's no callers left. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- include/linux/lz4.h | 73

[PATCH v6 5/5] lib/lz4: Remove back-compat wrappers

This patch removes the functions introduced as wrappers for providing backwards compatibility to the prior LZ4 version. They're not needed anymore since there's no callers left. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- include/linux/lz4.h | 73

[PATCH v6 0/5] Update LZ4 compressor module

This patchset is for updating the LZ4 compression module to a version based on LZ4 v1.7.3 allowing to use the fast compression algorithm aka LZ4 fast which provides an "acceleration" parameter as a tradeoff between high compression ratio and high compression speed. We want to use LZ4 fast in

[PATCH v6 2/5] lib/decompress_unlz4: Change module to work with new LZ4 module version

This patch updates the unlz4 wrapper to work with the updated LZ4 kernel module version. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- lib/decompress_unlz4.c | 13 - 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/lib/decompress_unlz4.c

<    1   2   3   4   5   6   7   8   9   10   >