[PATCHv4 08/10] backlight: add TI LMU backlight driver

This adds backlight support for the following TI LMU chips: LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. Signed-off-by: Milo Kim [add LED subsystem support for keyboard backlight and rework DT binding according to Rob Herrings feedback] Signed-off-by: Sebastian Reichel ---

[PATCHv4 09/10] dt-bindings: mfd: ti-lmu: update for backlight

Update binding to integrate the backlight feature directly into the main node, as suggested by Rob Herring. Signed-off-by: Sebastian Reichel --- Documentation/devicetree/bindings/mfd/ti-lmu.txt | 119 --- 1 file changed, 60 insertions(+), 59 deletions(-) diff --git

[PATCHv4 07/10] mfd: ti-lmu: register one backlight device per channel

All LMU devices support multiple channels, that can be controlled independently. This registers one backlight sub-device per channel. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 62 +-

[PATCHv4 07/10] mfd: ti-lmu: register one backlight device per channel

All LMU devices support multiple channels, that can be controlled independently. This registers one backlight sub-device per channel. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 62 +- include/linux/mfd/ti-lmu.h | 4 +++ 2 files

[PATCHv4 10/10] ARM: dts: omap4-droid4: update backlight led-controller

From: Sebastian Reichel This updates the backlight led-controller node to follow the new binding instead of the legacy out-of-tree binding. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 20 1 file

[PATCHv4 10/10] ARM: dts: omap4-droid4: update backlight led-controller

From: Sebastian Reichel This updates the backlight led-controller node to follow the new binding instead of the legacy out-of-tree binding. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 20 1 file changed, 12 insertions(+), 8 deletions(-)

[PATCHv4 06/10] mfd: ti-lmu: add PWM support

This adds support to acquire the optional PWM channel, that can be used by some of the LMU variants. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 11 +++ include/linux/mfd/ti-lmu.h | 3 +++ 2 files changed, 14 insertions(+) diff

[PATCHv4 05/10] mfd: ti-lmu: use of_device_get_match_data() helper

Replace of_match_device() with of_device_get_match_data(), which slightly decreases lines of code and allows to move the DT table next to the I2C table. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 30 ++ 1 file

[PATCHv4 06/10] mfd: ti-lmu: add PWM support

This adds support to acquire the optional PWM channel, that can be used by some of the LMU variants. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 11 +++ include/linux/mfd/ti-lmu.h | 3 +++ 2 files changed, 14 insertions(+) diff --git a/drivers/mfd/ti-lmu.c

[PATCHv4 05/10] mfd: ti-lmu: use of_device_get_match_data() helper

Replace of_match_device() with of_device_get_match_data(), which slightly decreases lines of code and allows to move the DT table next to the I2C table. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 30 ++ 1 file changed, 14 insertions(+), 16

[PATCHv4 01/10] mfd: ti-lmu: constify mfd_cell tables

Add const attribute to all mfd_cell structures. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/mfd/ti-lmu.c b/drivers/mfd/ti-lmu.c index

[PATCHv4 01/10] mfd: ti-lmu: constify mfd_cell tables

Add const attribute to all mfd_cell structures. Signed-off-by: Sebastian Reichel --- drivers/mfd/ti-lmu.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/mfd/ti-lmu.c b/drivers/mfd/ti-lmu.c index cfb411cde51c..990437e5ed0a 100644 ---

Re: [PATCH 2/6] x86/intel_rdt/mba_sc: Add support to enable/disable via mount option

Hello Thomas, On Fri, 30 Mar 2018, Thomas Gleixner wrote: On Thu, 29 Mar 2018, Vikas Shivappa wrote: Subject: x86/intel_rdt/mba_sc: Add support to enable/disable via mount option Huch? From Documentation: The ``summary phrase`` in the email's Subject should concisely describe the

Re: [PATCH 2/6] x86/intel_rdt/mba_sc: Add support to enable/disable via mount option

Hello Thomas, On Fri, 30 Mar 2018, Thomas Gleixner wrote: On Thu, 29 Mar 2018, Vikas Shivappa wrote: Subject: x86/intel_rdt/mba_sc: Add support to enable/disable via mount option Huch? From Documentation: The ``summary phrase`` in the email's Subject should concisely describe the

[PATCHv3 1/8] drm/omap: add framedone interrupt support

This prepares framedone interrupt handling for manual display update support. Tested-by: Tony Lindgren Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/omap_crtc.c | 48 +

[PATCHv3 0/8] omapdrm: DSI command mode panel support

Hi, These are the remaining patches from my previous patchset to get Droid 4 (OMAP4) display working. The patches have been rebased to linux-next tag next-20180329. I skipped the OMAP3 support patches. They should get their own series, once this patchset has landed. Working on Droid 4: *

[PATCHv3 1/8] drm/omap: add framedone interrupt support

This prepares framedone interrupt handling for manual display update support. Tested-by: Tony Lindgren Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/omap_crtc.c | 48 + drivers/gpu/drm/omapdrm/omap_crtc.h | 1 +

[PATCHv3 0/8] omapdrm: DSI command mode panel support

Hi, These are the remaining patches from my previous patchset to get Droid 4 (OMAP4) display working. The patches have been rebased to linux-next tag next-20180329. I skipped the OMAP3 support patches. They should get their own series, once this patchset has landed. Working on Droid 4: *

[PATCHv3 3/8] drm/omap: add support for manually updated displays

This adds the required infrastructure for manually updated displays, such as DSI command mode panels. While those panels often support partial updates we currently always do a full refresh. Display will be refreshed when something calls the dirty callback, such as libdrm's drmModeDirtyFB(). This

[PATCHv3 3/8] drm/omap: add support for manually updated displays

This adds the required infrastructure for manually updated displays, such as DSI command mode panels. While those panels often support partial updates we currently always do a full refresh. Display will be refreshed when something calls the dirty callback, such as libdrm's drmModeDirtyFB(). This

[PATCHv3 5/8] dt-bindings: panel: common: document orientation property

Merge "rotation" property description into common panel binding. Suggested-by: Rob Herring Signed-off-by: Sebastian Reichel --- .../devicetree/bindings/display/panel/panel-common.txt | 12

[PATCHv3 5/8] dt-bindings: panel: common: document orientation property

Merge "rotation" property description into common panel binding. Suggested-by: Rob Herring Signed-off-by: Sebastian Reichel --- .../devicetree/bindings/display/panel/panel-common.txt | 12 Documentation/devicetree/bindings/display/panel/panel.txt| 4 2 files

[PATCHv3 8/8] ARM: dts: omap4-droid4: Add LCD panel rotation property

This adds a LCD panel rotation hint to the Droid 4. If the display is rotated this way the keyboard can be used properly. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCHv3 2/8] drm/omap: add manual update detection helper

In preparation for manually updated display support, such as DSI command mode panels, this adds a simple helper to see if a connector is manually updated. Tested-by: Tony Lindgren Signed-off-by: Sebastian Reichel ---

[PATCHv3 8/8] ARM: dts: omap4-droid4: Add LCD panel rotation property

This adds a LCD panel rotation hint to the Droid 4. If the display is rotated this way the keyboard can be used properly. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/omap4-droid4-xt894.dts

[PATCHv3 2/8] drm/omap: add manual update detection helper

In preparation for manually updated display support, such as DSI command mode panels, this adds a simple helper to see if a connector is manually updated. Tested-by: Tony Lindgren Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/omap_connector.c | 8

[PATCHv3 4/8] drm/omap: make omap_framebuffer_get_next_connector static

omap_framebuffer_get_next_connector() is only required within omap_fb, so let's make it static. The function had to be moved before the first (and only) user. Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/omap_fb.c | 54

[PATCHv3 4/8] drm/omap: make omap_framebuffer_get_next_connector static

omap_framebuffer_get_next_connector() is only required within omap_fb, so let's make it static. The function had to be moved before the first (and only) user. Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/omap_fb.c | 54 +++

[PATCHv3 6/8] drm/omap: add support for rotation hints from display drivers

This adds support for setting DRM panel orientation property based on rotation information from the display driver. Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/dss/omapdss.h| 2 ++ drivers/gpu/drm/omapdrm/omap_connector.c | 34

[PATCHv3 6/8] drm/omap: add support for rotation hints from display drivers

This adds support for setting DRM panel orientation property based on rotation information from the display driver. Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/dss/omapdss.h| 2 ++ drivers/gpu/drm/omapdrm/omap_connector.c | 34 +++- 2 files

[PATCHv3 7/8] drm/omap: panel-dsi-cm: add rotation support

From: Sebastian Reichel Add support to inform the DRM subsystem about the orientation the display has been mounted to the casing. Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c | 13 + 1 file

[PATCHv3 7/8] drm/omap: panel-dsi-cm: add rotation support

From: Sebastian Reichel Add support to inform the DRM subsystem about the orientation the display has been mounted to the casing. Signed-off-by: Sebastian Reichel --- drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c | 13 + 1 file changed, 13 insertions(+) diff --git

Re: [RESEND PATCH] crypto: Add zstd support

On Thu, Mar 22, 2018 at 01:32:30PM +0900, Sergey Senozhatsky wrote: > On (03/21/18 15:49), Nick Terrell wrote: > > depends on CONFIG_CRYPTO_ZSTD, which isn't defined until this patch is in > > Yikes! How come I missed that... :) > > > [0] > >

Re: [RESEND PATCH] crypto: Add zstd support

On Thu, Mar 22, 2018 at 01:32:30PM +0900, Sergey Senozhatsky wrote: > On (03/21/18 15:49), Nick Terrell wrote: > > depends on CONFIG_CRYPTO_ZSTD, which isn't defined until this patch is in > > Yikes! How come I missed that... :) > > > [0] > >

[PATCH] debugfs_simple_attr.cocci: add clarifying information

The referenced commit gives some information about the overhead reduced by this change. Signed-off-by: Julia Lawall --- scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci |2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH] debugfs_simple_attr.cocci: add clarifying information

The referenced commit gives some information about the overhead reduced by this change. Signed-off-by: Julia Lawall --- scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci |2 ++ 1 file changed, 2 insertions(+) diff --git a/scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci

Re: [PATCH v5 5/8] remoteproc/davinci: prepare and unprepare the clock where needed

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski We're currently switching the platform to using the common clock framework. We need to explicitly prepare and unprepare the rproc clock. Signed-off-by: Bartosz Golaszewski

Re: [PATCH v5 5/8] remoteproc/davinci: prepare and unprepare the clock where needed

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski We're currently switching the platform to using the common clock framework. We need to explicitly prepare and unprepare the rproc clock. Signed-off-by: Bartosz Golaszewski Acked-by: Suman Anna --- Reviewed-by:

Re: [PATCH v5 4/8] remoteproc/davinci: add the missing retval check for clk_enable()

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The davinci platform is being switched to using the common clock framework, where clk_enable() can fail. Add the return value check. Signed-off-by: Bartosz Golaszewski

Re: [PATCH v5 4/8] remoteproc/davinci: add the missing retval check for clk_enable()

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The davinci platform is being switched to using the common clock framework, where clk_enable() can fail. Add the return value check. Signed-off-by: Bartosz Golaszewski Acked-by: Suman Anna --- Reviewed-by: David

Re: [PATCH v5 3/8] clk: davinci: add a reset lookup table for psc0

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski In order to be able to use the reset framework in legacy boot mode as well, add the reset lookup table to the psc driver for da850 variant. Signed-off-by: Bartosz Golaszewski

Re: [PATCH v5 3/8] clk: davinci: add a reset lookup table for psc0

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski In order to be able to use the reset framework in legacy boot mode as well, add the reset lookup table to the psc driver for da850 variant. Signed-off-by: Bartosz Golaszewski --- Reviewed-by: David Lechner

Re: [PATCH v5 2/8] ARM: davinci: dts: add a reset control to the dsp node

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The davinci-rproc driver will soon use the reset framework. Add the resets property to the dsp node in da850.dtsi. Signed-off-by: Bartosz Golaszewski ---

Re: [PATCH v5 2/8] ARM: davinci: dts: add a reset control to the dsp node

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The davinci-rproc driver will soon use the reset framework. Add the resets property to the dsp node in da850.dtsi. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/da850.dtsi | 1 + 1 file changed, 1

Re: [PATCH v5 1/8] ARM: davinci: dts: make psc0 a reset provider

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The psc driver registers with the reset framework as a provider. Add the #reset-cells property to the psc0 node. Signed-off-by: Bartosz Golaszewski ---

Re: [PATCH v5 1/8] ARM: davinci: dts: make psc0 a reset provider

On 3/30/18 10:28 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The psc driver registers with the reset framework as a provider. Add the #reset-cells property to the psc0 node. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/da850.dtsi | 1 + 1 file changed, 1

[PULL REQUEST] i2c for 4.16

Linus, here is a simple but worthwhile I2C driver fix for 4.16. Please pull. Thanks, Wolfram The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f: Linux 4.16-rc6 (2018-03-18 17:48:42 -0700) are available in the git repository at:

[PULL REQUEST] i2c for 4.16

Linus, here is a simple but worthwhile I2C driver fix for 4.16. Please pull. Thanks, Wolfram The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f: Linux 4.16-rc6 (2018-03-18 17:48:42 -0700) are available in the git repository at:

[PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

This is a fix for a regression in 32 bit kernels caused by an invalid check for pgoff overflow in hugetlbfs mmap setup. The check incorrectly specified that the size of a loff_t was the same as the size of a long. The regression prevents mapping hugetlbfs files at offsets greater than 4GB on 32

[PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

This is a fix for a regression in 32 bit kernels caused by an invalid check for pgoff overflow in hugetlbfs mmap setup. The check incorrectly specified that the size of a loff_t was the same as the size of a long. The regression prevents mapping hugetlbfs files at offsets greater than 4GB on 32

Re: [PATCH] connector: add parent pid and tgid to coredump and exit events

From: Stefan Strogin Date: Thu, 29 Mar 2018 17:12:47 +0300 > diff --git a/include/uapi/linux/cn_proc.h b/include/uapi/linux/cn_proc.h > index 68ff25414700..db210625cee8 100644 > --- a/include/uapi/linux/cn_proc.h > +++ b/include/uapi/linux/cn_proc.h > @@ -116,12 +116,16 @@

Re: [PATCH] connector: add parent pid and tgid to coredump and exit events

From: Stefan Strogin Date: Thu, 29 Mar 2018 17:12:47 +0300 > diff --git a/include/uapi/linux/cn_proc.h b/include/uapi/linux/cn_proc.h > index 68ff25414700..db210625cee8 100644 > --- a/include/uapi/linux/cn_proc.h > +++ b/include/uapi/linux/cn_proc.h > @@ -116,12 +116,16 @@ struct proc_event { >

Re: [PATCH net-next] MAINTAINERS: Update my email address from freescale to nxp

From: Claudiu Manoil Date: Thu, 29 Mar 2018 13:58:48 +0300 > The freescale.com address will no longer be available. > > Signed-off-by: Claudiu Manoil Applied.

Re: [PATCH net-next] MAINTAINERS: Update my email address from freescale to nxp

From: Claudiu Manoil Date: Thu, 29 Mar 2018 13:58:48 +0300 > The freescale.com address will no longer be available. > > Signed-off-by: Claudiu Manoil Applied.

[PATCH v2] crypto/ecc: Actually remove stack VLA usage

On the quest to remove all VLAs from the kernel[1], this avoids VLAs by just using the maximum allocation size (4 bytes) for stack arrays. All the VLAs in ecc were either 3 or 4 bytes (or a multiple), so just make it 4 bytes all the time. Initialization routines are adjusted to check that ndigits

[PATCH v2] crypto/ecc: Actually remove stack VLA usage

On the quest to remove all VLAs from the kernel[1], this avoids VLAs by just using the maximum allocation size (4 bytes) for stack arrays. All the VLAs in ecc were either 3 or 4 bytes (or a multiple), so just make it 4 bytes all the time. Initialization routines are adjusted to check that ndigits

Re: INFO: task hung in stop_sync_thread (2)

On Fri, Mar 30, 2018 at 6:46 PM, syzbot wrote: > syzbot has found reproducer for the following crash on net-next commit /\/\/\/\/\/\ now syzbot can test fixes > 18845557fd6fc1998f2d0d8c30467f86db587529 (Thu Mar 29 20:24:06 2018 +) >

Re: INFO: task hung in stop_sync_thread (2)

On Fri, Mar 30, 2018 at 6:46 PM, syzbot wrote: > syzbot has found reproducer for the following crash on net-next commit /\/\/\/\/\/\ now syzbot can test fixes > 18845557fd6fc1998f2d0d8c30467f86db587529 (Thu Mar 29 20:24:06 2018 +) > Merge tag 'wireless-drivers-next-for-davem-2018-03-29' of

Re: [PATCH] Revert "crypto/ecc: Remove stack VLA usage"

On Fri, Mar 30, 2018 at 9:39 AM, Herbert Xu wrote: > On Mon, Mar 26, 2018 at 04:03:08PM -0700, Kees Cook wrote: >> This reverts commit 14de52112ee70ca289fa77bf2d9cbc79fd2c811f. >> >> The solution was incomplete and inefficient. This will be fixed >> correctly in the

Re: [PATCH] Revert "crypto/ecc: Remove stack VLA usage"

On Fri, Mar 30, 2018 at 9:39 AM, Herbert Xu wrote: > On Mon, Mar 26, 2018 at 04:03:08PM -0700, Kees Cook wrote: >> This reverts commit 14de52112ee70ca289fa77bf2d9cbc79fd2c811f. >> >> The solution was incomplete and inefficient. This will be fixed >> correctly in the next patch. >> >>

Re: INFO: task hung in stop_sync_thread (2)

syzbot has found reproducer for the following crash on net-next commit 18845557fd6fc1998f2d0d8c30467f86db587529 (Thu Mar 29 20:24:06 2018 +) Merge tag 'wireless-drivers-next-for-davem-2018-03-29' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next syzbot dashboard

Re: INFO: task hung in stop_sync_thread (2)

syzbot has found reproducer for the following crash on net-next commit 18845557fd6fc1998f2d0d8c30467f86db587529 (Thu Mar 29 20:24:06 2018 +) Merge tag 'wireless-drivers-next-for-davem-2018-03-29' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next syzbot dashboard

[PATCH v2] perf stat: avoid 10ms limit for printing event counts

Currently print count interval for performance counters values is limited by 10ms so reading the values at frequencies higher than 100Hz is restricted by the tool. This change avoids that limitation and makes perf stat -I possible on frequencies up to 1KHz and, to some extent, makes perf stat

[PATCH v2] perf stat: avoid 10ms limit for printing event counts

Currently print count interval for performance counters values is limited by 10ms so reading the values at frequencies higher than 100Hz is restricted by the tool. This change avoids that limitation and makes perf stat -I possible on frequencies up to 1KHz and, to some extent, makes perf stat

Re: [PATCH] Revert "crypto/ecc: Remove stack VLA usage"

On Mon, Mar 26, 2018 at 04:03:08PM -0700, Kees Cook wrote: > This reverts commit 14de52112ee70ca289fa77bf2d9cbc79fd2c811f. > > The solution was incomplete and inefficient. This will be fixed > correctly in the next patch. > > Signed-off-by: Kees Cook Hmm you didn't post

Re: [PATCH] Revert "crypto/ecc: Remove stack VLA usage"

On Mon, Mar 26, 2018 at 04:03:08PM -0700, Kees Cook wrote: > This reverts commit 14de52112ee70ca289fa77bf2d9cbc79fd2c811f. > > The solution was incomplete and inefficient. This will be fixed > correctly in the next patch. > > Signed-off-by: Kees Cook Hmm you didn't post this to linux-crypto so

Re: [PATCH v1] kernel/trace:check the val against the available mem

Hi Steve, On Fri, Mar 30, 2018 at 7:20 AM, Steven Rostedt wrote: > > [ Adding memory management folks to discuss the issue ] > > On Thu, 29 Mar 2018 18:41:44 +0800 > Zhaoyang Huang wrote: > >> It is reported that some user app would like to echo a

Re: [PATCH v1] kernel/trace:check the val against the available mem

Hi Steve, On Fri, Mar 30, 2018 at 7:20 AM, Steven Rostedt wrote: > > [ Adding memory management folks to discuss the issue ] > > On Thu, 29 Mar 2018 18:41:44 +0800 > Zhaoyang Huang wrote: > >> It is reported that some user app would like to echo a huge >> number to

kernel BUG at /home/blee/project/race-fuzzer/kernels/kernel_v4.16-rc3/net/packet/af_packet.c:LINE!

We report the crash: kernel BUG at /home/blee/project/race-fuzzer/kernels/kernel_v4.16-rc3/net/packet/af_packet.c:LINE! This crash has been found in v4.16-rc3 using RaceFuzzer (a modified version of Syzkaller), which we describe more at the end of this report. Our analysis shows that the race

kernel BUG at /home/blee/project/race-fuzzer/kernels/kernel_v4.16-rc3/net/packet/af_packet.c:LINE!

We report the crash: kernel BUG at /home/blee/project/race-fuzzer/kernels/kernel_v4.16-rc3/net/packet/af_packet.c:LINE! This crash has been found in v4.16-rc3 using RaceFuzzer (a modified version of Syzkaller), which we describe more at the end of this report. Our analysis shows that the race

Re: [PATCH] ISDN: eicon: message: remove redundant check

On 03/30/2018 11:19 AM, Joe Perches wrote: On Fri, 2018-03-30 at 10:46 -0500, Gustavo A. R. Silva wrote: Check on plci->internal_command is unnecessary. Probably all of these are unnecessary too: $ for length in {7..2} ; do \ grep-2.5.4 -rP --include=*.[ch] -n

Re: [PATCH] ISDN: eicon: message: remove redundant check

On 03/30/2018 11:19 AM, Joe Perches wrote: On Fri, 2018-03-30 at 10:46 -0500, Gustavo A. R. Silva wrote: Check on plci->internal_command is unnecessary. Probably all of these are unnecessary too: $ for length in {7..2} ; do \ grep-2.5.4 -rP --include=*.[ch] -n

Re: [PATCH] f2fs: remain written times to update inode during fsync

On 03/30, Chao Yu wrote: > Hi Jaegeuk, > > On 2018/3/30 13:51, Jaegeuk Kim wrote: > > This fixes xfstests/generic/392. > > Hmm... Could you please give more details about this issue and solution in > commit message, since I can catch up the solution only with the code. Yeah, I missed some

Re: [PATCH] f2fs: remain written times to update inode during fsync

On 03/30, Chao Yu wrote: > Hi Jaegeuk, > > On 2018/3/30 13:51, Jaegeuk Kim wrote: > > This fixes xfstests/generic/392. > > Hmm... Could you please give more details about this issue and solution in > commit message, since I can catch up the solution only with the code. Yeah, I missed some

Re: [PATCH v2] f2fs: remain written times to update inode during fsync

Change log from v1: - add more description This fixes xfstests/generic/392. The failure was caused by different times between 1) one marked in the last fsync(2) call and 2) the other given by roll-forward recovery after power-cut. The reason was that we skipped updating inode block at 1), since

Re: [PATCH v2] f2fs: remain written times to update inode during fsync

Change log from v1: - add more description This fixes xfstests/generic/392. The failure was caused by different times between 1) one marked in the last fsync(2) call and 2) the other given by roll-forward recovery after power-cut. The reason was that we skipped updating inode block at 1), since

Re: [PATCH] net: mvneta: remove duplicate *_coal assignment

From: Jisheng Zhang Date: Thu, 29 Mar 2018 17:29:40 +0800 > The style of the rx/tx queue's *_coal member assignment is: > > static void foo_coal_set(...) > { > set the coal in hw; > update queue's foo_coal member; [1] > } > > In other place, we call

Re: [PATCH] net: mvneta: remove duplicate *_coal assignment

From: Jisheng Zhang Date: Thu, 29 Mar 2018 17:29:40 +0800 > The style of the rx/tx queue's *_coal member assignment is: > > static void foo_coal_set(...) > { > set the coal in hw; > update queue's foo_coal member; [1] > } > > In other place, we call foo_coal_set(pp,

Re: [PATCH] ISDN: eicon: message: remove redundant check

On Fri, 2018-03-30 at 10:46 -0500, Gustavo A. R. Silva wrote: > Check on plci->internal_command is unnecessary. Probably all of these are unnecessary too: $ for length in {7..2} ; do \ grep-2.5.4 -rP --include=*.[ch] -n "^\t{$length,$length}break;\n\t{$(($length-1)),$(($length-1))}break;" *

Re: [PATCH] ISDN: eicon: message: remove redundant check

On Fri, 2018-03-30 at 10:46 -0500, Gustavo A. R. Silva wrote: > Check on plci->internal_command is unnecessary. Probably all of these are unnecessary too: $ for length in {7..2} ; do \ grep-2.5.4 -rP --include=*.[ch] -n "^\t{$length,$length}break;\n\t{$(($length-1)),$(($length-1))}break;" *

[PATCH] arm64: dts: hikey: Enable SDIO high-speed mode on WL1835 module

According to hardware documentation, the WL1835MOD WiFi chip supports SDIO high-speed mode, which increases the clock to 50 MHz. This results in a modest increase in throughput. Signed-off-by: Ryan Grachek --- arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + 1 file changed,

[PATCH] arm64: dts: hikey: Enable SDIO high-speed mode on WL1835 module

According to hardware documentation, the WL1835MOD WiFi chip supports SDIO high-speed mode, which increases the clock to 50 MHz. This results in a modest increase in throughput. Signed-off-by: Ryan Grachek --- arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + 1 file changed, 1 insertion(+)

[PATCH] drm/amd/display: fix spelling mistake: "Usupported" -> "Unsupported"

From: Colin Ian King Trivial fix to spelling mistake in DRM_ERROR error message text Signed-off-by: Colin Ian King --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] drm/amd/display: fix spelling mistake: "Usupported" -> "Unsupported"

From: Colin Ian King Trivial fix to spelling mistake in DRM_ERROR error message text Signed-off-by: Colin Ian King --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c

Linux 4.16: Reported regressions as of Friday, 2018-03-30

On 26.03.2018 01:37, Linus Torvalds wrote: > […] Anyway. Go out and test. And let's hope next week is nice and calm and > I can release the final 4.16 next Sunday without any extra rc's. > >Linus Hi! Find below my seventh regression report for Linux 4.16; it's a "the final

Linux 4.16: Reported regressions as of Friday, 2018-03-30

On 26.03.2018 01:37, Linus Torvalds wrote: > […] Anyway. Go out and test. And let's hope next week is nice and calm and > I can release the final 4.16 next Sunday without any extra rc's. > >Linus Hi! Find below my seventh regression report for Linux 4.16; it's a "the final

[PATCH v2 1/2] io: prevent compiler reordering on the default writeX() implementation

The default implementation of mapping writeX() to __raw_writeX() is wrong. writeX() has stronger ordering semantics. Compiler is allowed to reorder __raw_writeX(). In the abscence of a write barrier or when using a strongly ordered architecture, writeX() should at least have a compiler barrier in

[PATCH v2 1/2] io: prevent compiler reordering on the default writeX() implementation

The default implementation of mapping writeX() to __raw_writeX() is wrong. writeX() has stronger ordering semantics. Compiler is allowed to reorder __raw_writeX(). In the abscence of a write barrier or when using a strongly ordered architecture, writeX() should at least have a compiler barrier in

[PATCH v2 2/2] io: prevent compiler reordering on the default readX() implementation

The default implementation of mapping readX() to __raw_readX() is wrong. readX() has stronger ordering semantics. Compiler is allowed to reorder __raw_readX(). In the abscence of a read barrier or when using a strongly ordered architecture, readX() should at least have a compiler barrier in it to

[PATCH v2 2/2] io: prevent compiler reordering on the default readX() implementation

The default implementation of mapping readX() to __raw_readX() is wrong. readX() has stronger ordering semantics. Compiler is allowed to reorder __raw_readX(). In the abscence of a read barrier or when using a strongly ordered architecture, readX() should at least have a compiler barrier in it to

[PATCH] powerpc: fix spelling mistake: "Usupported" -> "Unsupported"

From: Colin Ian King Trivial fix to spelling mistake in bootx_printf message text Signed-off-by: Colin Ian King --- arch/powerpc/platforms/powermac/bootx_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] powerpc: fix spelling mistake: "Usupported" -> "Unsupported"

From: Colin Ian King Trivial fix to spelling mistake in bootx_printf message text Signed-off-by: Colin Ian King --- arch/powerpc/platforms/powermac/bootx_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/platforms/powermac/bootx_init.c

Re: [RFC] new SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE wrappers

On Fri, Mar 30, 2018 at 12:58:02PM +0200, Ingo Molnar wrote: > * John Paul Adrian Glaubitz wrote: > > > On 03/27/2018 12:40 PM, Linus Torvalds wrote: > > > On Mon, Mar 26, 2018 at 4:37 PM, John Paul Adrian Glaubitz > > > wrote: > > >>

Re: [RFC] new SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE wrappers

On Fri, Mar 30, 2018 at 12:58:02PM +0200, Ingo Molnar wrote: > * John Paul Adrian Glaubitz wrote: > > > On 03/27/2018 12:40 PM, Linus Torvalds wrote: > > > On Mon, Mar 26, 2018 at 4:37 PM, John Paul Adrian Glaubitz > > > wrote: > > >> > > >> What about a tarball with a minimal Debian x32

Re: [PATCH] selftests/ftrace: fix spelling mistake: "tiggers" -> "triggers"

On 03/29/2018 12:04 PM, Steven Rostedt wrote: > On Thu, 29 Mar 2018 11:54:28 -0600 > Shuah Khan wrote: > >> I will pick this up with your Ack Steve, unless you want include >> it in your pull request. > > You or Janitors can take it. > Okay we can leave it to the Janitors

Re: [PATCH] selftests/ftrace: fix spelling mistake: "tiggers" -> "triggers"

On 03/29/2018 12:04 PM, Steven Rostedt wrote: > On Thu, 29 Mar 2018 11:54:28 -0600 > Shuah Khan wrote: > >> I will pick this up with your Ack Steve, unless you want include >> it in your pull request. > > You or Janitors can take it. > Okay we can leave it to the Janitors then. thanks, --

[PATCH] ISDN: eicon: message: remove redundant check

Check on plci->internal_command is unnecessary. Addresses-Coverity-ID: 1268778 ("Identical code for different branches") Signed-off-by: Gustavo A. R. Silva --- drivers/isdn/hardware/eicon/message.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH] ISDN: eicon: message: remove redundant check

Check on plci->internal_command is unnecessary. Addresses-Coverity-ID: 1268778 ("Identical code for different branches") Signed-off-by: Gustavo A. R. Silva --- drivers/isdn/hardware/eicon/message.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/isdn/hardware/eicon/message.c

[PATCH 32/32] random: convert to ->poll_mask

The big change is that random_read_wait and random_write_wait are merged into a single waitqueue that uses keyed wakeups. Because wait_event_* doesn't know about that this will lead to occassional spurious wakeups in _random_read and add_hwgenerator_randomness, but wait_event_* is designed to

[PATCH 32/32] random: convert to ->poll_mask

The big change is that random_read_wait and random_write_wait are merged into a single waitqueue that uses keyed wakeups. Because wait_event_* doesn't know about that this will lead to occassional spurious wakeups in _random_read and add_hwgenerator_randomness, but wait_event_* is designed to

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