[PATCH 3/3] lightnvm: pblk: fix smeta write error path

From: Hans Holmberg Smeta write errors were previously ignored. Skip these lines instead and throw them back on the free list, so the chunks will go through a reset cycle before we attempt to use the line again. Signed-off-by: Hans Holmberg

[PATCH 3/3] lightnvm: pblk: fix smeta write error path

From: Hans Holmberg Smeta write errors were previously ignored. Skip these lines instead and throw them back on the free list, so the chunks will go through a reset cycle before we attempt to use the line again. Signed-off-by: Hans Holmberg --- drivers/lightnvm/pblk-core.c | 7 --- 1 file

[PATCH 2/3] lightnvm: pblk: garbage collect lines with failed writes

From: Hans Holmberg Write failures should not happen under normal circumstances, so in order to bring the chunk back into a known state as soon as possible, evacuate all the valid data out of the line and let the fw judge if the block can be written to in the next

[PATCH 2/3] lightnvm: pblk: garbage collect lines with failed writes

From: Hans Holmberg Write failures should not happen under normal circumstances, so in order to bring the chunk back into a known state as soon as possible, evacuate all the valid data out of the line and let the fw judge if the block can be written to in the next reset cycle. Do this by

Re: [PATCH v2 3/6] drm: of: introduce drm_of_media_bus_fmt

On 2018-04-19 18:22, Rob Herring wrote: > On Tue, Apr 17, 2018 at 8:10 AM, Peter Rosin wrote: >> Add a central function to parse a node according to the video >> interface binding and get a media bus format. >> >> Start with only supporting a very limited set of a few basic media

Re: [PATCH v2 3/6] drm: of: introduce drm_of_media_bus_fmt

On 2018-04-19 18:22, Rob Herring wrote: > On Tue, Apr 17, 2018 at 8:10 AM, Peter Rosin wrote: >> Add a central function to parse a node according to the video >> interface binding and get a media bus format. >> >> Start with only supporting a very limited set of a few basic media >> bus formats.

[PATCH 1/3] lightnvm: pblk: rework write error recovery path

From: Hans Holmberg The write error recovery path is incomplete, so rework the write error recovery handling to do resubmits directly from the write buffer. When a write error occurs, the remaining sectors in the chunk are mapped out and invalidated and the request

[PATCH 1/3] lightnvm: pblk: rework write error recovery path

From: Hans Holmberg The write error recovery path is incomplete, so rework the write error recovery handling to do resubmits directly from the write buffer. When a write error occurs, the remaining sectors in the chunk are mapped out and invalidated and the request inserted in a resubmit list.

Re: [PATCH v6 05/16] c6x: Switch to generic free_initrd_mem.

On Sun, 2018-04-01 at 10:59 -0400, Shea Levy wrote: > The first patch in this series added a weakly-defined generic > implementation, which is functionally identical to the > architecture-specific one removed here. > > Series boot-tested on RISC-V (which now uses the generic > implementation) and

Re: [PATCH v2] tracing: fix bad use of igrab in trace_uprobe.c

> On Apr 19, 2018, at 7:44 AM, Miklos Szeredi wrote: > > On Thu, Apr 19, 2018 at 10:58 AM, Miklos Szeredi wrote: >> On Wed, Apr 18, 2018 at 7:40 PM, Song Liu wrote: >>> As Miklos reported and suggested: >>> >>> This pattern

Re: [PATCH v6 05/16] c6x: Switch to generic free_initrd_mem.

On Sun, 2018-04-01 at 10:59 -0400, Shea Levy wrote: > The first patch in this series added a weakly-defined generic > implementation, which is functionally identical to the > architecture-specific one removed here. > > Series boot-tested on RISC-V (which now uses the generic > implementation) and

Re: [PATCH v2] tracing: fix bad use of igrab in trace_uprobe.c

> On Apr 19, 2018, at 7:44 AM, Miklos Szeredi wrote: > > On Thu, Apr 19, 2018 at 10:58 AM, Miklos Szeredi wrote: >> On Wed, Apr 18, 2018 at 7:40 PM, Song Liu wrote: >>> As Miklos reported and suggested: >>> >>> This pattern repeats two times in trace_uprobe.c and in >>>

Re: 4.15.17 regression: bisected: timeout during microcode update

On Thu, Apr 19, 2018 at 03:46:27PM +0200, Vitezslav Samel wrote: > > microcode: __reload_late: CPU0 > microcode: __reload_late: CPU3 > microcode: __reload_late: CPU2 > microcode: __reload_late: CPU1 > microcode: __reload_late: CPU0

Re: 4.15.17 regression: bisected: timeout during microcode update

On Thu, Apr 19, 2018 at 03:46:27PM +0200, Vitezslav Samel wrote: > > microcode: __reload_late: CPU0 > microcode: __reload_late: CPU3 > microcode: __reload_late: CPU2 > microcode: __reload_late: CPU1 > microcode: __reload_late: CPU0

Re: [PATCH v2] x86/cpufeature: guard asm_volatile_goto usage with NO_BPF_WORKAROUND

Hi, Peter, Just pinging. Did you get chances to look at this? [ cc netdev as well so folks are aware of the issue. ] Thanks! Yonghong On 4/14/18 9:27 PM, Yonghong Song wrote: Commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") removed X86_FAST_FEATURE_TESTS and make macro

Re: [PATCH v2] x86/cpufeature: guard asm_volatile_goto usage with NO_BPF_WORKAROUND

Hi, Peter, Just pinging. Did you get chances to look at this? [ cc netdev as well so folks are aware of the issue. ] Thanks! Yonghong On 4/14/18 9:27 PM, Yonghong Song wrote: Commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") removed X86_FAST_FEATURE_TESTS and make macro

[PATCH v3 3/7] drm: of: introduce drm_of_media_bus_fmt

Add a central function to parse a node according to the video interface binding and get a media bus format. Start with only supporting a very limited set of a few basic media bus formats. Signed-off-by: Peter Rosin --- drivers/gpu/drm/drm_of.c | 38

[PATCH v3 3/7] drm: of: introduce drm_of_media_bus_fmt

Add a central function to parse a node according to the video interface binding and get a media bus format. Start with only supporting a very limited set of a few basic media bus formats. Signed-off-by: Peter Rosin --- drivers/gpu/drm/drm_of.c | 38 ++

[PATCH v3 4/7] drm/atmel-hlcdc: support bus-width (12/16/18/24) in endpoint nodes

This beats the heuristic that the connector is involved in what format should be output for cases where this fails. E.g. if there is a bridge that changes format between the encoder and the connector, or if some of the RGB pins between the lcd controller and the encoder are not routed on the PCB.

[PATCH v3 4/7] drm/atmel-hlcdc: support bus-width (12/16/18/24) in endpoint nodes

This beats the heuristic that the connector is involved in what format should be output for cases where this fails. E.g. if there is a bridge that changes format between the encoder and the connector, or if some of the RGB pins between the lcd controller and the encoder are not routed on the PCB.

[PATCH v3 5/7] drm/i2c: tda998x: find the drm_device via the drm_connector

This prepares for being a drm_bridge which will not register the encoder. That makes the connector the better choice. Signed-off-by: Peter Rosin --- drivers/gpu/drm/i2c/tda998x_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v3 5/7] drm/i2c: tda998x: find the drm_device via the drm_connector

This prepares for being a drm_bridge which will not register the encoder. That makes the connector the better choice. Signed-off-by: Peter Rosin --- drivers/gpu/drm/i2c/tda998x_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c

[PATCH v3 6/7] drm/i2c: tda998x: split encoder and component functions from the work

This enables reuse of the machinery for the case where a drm_bridge needs to do the same work via different interfaces. Signed-off-by: Peter Rosin --- drivers/gpu/drm/i2c/tda998x_drv.c | 46 ++- 1 file changed, 36 insertions(+), 10

[PATCH v3 6/7] drm/i2c: tda998x: split encoder and component functions from the work

This enables reuse of the machinery for the case where a drm_bridge needs to do the same work via different interfaces. Signed-off-by: Peter Rosin --- drivers/gpu/drm/i2c/tda998x_drv.c | 46 ++- 1 file changed, 36 insertions(+), 10 deletions(-) diff --git

[PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

This makes this driver work with all(?) drivers that are not componentized and instead expect to connect to a panel/bridge. That said, the only one tested is atmel_hlcdc. This hooks the relevant work function previously called by the encoder and the component also to the bridge, since the encoder

[PATCH v3 0/7] Add tda998x (HDMI) support to atmel-hlcdc

Hi! I naively thought that since there was support for both nxp,tda19988 (in the tda998x driver) and the atmel-hlcdc, things would be a smooth ride. But it wasn't, so I started looking around and realized I had to fix things. In v1 and v2 I fixed things by making the atmel-hlcdc driver a master

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Thu, 19 Apr 2018, Eric Dumazet wrote: > > > On 04/19/2018 09:12 AM, Mikulas Patocka wrote: > > > > > > These bugs are hard to reproduce because vmalloc falls back to kmalloc > > only if memory is fragmented. > > > > This sentence is wrong. > > because kvmalloc() falls back to

[PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

This makes this driver work with all(?) drivers that are not componentized and instead expect to connect to a panel/bridge. That said, the only one tested is atmel_hlcdc. This hooks the relevant work function previously called by the encoder and the component also to the bridge, since the encoder

[PATCH v3 0/7] Add tda998x (HDMI) support to atmel-hlcdc

Hi! I naively thought that since there was support for both nxp,tda19988 (in the tda998x driver) and the atmel-hlcdc, things would be a smooth ride. But it wasn't, so I started looking around and realized I had to fix things. In v1 and v2 I fixed things by making the atmel-hlcdc driver a master

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Thu, 19 Apr 2018, Eric Dumazet wrote: > > > On 04/19/2018 09:12 AM, Mikulas Patocka wrote: > > > > > > These bugs are hard to reproduce because vmalloc falls back to kmalloc > > only if memory is fragmented. > > > > This sentence is wrong. > > because kvmalloc() falls back to

[PATCH v3 2/7] dt-bindings: display: atmel: optional video-interface of endpoints

With bus-type/bus-width properties in the endpoint nodes, the video- interface of the connection can be specified for cases where the heuristic fails to select the correct output mode. This can happen e.g. if not all RGB pins are routed on the PCB; the driver has no way of knowing this, and needs

[PATCH v3 2/7] dt-bindings: display: atmel: optional video-interface of endpoints

With bus-type/bus-width properties in the endpoint nodes, the video- interface of the connection can be specified for cases where the heuristic fails to select the correct output mode. This can happen e.g. if not all RGB pins are routed on the PCB; the driver has no way of knowing this, and needs

[PATCH v3 1/7] dt-bindings: display: bridge: lvds-transmitter: add ti,ds90c185

Start list of actual chips compatible with "lvds-encoder". Reviewed-by: Laurent Pinchart Reviewed-by: Rob Herring Signed-off-by: Peter Rosin --- .../devicetree/bindings/display/bridge/lvds-transmitter.txt | 8 +++-

[PATCH v3 1/7] dt-bindings: display: bridge: lvds-transmitter: add ti,ds90c185

Start list of actual chips compatible with "lvds-encoder". Reviewed-by: Laurent Pinchart Reviewed-by: Rob Herring Signed-off-by: Peter Rosin --- .../devicetree/bindings/display/bridge/lvds-transmitter.txt | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git

Re: [RFC PATCH v2 3/4] acpi: apei: Do not panic() when correctable errors are marked as fatal.

On 04/19/2018 10:35 AM, James Morse wrote: > Hi Alex, > > (I haven't read through all this yet, just on this one:) > > On 04/19/2018 03:57 PM, Alex G. wrote: >> Maybe it's better move the AER handling to NMI/IRQ context, since >> ghes_handle_aer() is only scheduling the real AER andler, and is

Re: [RFC PATCH v2 3/4] acpi: apei: Do not panic() when correctable errors are marked as fatal.

On 04/19/2018 10:35 AM, James Morse wrote: > Hi Alex, > > (I haven't read through all this yet, just on this one:) > > On 04/19/2018 03:57 PM, Alex G. wrote: >> Maybe it's better move the AER handling to NMI/IRQ context, since >> ghes_handle_aer() is only scheduling the real AER andler, and is

Re: [RFC PATCH v2 3/4] acpi: apei: Do not panic() when correctable errors are marked as fatal.

On 04/19/2018 10:40 AM, Borislav Petkov wrote: > On Thu, Apr 19, 2018 at 09:57:07AM -0500, Alex G. wrote: >> ghes_severity() is a one-to-one mapping from a set of unsorted >> severities to monotonically increasing numbers. The "one-to-one" mapping >> part of the sentence is obvious from the

Re: [RFC PATCH v2 3/4] acpi: apei: Do not panic() when correctable errors are marked as fatal.

On 04/19/2018 10:40 AM, Borislav Petkov wrote: > On Thu, Apr 19, 2018 at 09:57:07AM -0500, Alex G. wrote: >> ghes_severity() is a one-to-one mapping from a set of unsorted >> severities to monotonically increasing numbers. The "one-to-one" mapping >> part of the sentence is obvious from the

Re: [PATCH v3] serial: imx: warn user when using unsupported configuration

Hello Stefan, On Thu, Apr 19, 2018 at 05:39:16PM +0200, Stefan Agner wrote: > When using half-duplex mode (which disables receiver during txing) > the RTS signal cannot be driven low during transmission when using > i.MX UART RTS/CTS control. This seems to be a limitation of the > i.MX UART IP:

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

Den 19.04.2018 kl. 18:57, skrev Greg KH: On Thu, Apr 19, 2018 at 06:16:26PM +0300, Thomas Backlund wrote: Den 19.04.2018 kl. 17:22, skrev Greg KH: On Thu, Apr 19, 2018 at 04:05:45PM +0200, Jan Kara wrote: On Thu 19-04-18 15:59:43, Greg KH wrote: On Thu, Apr 19, 2018 at 02:41:33PM +0300,

Re: [PATCH v3] serial: imx: warn user when using unsupported configuration

Hello Stefan, On Thu, Apr 19, 2018 at 05:39:16PM +0200, Stefan Agner wrote: > When using half-duplex mode (which disables receiver during txing) > the RTS signal cannot be driven low during transmission when using > i.MX UART RTS/CTS control. This seems to be a limitation of the > i.MX UART IP:

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

Den 19.04.2018 kl. 18:57, skrev Greg KH: On Thu, Apr 19, 2018 at 06:16:26PM +0300, Thomas Backlund wrote: Den 19.04.2018 kl. 17:22, skrev Greg KH: On Thu, Apr 19, 2018 at 04:05:45PM +0200, Jan Kara wrote: On Thu 19-04-18 15:59:43, Greg KH wrote: On Thu, Apr 19, 2018 at 02:41:33PM +0300,

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On 04/19/2018 09:12 AM, Mikulas Patocka wrote: > > > These bugs are hard to reproduce because vmalloc falls back to kmalloc > only if memory is fragmented. > This sentence is wrong. because kvmalloc() falls back to vmalloc() ...

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On 04/19/2018 09:12 AM, Mikulas Patocka wrote: > > > These bugs are hard to reproduce because vmalloc falls back to kmalloc > only if memory is fragmented. > This sentence is wrong. because kvmalloc() falls back to vmalloc() ...

Re: [PATCH 53/61] tty: serial: simplify getting .drvdata

Hello Wolfram, On Thu, Apr 19, 2018 at 04:06:23PM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang > --- > > Build tested only.

Re: [PATCH 53/61] tty: serial: simplify getting .drvdata

Hello Wolfram, On Thu, Apr 19, 2018 at 04:06:23PM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang > --- > > Build tested only. buildbot is happy. Please apply

Re: [PATCH 02/61] ata: simplify getting .drvdata

Hello! On 04/19/2018 05:05 PM, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via Note that the name of the field in the 'struct device' is driver_data, not drvdata. Otherwise the patch looks good. > platform_device is an unneeded step back and forth. > >

Re: [PATCH 02/61] ata: simplify getting .drvdata

Hello! On 04/19/2018 05:05 PM, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via Note that the name of the field in the 'struct device' is driver_data, not drvdata. Otherwise the patch looks good. > platform_device is an unneeded step back and forth. > >

Re: general protection fault in rdma_resolve_route

On Thu, Apr 19, 2018 at 04:12:20PM +, Parav Pandit wrote: > > > > From: syzbot > > [mailto:syzbot+17c13600b3977aa8e...@syzkaller.appspotmail.com] > > Sent: Thursday, April 19, 2018 11:04 AM > > To: Daniel Jurgens ; > > dasaratharaman.chandramo...@intel.com;

Re: general protection fault in rdma_resolve_route

On Thu, Apr 19, 2018 at 04:12:20PM +, Parav Pandit wrote: > > > > From: syzbot > > [mailto:syzbot+17c13600b3977aa8e...@syzkaller.appspotmail.com] > > Sent: Thursday, April 19, 2018 11:04 AM > > To: Daniel Jurgens ; > > dasaratharaman.chandramo...@intel.com; dledf...@redhat.com; > >

Re: [PATCH v2 3/6] drm: of: introduce drm_of_media_bus_fmt

On Tue, Apr 17, 2018 at 8:10 AM, Peter Rosin wrote: > Add a central function to parse a node according to the video > interface binding and get a media bus format. > > Start with only supporting a very limited set of a few basic media > bus formats. > > Signed-off-by: Peter Rosin

Re: [PATCH v2 3/6] drm: of: introduce drm_of_media_bus_fmt

On Tue, Apr 17, 2018 at 8:10 AM, Peter Rosin wrote: > Add a central function to parse a node according to the video > interface binding and get a media bus format. > > Start with only supporting a very limited set of a few basic media > bus formats. > > Signed-off-by: Peter Rosin > --- >

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported

On 04/19/2018 03:35 AM, Sudeep Holla wrote: > > > On 18/04/18 16:56, Markus Mayer wrote: >> From: Jim Quinlan >> >> If the SCMI cpufreq driver is supported, we bail, so that the new >> approach can be used. >> >> Signed-off-by: Jim Quinlan >>

[PATCH v2] mmc: sdhci-cadence: fix logically and structurally dead code

Currently, the code block inside the for loop will never execute more than once, because the function returns inmediately after the first iteration, hence the execution of the code at the second iteration is structurally dead and, code at line 281: return 0; is never reached. Fix this by checking

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported

On 04/19/2018 03:35 AM, Sudeep Holla wrote: > > > On 18/04/18 16:56, Markus Mayer wrote: >> From: Jim Quinlan >> >> If the SCMI cpufreq driver is supported, we bail, so that the new >> approach can be used. >> >> Signed-off-by: Jim Quinlan >> Signed-off-by: Markus Mayer >> --- >>

[PATCH v2] mmc: sdhci-cadence: fix logically and structurally dead code

Currently, the code block inside the for loop will never execute more than once, because the function returns inmediately after the first iteration, hence the execution of the code at the second iteration is structurally dead and, code at line 281: return 0; is never reached. Fix this by checking

Re: general protection fault in snd_rawmidi_ioctl_compat

On Thu, 19 Apr 2018 18:10:01 +0200, syzbot wrote: > > Hello, > > syzbot hit the following crash on upstream commit > b284d4d5a6785f8cd07eda2646a95782373cd01e (Tue Apr 10 19:25:30 2018 +) > Merge tag 'ceph-for-4.17-rc1' of git://github.com/ceph/ceph-client > syzbot dashboard link: >

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

Den 19.04.2018 kl. 18:09, skrev Sasha Levin: On Thu, Apr 19, 2018 at 06:04:26PM +0300, Thomas Backlund wrote: Den 19.04.2018 kl. 16:59, skrev Greg KH: Anyway, we are trying not to do this, but it does, and will, occasionally happen. Look, we just did that for one platform for 4.9.94! And the

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

Den 19.04.2018 kl. 18:09, skrev Sasha Levin: On Thu, Apr 19, 2018 at 06:04:26PM +0300, Thomas Backlund wrote: Den 19.04.2018 kl. 16:59, skrev Greg KH: Anyway, we are trying not to do this, but it does, and will, occasionally happen. Look, we just did that for one platform for 4.9.94! And the

Re: general protection fault in snd_rawmidi_ioctl_compat

On Thu, 19 Apr 2018 18:10:01 +0200, syzbot wrote: > > Hello, > > syzbot hit the following crash on upstream commit > b284d4d5a6785f8cd07eda2646a95782373cd01e (Tue Apr 10 19:25:30 2018 +) > Merge tag 'ceph-for-4.17-rc1' of git://github.com/ceph/ceph-client > syzbot dashboard link: >

Re: [PATCH] vfio iommu type1: no need to check task->mm if task has been destroyed

[cc +Kirti] On Wed, 18 Apr 2018 18:55:45 +0800 Xu Yandong wrote: > The task structure in vfio_dma struct used to identify the same > task who map it or other task who shares same adress space is > allowed to unmap. But if the task who map it has exited, mm of > the task

Re: [PATCH] vfio iommu type1: no need to check task->mm if task has been destroyed

[cc +Kirti] On Wed, 18 Apr 2018 18:55:45 +0800 Xu Yandong wrote: > The task structure in vfio_dma struct used to identify the same > task who map it or other task who shares same adress space is > allowed to unmap. But if the task who map it has exited, mm of > the task has been set to null, we

Re: [PATCH] USB: Increment wakeup count on remote wakeup.

On Thu, Apr 19, 2018 at 8:01 AM, Alan Stern wrote: > On Wed, 18 Apr 2018, Ravi Chandra Sadineni wrote: > >> On chromebooks we depend on wakeup count to identify the wakeup source. >> But currently USB devices do not increment the wakeup count when they >> trigger the

[PATCH] regulator: tps6586x: Add support for TPS658624

This version is exists in the Samsung Galaxy Tab 10.1 which is based on the Nvidia Tegra 2 board. The TPS658624 has the same SM2 voltage table as TPS658623. Signed-off-by: ryang --- drivers/regulator/tps6586x-regulator.c | 1 + include/linux/mfd/tps6586x.h | 1 + 2

Re: [PATCH] USB: Increment wakeup count on remote wakeup.

On Thu, Apr 19, 2018 at 8:01 AM, Alan Stern wrote: > On Wed, 18 Apr 2018, Ravi Chandra Sadineni wrote: > >> On chromebooks we depend on wakeup count to identify the wakeup source. >> But currently USB devices do not increment the wakeup count when they >> trigger the remote wake. This patch

[PATCH] regulator: tps6586x: Add support for TPS658624

This version is exists in the Samsung Galaxy Tab 10.1 which is based on the Nvidia Tegra 2 board. The TPS658624 has the same SM2 voltage table as TPS658623. Signed-off-by: ryang --- drivers/regulator/tps6586x-regulator.c | 1 + include/linux/mfd/tps6586x.h | 1 + 2 files changed, 2

Re: [PATCH v2 2/2] regulator: add QCOM RPMh regulator driver

Hi, On Wed, Apr 18, 2018 at 4:30 PM, David Collins wrote: >>> + * @drms_mode: Array of regulator framework modes which can >>> + * be configured dynamically for this regulator >>> + * via the

Re: [PATCH v2 2/2] regulator: add QCOM RPMh regulator driver

Hi, On Wed, Apr 18, 2018 at 4:30 PM, David Collins wrote: >>> + * @drms_mode: Array of regulator framework modes which can >>> + * be configured dynamically for this regulator >>> + * via the set_load() callback. >> >> Using

[GIT PULL] MD update for 4.17-rc1

Hi, 3 small fixes for MD: - md-cluster fix for faulty device from Guoqing - writehint fix for writebehind IO for raid1 from Mariusz - a live lock fix for interrupted recovery from Yufen Please pull! The following changes since commit f8cf2f16a7c95acce497bfafa90e7c6d8397d653: Merge branch

[GIT PULL] MD update for 4.17-rc1

Hi, 3 small fixes for MD: - md-cluster fix for faulty device from Guoqing - writehint fix for writebehind IO for raid1 from Mariusz - a live lock fix for interrupted recovery from Yufen Please pull! The following changes since commit f8cf2f16a7c95acce497bfafa90e7c6d8397d653: Merge branch

[PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Wed, 18 Apr 2018, Mikulas Patocka wrote: > > > On Wed, 18 Apr 2018, David Miller wrote: > > > From: Mikulas Patocka > > Date: Wed, 18 Apr 2018 12:44:25 -0400 (EDT) > > > > > The structure net_device is followed by arbitrary driver-specific data > > > (accessible

KASAN: use-after-free Read in __fput (2)

Hello, syzbot hit the following crash on net-next commit 17dec0a949153d9ac00760ba2f5b78cb583e995f (Wed Apr 4 02:15:32 2018 +) Merge branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace syzbot dashboard link:

[PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Wed, 18 Apr 2018, Mikulas Patocka wrote: > > > On Wed, 18 Apr 2018, David Miller wrote: > > > From: Mikulas Patocka > > Date: Wed, 18 Apr 2018 12:44:25 -0400 (EDT) > > > > > The structure net_device is followed by arbitrary driver-specific data > > > (accessible with the function

KASAN: use-after-free Read in __fput (2)

Hello, syzbot hit the following crash on net-next commit 17dec0a949153d9ac00760ba2f5b78cb583e995f (Wed Apr 4 02:15:32 2018 +) Merge branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace syzbot dashboard link:

RE: general protection fault in rdma_resolve_route

> -Original Message- > From: syzbot > [mailto:syzbot+17c13600b3977aa8e...@syzkaller.appspotmail.com] > Sent: Thursday, April 19, 2018 11:04 AM > To: Daniel Jurgens ; > dasaratharaman.chandramo...@intel.com; dledf...@redhat.com; > j...@ziepe.ca; l...@kernel.org;

RE: general protection fault in rdma_resolve_route

> -Original Message- > From: syzbot > [mailto:syzbot+17c13600b3977aa8e...@syzkaller.appspotmail.com] > Sent: Thursday, April 19, 2018 11:04 AM > To: Daniel Jurgens ; > dasaratharaman.chandramo...@intel.com; dledf...@redhat.com; > j...@ziepe.ca; l...@kernel.org;

Re: [PATCH 4.9 181/310] net: phy: micrel: Restore led_mode and clk_sel on resume

On Thu, 2018-04-19 at 17:02 +0530, Naresh Kamboju wrote: > On 12 April 2018 at 00:05, Greg Kroah-Hartman > wrote: > > > > 4.9-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Leonard Crestez

Re: [PATCH 4.9 181/310] net: phy: micrel: Restore led_mode and clk_sel on resume

On Thu, 2018-04-19 at 17:02 +0530, Naresh Kamboju wrote: > On 12 April 2018 at 00:05, Greg Kroah-Hartman > wrote: > > > > 4.9-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Leonard Crestez > > > > [ Upstream commit

[GIT PULL] eCryptfs fixes for 4.17-rc2

Hi Linus, The following changes since commit 3215b9d57a2c75c4305a3956ca303d7004485200: Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux (2018-03-20 17:44:27 -0700) are available in the git repository at:

[GIT PULL] eCryptfs fixes for 4.17-rc2

Hi Linus, The following changes since commit 3215b9d57a2c75c4305a3956ca303d7004485200: Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux (2018-03-20 17:44:27 -0700) are available in the git repository at:

general protection fault in snd_rawmidi_ioctl_compat

Hello, syzbot hit the following crash on upstream commit b284d4d5a6785f8cd07eda2646a95782373cd01e (Tue Apr 10 19:25:30 2018 +) Merge tag 'ceph-for-4.17-rc1' of git://github.com/ceph/ceph-client syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=f7a0348affc3b67bc617

general protection fault in snd_rawmidi_ioctl_compat

Hello, syzbot hit the following crash on upstream commit b284d4d5a6785f8cd07eda2646a95782373cd01e (Tue Apr 10 19:25:30 2018 +) Merge tag 'ceph-for-4.17-rc1' of git://github.com/ceph/ceph-client syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=f7a0348affc3b67bc617

Re: WARNING in ext4_set_page_dirty

Hello, This is a known problem I was speaking about here [1]. It is a generic mm/fs problem but there's no solution to it yet. We'll discuss it at LSF/MM next week so after that we may have some solution... Honza [1]

Re: WARNING in ext4_set_page_dirty

Hello, This is a known problem I was speaking about here [1]. It is a generic mm/fs problem but there's no solution to it yet. We'll discuss it at LSF/MM next week so after that we may have some solution... Honza [1]

Re: [PATCH resend v3 3/3] dt-bindings: Document the DT bindings for lan78xx

On Thu, Apr 19, 2018 at 10:16 AM, Phil Elwell wrote: > The Microchip LAN78XX family of devices are Ethernet controllers with > a USB interface. Despite being discoverable devices it can be useful to > be able to configure them from Device Tree, particularly in low-cost >

Re: [PATCH resend v3 3/3] dt-bindings: Document the DT bindings for lan78xx

On Thu, Apr 19, 2018 at 10:16 AM, Phil Elwell wrote: > The Microchip LAN78XX family of devices are Ethernet controllers with > a USB interface. Despite being discoverable devices it can be useful to > be able to configure them from Device Tree, particularly in low-cost > applications without an

BUG: corrupted list in rdma_listen

Hello, syzbot hit the following crash on upstream commit bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +) Merge tag 'pinctrl-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl syzbot dashboard link:

BUG: corrupted list in rdma_listen

Hello, syzbot hit the following crash on upstream commit bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +) Merge tag 'pinctrl-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl syzbot dashboard link:

KASAN: use-after-free Read in llc_conn_tmr_common_cb

Hello, syzbot hit the following crash on upstream commit a27fc14219f2e3c4a46ba9177b04d9b52c875532 (Mon Apr 16 21:07:39 2018 +) Merge branch 'parisc-4.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux syzbot dashboard link:

KASAN: use-after-free Read in llc_conn_tmr_common_cb

Hello, syzbot hit the following crash on upstream commit a27fc14219f2e3c4a46ba9177b04d9b52c875532 (Mon Apr 16 21:07:39 2018 +) Merge branch 'parisc-4.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux syzbot dashboard link:

WARNING in reconnect_path

Hello, syzbot hit the following crash on upstream commit b5dbc28762fd3fd40ba76303be0c7f707826f982 (Sat Mar 31 04:53:57 2018 +) Merge tag 'kbuild-fixes-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild syzbot dashboard link:

WARNING in reconnect_path

Hello, syzbot hit the following crash on upstream commit b5dbc28762fd3fd40ba76303be0c7f707826f982 (Sat Mar 31 04:53:57 2018 +) Merge tag 'kbuild-fixes-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild syzbot dashboard link:

general protection fault in wb_workfn

Hello, syzbot hit the following crash on upstream commit 3eb2ce825ea1ad89d20f7a3b5780df850e4be274 (Sun Mar 25 22:44:30 2018 +) Linux 4.16-rc7 syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=9873874c735f2892e7e9 So far this crash happened 29 times on upstream.

general protection fault in wb_workfn

Hello, syzbot hit the following crash on upstream commit 3eb2ce825ea1ad89d20f7a3b5780df850e4be274 (Sun Mar 25 22:44:30 2018 +) Linux 4.16-rc7 syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=9873874c735f2892e7e9 So far this crash happened 29 times on upstream.

general protection fault in __delayacct_blkio_end

Hello, syzbot hit the following crash on upstream commit 0b412605ef5f5c64b31f19e2910b1d5eba9929c3 (Thu Mar 29 01:07:23 2018 +) Merge tag 'drm-fixes-for-v4.16-rc8' of git://people.freedesktop.org/~airlied/linux syzbot dashboard link:

general protection fault in __delayacct_blkio_end

Hello, syzbot hit the following crash on upstream commit 0b412605ef5f5c64b31f19e2910b1d5eba9929c3 (Thu Mar 29 01:07:23 2018 +) Merge tag 'drm-fixes-for-v4.16-rc8' of git://people.freedesktop.org/~airlied/linux syzbot dashboard link:

Re: [PATCH v2 08/10] dt-bindings: media: Document bindings for the Sunxi-Cedrus VPU driver

Hi Paul, On Thu, 2018-04-19 at 17:45 +0200, Paul Kocialkowski wrote: > This adds a device-tree binding document that specifies the properties > used by the Sunxi-Cedurs VPU driver, as well as examples. > > Signed-off-by: Paul Kocialkowski > --- >

Re: [PATCH v2 08/10] dt-bindings: media: Document bindings for the Sunxi-Cedrus VPU driver

Hi Paul, On Thu, 2018-04-19 at 17:45 +0200, Paul Kocialkowski wrote: > This adds a device-tree binding document that specifies the properties > used by the Sunxi-Cedurs VPU driver, as well as examples. > > Signed-off-by: Paul Kocialkowski > --- > .../devicetree/bindings/media/sunxi-cedrus.txt

Re: [PATCH] x86/ldt: Fix support_pte_mask filtering in map_ldt_struct()

On Thu, Apr 19, 2018 at 05:11:27PM +0200, Joerg Roedel wrote: > Cool, thanks for testing! I prepared a patch and will send it out if > Boris also reports success. I'll also added your Tested-by :) Boris reports success too. Very good catch, thanks! -- Regards/Gruss, Boris. SUSE Linux

Re: [PATCH] x86/ldt: Fix support_pte_mask filtering in map_ldt_struct()

On Thu, Apr 19, 2018 at 05:11:27PM +0200, Joerg Roedel wrote: > Cool, thanks for testing! I prepared a patch and will send it out if > Boris also reports success. I'll also added your Tested-by :) Boris reports success too. Very good catch, thanks! -- Regards/Gruss, Boris. SUSE Linux

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