Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 11:52 AM, Al Viro wrote: > > And that call can happen as soon as we return from __blockdev_direct_IO() > (even earlier, actually). As soon as that happens, the reference to > struct file we'd acquired in io_submit_one() is dropped. If descriptor > table had been shared,

[GIT PULL] UBI/UBIFS fixes for 4.9-rc3

Linus, The following changes since commit 14970f204b1993af7459d5bd34aaff38dfee6670: Merge branch 'akpm' (patches from Andrew) (2016-10-27 19:58:39 -0700) are available in the git repository at: git://git.infradead.org/linux-ubifs.git tags/upstream-4.9-rc3 for you to fetch changes up to

[GIT PULL] ARM: SoC fixes

Hi Linus, The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for you to fetch changes up to

[GIT PULL] ARM: SoC fixes

Hi Linus, The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for you to fetch changes up to

Re: [PATCH] [net-next] net: ip, diag: include net/inet_sock.h

From: Arnd Bergmann Date: Tue, 25 Oct 2016 17:53:22 +0200 > The newly added raw_diag.c fails to build in some configurations > unless we include this header: > > In file included from net/ipv4/raw_diag.c:6:0: > include/net/raw.h:71:21: error: field 'inet' has incomplete type >

Re: [PATCH] [net-next] net: ip, diag: include net/inet_sock.h

From: Arnd Bergmann Date: Tue, 25 Oct 2016 17:53:22 +0200 > The newly added raw_diag.c fails to build in some configurations > unless we include this header: > > In file included from net/ipv4/raw_diag.c:6:0: > include/net/raw.h:71:21: error: field 'inet' has incomplete type >

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 10:47:58AM -0700, Linus Torvalds wrote: > Also, honestly, make it use a helper: "aio_file_start_write()" and > "aio_file_end_write()" that has the comments and the lockdep games. > > Because that patch is just too effing ugly. > > Does something like the attached work

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 10:47:58AM -0700, Linus Torvalds wrote: > Also, honestly, make it use a helper: "aio_file_start_write()" and > "aio_file_end_write()" that has the comments and the lockdep games. > > Because that patch is just too effing ugly. > > Does something like the attached work

Applied "spi: dspi: clear SPI_SR before enable interrupt" to the spi tree

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

Applied "spi: dspi: clear SPI_SR before enable interrupt" to the spi tree

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

Re: [RFC 1/3] regulator: core: Add over current changed event

On Fri, Oct 28, 2016 at 09:41:44PM +0200, Axel Haslam wrote: > i think today each time an event occurs a notification is sent with the > corresponding flag(s) set. Right, so I think the problem here is actually that you called this REGULATOR_EVENT_OVER_CURRENT_CHANGE with the _CHANGE on the end

Re: [RFC 1/3] regulator: core: Add over current changed event

On Fri, Oct 28, 2016 at 09:41:44PM +0200, Axel Haslam wrote: > i think today each time an event occurs a notification is sent with the > corresponding flag(s) set. Right, so I think the problem here is actually that you called this REGULATOR_EVENT_OVER_CURRENT_CHANGE with the _CHANGE on the end

Re: [PATCH v4 6/8] dt-bindings: Add support for Amlogic GXBB SCPI Interface

Hi, On Wed, Oct 5, 2016 at 12:33 AM, Neil Armstrong wrote: > Acked-by: Rob Herring > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/arm/arm,scpi.txt | 8 +--- > 1 file changed, 5 insertions(+), 3

Re: [PATCH v4 6/8] dt-bindings: Add support for Amlogic GXBB SCPI Interface

Hi, On Wed, Oct 5, 2016 at 12:33 AM, Neil Armstrong wrote: > Acked-by: Rob Herring > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/arm/arm,scpi.txt | 8 +--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git

Re: [PATCH v10 01/19] vfio: Mediated device Core driver

On 10/29/2016 06:06 PM, Kirti Wankhede wrote: > > > On 10/29/2016 10:00 AM, Jike Song wrote: >> On 10/27/2016 05:29 AM, Kirti Wankhede wrote: >>> +int mdev_register_device(struct device *dev, const struct parent_ops *ops) >>> +{ >>> + int ret; >>> + struct parent_device *parent; >>> + >>> +

Re: [PATCH v10 01/19] vfio: Mediated device Core driver

On 10/29/2016 06:06 PM, Kirti Wankhede wrote: > > > On 10/29/2016 10:00 AM, Jike Song wrote: >> On 10/27/2016 05:29 AM, Kirti Wankhede wrote: >>> +int mdev_register_device(struct device *dev, const struct parent_ops *ops) >>> +{ >>> + int ret; >>> + struct parent_device *parent; >>> + >>> +

Applied "spi: sun4i: Allow transfers larger than FIFO size" to the spi tree

The patch spi: sun4i: Allow transfers larger than FIFO size has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: wm8580: Fix non static symbol warnings" to the asoc tree

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

Applied "spi: sun4i: Allow transfers larger than FIFO size" to the spi tree

The patch spi: sun4i: Allow transfers larger than FIFO size has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: wm8580: Fix non static symbol warnings" to the asoc tree

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

Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver

On Wed 26 Oct 16:32 PDT 2016, Michael Scott wrote: > Initial pinctrl driver for QCOM msm8994 platforms. > > In order to continue the initial board support for QCOM msm8994/msm8992 > presented in patches from Jeremy McNicoll , let's put > a proper pinctrl driver in place. >

Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver

On Wed 26 Oct 16:32 PDT 2016, Michael Scott wrote: > Initial pinctrl driver for QCOM msm8994 platforms. > > In order to continue the initial board support for QCOM msm8994/msm8992 > presented in patches from Jeremy McNicoll , let's put > a proper pinctrl driver in place. > > Currently, the DT

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

On Sat, 2016-10-29 at 19:59 +0200, Andrey Konovalov wrote: > Hi Eric, > > Tested with both patches applied, still seeing the warning. > > Thanks! Arg, sorry, this was at the wrong place. Thanks for testing ! diff --git a/net/dccp/output.c b/net/dccp/output.c index b66c84db0766..2548edff86ff

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

On Sat, 2016-10-29 at 19:59 +0200, Andrey Konovalov wrote: > Hi Eric, > > Tested with both patches applied, still seeing the warning. > > Thanks! Arg, sorry, this was at the wrong place. Thanks for testing ! diff --git a/net/dccp/output.c b/net/dccp/output.c index b66c84db0766..2548edff86ff

Re: [GIT PULL] STi DT update for v4.10 round 1

Hi, On Thu, Oct 20, 2016 at 04:27:10PM +0200, Patrice Chotard wrote: > Hi Arnd, Kevin, Olof > > PLease consider this first round of STi dts update for v4.10 : > > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) >

Re: [GIT PULL] STi defconfig updates for v4.10

On Thu, Oct 20, 2016 at 05:20:27PM +0200, Patrice Chotard wrote: > Hi Olof, Arnd and Kevin, > > Please consider this first round of multi_v7_defconfig updates for v4.10 : > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50

Re: [GIT PULL] STi DT update for v4.10 round 1

Hi, On Thu, Oct 20, 2016 at 04:27:10PM +0200, Patrice Chotard wrote: > Hi Arnd, Kevin, Olof > > PLease consider this first round of STi dts update for v4.10 : > > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) >

Re: [GIT PULL] STi defconfig updates for v4.10

On Thu, Oct 20, 2016 at 05:20:27PM +0200, Patrice Chotard wrote: > Hi Olof, Arnd and Kevin, > > Please consider this first round of multi_v7_defconfig updates for v4.10 : > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

Hi Eric, Tested with both patches applied, still seeing the warning. Thanks! On Sat, Oct 29, 2016 at 7:43 PM, Eric Dumazet wrote: > On Sat, 2016-10-29 at 19:06 +0200, Andrey Konovalov wrote: >> Hi Cong, >> >> Tested with your patch, still getting a warning, though it's

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

Hi Eric, Tested with both patches applied, still seeing the warning. Thanks! On Sat, Oct 29, 2016 at 7:43 PM, Eric Dumazet wrote: > On Sat, 2016-10-29 at 19:06 +0200, Andrey Konovalov wrote: >> Hi Cong, >> >> Tested with your patch, still getting a warning, though it's a little >> different:

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 8:20 AM, Christoph Hellwig wrote: > > We can't as that would not fix the use after free (at least for the lockdep > case - otherwise the call is a no-op). Once iter_op returns aio_complete > might have dropped our reference to the file, and another thread

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 8:20 AM, Christoph Hellwig wrote: > > We can't as that would not fix the use after free (at least for the lockdep > case - otherwise the call is a no-op). Once iter_op returns aio_complete > might have dropped our reference to the file, and another thread might > have

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

On Sat, 2016-10-29 at 19:06 +0200, Andrey Konovalov wrote: > Hi Cong, > > Tested with your patch, still getting a warning, though it's a little > different: > > [ cut here ] > WARNING: CPU: 1 PID: 3876 at kernel/sched/core.c:7724 > __might_sleep+0x14c/0x1a0

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

On Sat, 2016-10-29 at 19:06 +0200, Andrey Konovalov wrote: > Hi Cong, > > Tested with your patch, still getting a warning, though it's a little > different: > > [ cut here ] > WARNING: CPU: 1 PID: 3876 at kernel/sched/core.c:7724 > __might_sleep+0x14c/0x1a0

Re: [PATCH 00/14] introduce the BFQ-v0 I/O scheduler as an extra scheduler

Hey, people, don't you annoy yourselves all the time? The BFQ patches provide a useful alternative for the code called "legacy" by you, while you're not maintaining the base any more, and just about to invent something new, again. ?! When blk-mq has no scheduler -> work on it. When you want to

Re: [PATCH 00/14] introduce the BFQ-v0 I/O scheduler as an extra scheduler

Hey, people, don't you annoy yourselves all the time? The BFQ patches provide a useful alternative for the code called "legacy" by you, while you're not maintaining the base any more, and just about to invent something new, again. ?! When blk-mq has no scheduler -> work on it. When you want to

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

Hi Cong, Tested with your patch, still getting a warning, though it's a little different: [ cut here ] WARNING: CPU: 1 PID: 3876 at kernel/sched/core.c:7724 __might_sleep+0x14c/0x1a0 kernel/sched/core.c:7719 do not call blocking ops when !TASK_RUNNING; state=1 set at []

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

Hi Cong, Tested with your patch, still getting a warning, though it's a little different: [ cut here ] WARNING: CPU: 1 PID: 3876 at kernel/sched/core.c:7724 __might_sleep+0x14c/0x1a0 kernel/sched/core.c:7719 do not call blocking ops when !TASK_RUNNING; state=1 set at []

Re: [RFC PATCH] kbuild: add -fno-PIE

On 2016-10-29 12:10 +0200, Tomas Janousek wrote: > On Mon, Oct 24, 2016 at 07:32:30PM +0200, Sven Joachim wrote: >> The attached patch works for me with Debian's gcc-6 package. > > I tried your patch when building 4.8.5 on an up-to-date Debian testing and > still got this: > > AS

Re: [RFC PATCH] kbuild: add -fno-PIE

On 2016-10-29 12:10 +0200, Tomas Janousek wrote: > On Mon, Oct 24, 2016 at 07:32:30PM +0200, Sven Joachim wrote: >> The attached patch works for me with Debian's gcc-6 package. > > I tried your patch when building 4.8.5 on an up-to-date Debian testing and > still got this: > > AS

Re: [PATCH v6 02/11] locking/osq: Drop the overload of osq_lock()

On Fri, 28 Oct 2016, Pan Xinhui wrote: /* * If we need to reschedule bail... so we can block. +* Use vcpu_is_preempted to detech lock holder preemption issue ^^ detect + * and break. Could you

Re: [PATCH v6 02/11] locking/osq: Drop the overload of osq_lock()

On Fri, 28 Oct 2016, Pan Xinhui wrote: /* * If we need to reschedule bail... so we can block. +* Use vcpu_is_preempted to detech lock holder preemption issue ^^ detect + * and break. Could you

[GIT PULL] Driver core fixes for 4.9-rc3

The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.9-rc3 for you to fetch changes up to

[GIT PULL] Char/Misc driver fixes for 4.9-rc3

The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.9-rc3 for you to fetch changes up to

[GIT PULL] Staging/IIO driver fixes for 4.9-rc3

The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.9-rc3 for you to fetch changes up to

[GIT PULL] Driver core fixes for 4.9-rc3

The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.9-rc3 for you to fetch changes up to

[GIT PULL] Char/Misc driver fixes for 4.9-rc3

The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.9-rc3 for you to fetch changes up to

[GIT PULL] Staging/IIO driver fixes for 4.9-rc3

The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.9-rc3 for you to fetch changes up to

[GIT PULL] TTY/Serial driver fixes for 4.9-rc3

The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.9-rc3 for you to fetch changes up to

[GIT PULL] TTY/Serial driver fixes for 4.9-rc3

The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.9-rc3 for you to fetch changes up to

[GIT PULL] USB driver fixes for 4.9-rc3

The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.9-rc3 for you to fetch changes up to

[GIT PULL] USB driver fixes for 4.9-rc3

The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.9-rc3 for you to fetch changes up to

Re: Section mismatch in reference from the function generic_NCR5380_isa_match()

On Sat, Oct 29, 2016 at 12:12:21PM +0200, Borislav Petkov wrote: > Hi, > > I'm seeing this during randconfig builds: > > WARNING: vmlinux.o(.text+0x1588439): Section mismatch in reference from the > function generic_NCR5380_isa_match() to the function .init.text:probe_intr() > The function

Re: Section mismatch in reference from the function generic_NCR5380_isa_match()

On Sat, Oct 29, 2016 at 12:12:21PM +0200, Borislav Petkov wrote: > Hi, > > I'm seeing this during randconfig builds: > > WARNING: vmlinux.o(.text+0x1588439): Section mismatch in reference from the > function generic_NCR5380_isa_match() to the function .init.text:probe_intr() > The function

Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver

Resending: The mailing lists bounced due me being silly and replying on my phone. Please reply to this email instead of the last one. On 10/29/2016 01:27 AM, Linus Walleij wrote: On Thu, Oct 27, 2016 at 1:32 AM, Michael Scott wrote: Initial pinctrl driver for QCOM

Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver

Resending: The mailing lists bounced due me being silly and replying on my phone. Please reply to this email instead of the last one. On 10/29/2016 01:27 AM, Linus Walleij wrote: On Thu, Oct 27, 2016 at 1:32 AM, Michael Scott wrote: Initial pinctrl driver for QCOM msm8994 platforms. In

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 05:12:30PM +0100, Al Viro wrote: > NAK, with apologies for not having looked at that earlier. The bug is real, > all right, but this is not a solution - both incomplete and far too brittle. > > Why do we play that kind of insane games, anyway? Why not e.g. refcount >

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 05:12:30PM +0100, Al Viro wrote: > NAK, with apologies for not having looked at that earlier. The bug is real, > all right, but this is not a solution - both incomplete and far too brittle. > > Why do we play that kind of insane games, anyway? Why not e.g. refcount >

[PATCH -next] ASoC: wm8580: Fix non static symbol warnings

From: Wei Yongjun Fixes the following sparse warnings: sound/soc/codecs/wm8580.c:988:33: warning: symbol 'wm8580_data' was not declared. Should it be static? sound/soc/codecs/wm8580.c:992:33: warning: symbol 'wm8581_data' was not declared. Should it be static?

[PATCH -next] ASoC: wm8580: Fix non static symbol warnings

From: Wei Yongjun Fixes the following sparse warnings: sound/soc/codecs/wm8580.c:988:33: warning: symbol 'wm8580_data' was not declared. Should it be static? sound/soc/codecs/wm8580.c:992:33: warning: symbol 'wm8581_data' was not declared. Should it be static? Signed-off-by: Wei Yongjun ---

[PATCH -next] ASoC: wm8580: Fix non static symbol warnings

From: Wei Yongjun Fixes the following sparse warnings: sound/soc/codecs/wm8580.c:988:33: warning: symbol 'wm8580_data' was not declared. Should it be static? sound/soc/codecs/wm8580.c:992:33: warning: symbol 'wm8581_data' was not declared. Should it be static?

[PATCH -next] ASoC: wm8580: Fix non static symbol warnings

From: Wei Yongjun Fixes the following sparse warnings: sound/soc/codecs/wm8580.c:988:33: warning: symbol 'wm8580_data' was not declared. Should it be static? sound/soc/codecs/wm8580.c:992:33: warning: symbol 'wm8581_data' was not declared. Should it be static? Signed-off-by: Wei Yongjun ---

Re: [PATCH 2/3] ASoC: lpass-platform: Fix broken pcm data usage

On Fri, Oct 28, 2016 at 04:32:19PM +0100, Srinivas Kandagatla wrote: > This patch fixes lpass-platform driver which was broken in v4.9-rc1. > lpass_pcm_data data structure holds information specific to stream. > Holding a single private pointer to it in global lpass_data > will not work, because

Re: [PATCH 2/3] ASoC: lpass-platform: Fix broken pcm data usage

On Fri, Oct 28, 2016 at 04:32:19PM +0100, Srinivas Kandagatla wrote: > This patch fixes lpass-platform driver which was broken in v4.9-rc1. > lpass_pcm_data data structure holds information specific to stream. > Holding a single private pointer to it in global lpass_data > will not work, because

Re: [PATCH 1/3] ASoC: lpass-platform: use dma_ch instead of rdma_ch/wrdma_ch

On Fri, Oct 28, 2016 at 04:32:18PM +0100, Srinivas Kandagatla wrote: > This patch cleans up usage of wrdma_ch and rdma_ch variables into a > common variable dma_ch, As there is no real use of tracking the dma > channel in two different variables based on stream direction. > > Signed-off-by:

Re: [PATCH 1/3] ASoC: lpass-platform: use dma_ch instead of rdma_ch/wrdma_ch

On Fri, Oct 28, 2016 at 04:32:18PM +0100, Srinivas Kandagatla wrote: > This patch cleans up usage of wrdma_ch and rdma_ch variables into a > common variable dma_ch, As there is no real use of tracking the dma > channel in two different variables based on stream direction. > > Signed-off-by:

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 05:20:17PM +0200, Christoph Hellwig wrote: > On Sat, Oct 29, 2016 at 01:24:51PM +0100, Al Viro wrote: > > How about taking this chunk (i.e. telling lockdep that we are not holding > > this > > thing) past the iter_op() call, where file_end_write() used to be? > > We can't

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 05:20:17PM +0200, Christoph Hellwig wrote: > On Sat, Oct 29, 2016 at 01:24:51PM +0100, Al Viro wrote: > > How about taking this chunk (i.e. telling lockdep that we are not holding > > this > > thing) past the iter_op() call, where file_end_write() used to be? > > We can't

[PATCH -next] brd: make symbol rd_size static

From: Wei Yongjun Fixes the following sparse warning: drivers/block/brd.c:411:15: warning: symbol 'rd_size' was not declared. Should it be static? Signed-off-by: Wei Yongjun --- drivers/block/brd.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH -next] brd: make symbol rd_size static

From: Wei Yongjun Fixes the following sparse warning: drivers/block/brd.c:411:15: warning: symbol 'rd_size' was not declared. Should it be static? Signed-off-by: Wei Yongjun --- drivers/block/brd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/brd.c

Re: [PATCH v2 net-next] virtio-net: Update the mtu code to match virtio spec

From: Aaron Conole Date: Tue, 25 Oct 2016 16:12:12 -0400 > The virtio committee recently ratified a change, VIRTIO-152, which > defines the mtu field to be 'max' MTU, not simply desired MTU. > > This commit brings the virtio-net device in compliance with VIRTIO-152. > >

Re: [PATCH v2 net-next] virtio-net: Update the mtu code to match virtio spec

From: Aaron Conole Date: Tue, 25 Oct 2016 16:12:12 -0400 > The virtio committee recently ratified a change, VIRTIO-152, which > defines the mtu field to be 'max' MTU, not simply desired MTU. > > This commit brings the virtio-net device in compliance with VIRTIO-152. > > Additionally, drop the

Re: [PATCH] coredump: clarify "unsafe core_pattern" warning

On Sat, Oct 29, 2016 at 8:21 AM, Alexey Dobriyan wrote: > I was amused to find "unsafe core_pattern" warning having these lines > in /etc/sysctl.conf: > > fs.suid_dumpable=2 > kernel.core_pattern=/core/core-%e-%p-%E > kernel.core_uses_pid=0 > > Turns

Re: [PATCH] coredump: clarify "unsafe core_pattern" warning

On Sat, Oct 29, 2016 at 8:21 AM, Alexey Dobriyan wrote: > I was amused to find "unsafe core_pattern" warning having these lines > in /etc/sysctl.conf: > > fs.suid_dumpable=2 > kernel.core_pattern=/core/core-%e-%p-%E > kernel.core_uses_pid=0 > > Turns out kernel is formally

Re: [PATCH] HID: intel-ish-hid: Fix !CONFIG_PM build warning

On Sat, 2016-10-29 at 13:17 +0200, Borislav Petkov wrote: > From: Borislav Petkov > > Fix > >   drivers/hid/intel-ish-hid/ipc/pci-ish.c:247:12: warning: > ‘ish_suspend’ defined but not used [-Wunused-function] >    static int ish_suspend(struct device *device) >   ^ >  

Re: [PATCH] HID: intel-ish-hid: Fix !CONFIG_PM build warning

On Sat, 2016-10-29 at 13:17 +0200, Borislav Petkov wrote: > From: Borislav Petkov > > Fix > >   drivers/hid/intel-ish-hid/ipc/pci-ish.c:247:12: warning: > ‘ish_suspend’ defined but not used [-Wunused-function] >    static int ish_suspend(struct device *device) >   ^ >  

Re: [PATCH] ARM: mm: add ARM_L1_CACHE_SHIFT_7 for UniPhier outer cache

Hi. If there is no objection to this patch, I will put it into Russell's patch tracker. 2016-10-19 21:39 GMT+09:00 Masahiro Yamada : > The UniPhier outer cache (arch/arm/mm/cache-uniphier.c) has 128 byte > line length and its tags are also managed per 128 byte

Re: [PATCH] ARM: mm: add ARM_L1_CACHE_SHIFT_7 for UniPhier outer cache

Hi. If there is no objection to this patch, I will put it into Russell's patch tracker. 2016-10-19 21:39 GMT+09:00 Masahiro Yamada : > The UniPhier outer cache (arch/arm/mm/cache-uniphier.c) has 128 byte > line length and its tags are also managed per 128 byte line. This > is very unfortunate,

Re: [PATCH 23/60] block: introduce flag QUEUE_FLAG_NO_MP

On Sat, Oct 29, 2016 at 04:08:22PM +0800, Ming Lei wrote: > MD(especially raid1 and raid10) is a bit difficult to support > multipage bvec, so introduce this flag for not enabling multipage > bvec, then MD can still accept singlepage bvec only, and once > direct access to bvec table in MD and

Re: [PATCH 23/60] block: introduce flag QUEUE_FLAG_NO_MP

On Sat, Oct 29, 2016 at 04:08:22PM +0800, Ming Lei wrote: > MD(especially raid1 and raid10) is a bit difficult to support > multipage bvec, so introduce this flag for not enabling multipage > bvec, then MD can still accept singlepage bvec only, and once > direct access to bvec table in MD and

Re: [PATCH 01/60] block: bio: introduce bio_init_with_vec_table()

Just add the two arguments to bio_init instead of adding a second function with a way too long name.

Re: [PATCH 01/60] block: bio: introduce bio_init_with_vec_table()

Just add the two arguments to bio_init instead of adding a second function with a way too long name.

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 01:24:51PM +0100, Al Viro wrote: > How about taking this chunk (i.e. telling lockdep that we are not holding this > thing) past the iter_op() call, where file_end_write() used to be? We can't as that would not fix the use after free (at least for the lockdep case -

Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)

On Sat, Oct 29, 2016 at 01:24:51PM +0100, Al Viro wrote: > How about taking this chunk (i.e. telling lockdep that we are not holding this > thing) past the iter_op() call, where file_end_write() used to be? We can't as that would not fix the use after free (at least for the lockdep case -

[PATCH 4.4 18/51] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arend Van Spriel commit ded89912156b1a47d940a0c954c43afbabd0c42c upstream. User-space can choose to omit NL80211_ATTR_SSID and only provide raw IE TLV data. When

[PATCH 4.4 22/51] tunnels: Remove encapsulation offloads on decap.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Gross commit a09a4c8dd1ec7f830e1fb9e59eb72bddc965d168 upstream. If a packet is either locally encapsulated or processed through GRO it is marked with the offloads that

[PATCH 4.4 10/51] drm/radeon: change vblank_times calculation method to reduce computational error.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 02cfb5fccb0f9f968f0e208d89d9769aa16267bc upstream. Ported from Rex's amdgpu change. Signed-off-by: Alex Deucher

[PATCH 4.4 04/51] drm/amdgpu/dce8: disable hpd on local panels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 324082586cc5918e3230f0b2f326656c653201eb upstream. Otherwise we can get a hotplug interrupt storm when we turn the panel off if hpd interrupts

[PATCH 4.4 05/51] drm/amdgpu/dce11: disable hpd on local panels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 3a9d993ee9809c217f4322623a9b78c8d17fdd1f upstream. Otherwise we can get a hotplug interrupt storm when we turn the panel off if hpd interrupts

[PATCH 4.4 14/51] Revert "drm/i915: Check live status before reading edid"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Weinehall commit 23f889bdf6ee5cfff012d8b09f6bec920c691696 upstream. This reverts commit 237ed86c693d8a8e4db476976aeb30df4deac74b. Our current

[PATCH 4.4 16/51] drm/i915: Unalias obj->phys_handle and obj->userptr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit ca5732c53bf66ad755284786897e0dd10330de87 upstream. We use obj->phys_handle to choose the pread/pwrite path, but as obj->phys_handle is a union

[PATCH 4.4 18/51] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arend Van Spriel commit ded89912156b1a47d940a0c954c43afbabd0c42c upstream. User-space can choose to omit NL80211_ATTR_SSID and only provide raw IE TLV data. When doing so it can provide SSID

[PATCH 4.4 22/51] tunnels: Remove encapsulation offloads on decap.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Gross commit a09a4c8dd1ec7f830e1fb9e59eb72bddc965d168 upstream. If a packet is either locally encapsulated or processed through GRO it is marked with the offloads that it requires.

[PATCH 4.4 05/51] drm/amdgpu/dce11: disable hpd on local panels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 3a9d993ee9809c217f4322623a9b78c8d17fdd1f upstream. Otherwise we can get a hotplug interrupt storm when we turn the panel off if hpd interrupts were enabled by the bios.

[PATCH 4.4 14/51] Revert "drm/i915: Check live status before reading edid"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Weinehall commit 23f889bdf6ee5cfff012d8b09f6bec920c691696 upstream. This reverts commit 237ed86c693d8a8e4db476976aeb30df4deac74b. Our current implementation of live status check (repeat

[PATCH 4.4 10/51] drm/radeon: change vblank_times calculation method to reduce computational error.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 02cfb5fccb0f9f968f0e208d89d9769aa16267bc upstream. Ported from Rex's amdgpu change. Signed-off-by: Alex Deucher Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.4 04/51] drm/amdgpu/dce8: disable hpd on local panels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 324082586cc5918e3230f0b2f326656c653201eb upstream. Otherwise we can get a hotplug interrupt storm when we turn the panel off if hpd interrupts were enabled by the bios.

[PATCH 4.4 16/51] drm/i915: Unalias obj->phys_handle and obj->userptr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit ca5732c53bf66ad755284786897e0dd10330de87 upstream. We use obj->phys_handle to choose the pread/pwrite path, but as obj->phys_handle is a union with obj->userptr, we then

[PATCH 4.4 02/51] drm/amdgpu: fix IB alignment for UVD

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit c4795ca642b8bd76b5b6ffba41ba909543273d43 upstream. According to the hw team, it should be 16, not 8. Cc: Peter Fang

[PATCH 4.4 21/51] tunnels: Dont apply GRO to multiple layers of encapsulation.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Gross commit fac8e0f579695a3ecbc4d3cac369139d7f819971 upstream. When drivers express support for TSO of encapsulated packets, they only mean that they can do it for one

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