Re: [PATCH 1/4] rcu: Allow for page faults in NMI handlers

On Sun, Sep 24, 2017 at 12:42:32PM -0700, Linus Torvalds wrote: > On Sat, Sep 23, 2017 at 1:56 PM, Steven Rostedt wrote: > > + > > + /* Page faults can happen in NMI handlers, so check... */ > > + if (READ_ONCE(rdtp->dynticks_nmi_nesting)) > > + return; > > + > > What

[PATCH v3 07/10] dmaengine: sun6i: Retrieve channel count/max request from devicetree

To avoid introduction of a new compatible for each small SoC/DMA controller variation, move the definition of the channel count to the devicetree. The number of vchans is no longer explicit, but limited by the highest port/DMA request number. The result is a slight overallocation for SoCs with a

[PATCH v3 09/10] arm64: allwinner: a64: Add device node for DMA controller

The A64 SoC has a DMA controller that supports 8 DMA channels to and from various peripherals. The last used DRQ port is 27. Add a device node for it. Signed-off-by: Stefan Brüns --- Changes in v3: - Drop leading 0 from dma controller unit name Changes in v2:

[PATCH v3 06/10] arm64: allwinner: a64: Add devicetree binding for DMA controller

The A64 is register compatible with the H3, but has a different number of dma channels and request ports. Attach additional properties to the node to allow future reuse of the compatible for controllers with different number of channels/requests. If dma-requests is not specified, the register

[PATCH v3 08/10] dmaengine: sun6i: Add support for Allwinner A64 and compatibles

The A64 SoC has the same dma engine as the H3 (sun8i), with a reduced amount of physical channels. To allow future reuse of the compatible, leave the channel count etc. in the config data blank and retrieve it from the devicetree. Signed-off-by: Stefan Brüns

[PATCH v3 09/10] arm64: allwinner: a64: Add device node for DMA controller

The A64 SoC has a DMA controller that supports 8 DMA channels to and from various peripherals. The last used DRQ port is 27. Add a device node for it. Signed-off-by: Stefan Brüns --- Changes in v3: - Drop leading 0 from dma controller unit name Changes in v2: None

[PATCH v3 06/10] arm64: allwinner: a64: Add devicetree binding for DMA controller

The A64 is register compatible with the H3, but has a different number of dma channels and request ports. Attach additional properties to the node to allow future reuse of the compatible for controllers with different number of channels/requests. If dma-requests is not specified, the register

[PATCH v3 08/10] dmaengine: sun6i: Add support for Allwinner A64 and compatibles

The A64 SoC has the same dma engine as the H3 (sun8i), with a reduced amount of physical channels. To allow future reuse of the compatible, leave the channel count etc. in the config data blank and retrieve it from the devicetree. Signed-off-by: Stefan Brüns Acked-by: Maxime Ripard ---

[PATCH v3 05/10] dmaengine: sun6i: Move number of pchans/vchans/request to device struct

Preparatory patch: If the same compatible is used for different SoCs which have a common register layout, but different number of channels, the channel count can no longer be stored in the config. Store it in the device structure instead. Signed-off-by: Stefan Brüns

[PATCH v3 02/10] dmaengine: sun6i: Correct burst length field offsets for H3

For the H3, the burst lengths field offsets in the channel configuration register differs from earlier SoC generations. Using the A31 register macros actually configured the H3 controller do to bursts of length 1 always, which although working leads to higher bus utilisation. Signed-off-by:

[PATCH v3 05/10] dmaengine: sun6i: Move number of pchans/vchans/request to device struct

Preparatory patch: If the same compatible is used for different SoCs which have a common register layout, but different number of channels, the channel count can no longer be stored in the config. Store it in the device structure instead. Signed-off-by: Stefan Brüns Acked-by: Maxime Ripard ---

[PATCH v3 02/10] dmaengine: sun6i: Correct burst length field offsets for H3

For the H3, the burst lengths field offsets in the channel configuration register differs from earlier SoC generations. Using the A31 register macros actually configured the H3 controller do to bursts of length 1 always, which although working leads to higher bus utilisation. Signed-off-by:

[PATCH v3 10/10] arm64: allwinner: a64: add dma controller references to spi nodes

The spi controller nodes omit the dma controller/channel references, add it. This does not yet enable DMA for SPI transfers, as the spi-sun6i driver lacks support for DMA, but always uses PIO to the FIFO. Signed-off-by: Stefan Brüns --- Changes in v3: None Changes

Linux 4.14-rc2

I'm back to my usual Sunday release schedule, and rc2 is out there in all the normal places. This was a fairly usual rc2, with a very quiet beginning of the week, and then most changes came in on Friday afternoon and Saturday (with the last few ones showing up Sunday morning). Normally I tend to

[PATCH v3 10/10] arm64: allwinner: a64: add dma controller references to spi nodes

The spi controller nodes omit the dma controller/channel references, add it. This does not yet enable DMA for SPI transfers, as the spi-sun6i driver lacks support for DMA, but always uses PIO to the FIFO. Signed-off-by: Stefan Brüns --- Changes in v3: None Changes in v2: None

Linux 4.14-rc2

I'm back to my usual Sunday release schedule, and rc2 is out there in all the normal places. This was a fairly usual rc2, with a very quiet beginning of the week, and then most changes came in on Friday afternoon and Saturday (with the last few ones showing up Sunday morning). Normally I tend to

Re: [lkp-robot] [sched/fair] 6d46bd3d97: netperf.Throughput_tps -11.3% regression

Hi Mike, On Sun, Sep 17, 2017 at 10:30 PM, Mike Galbraith wrote: > On Sun, 2017-09-17 at 14:41 -0700, Joel Fernandes wrote: >> Hi Mike, >> >> On Sun, Sep 17, 2017 at 9:47 AM, Mike Galbraith wrote: >> > On Sat, 2017-09-16 at 23:42 -0700, Joel Fernandes wrote: >> >>

Re: [lkp-robot] [sched/fair] 6d46bd3d97: netperf.Throughput_tps -11.3% regression

Hi Mike, On Sun, Sep 17, 2017 at 10:30 PM, Mike Galbraith wrote: > On Sun, 2017-09-17 at 14:41 -0700, Joel Fernandes wrote: >> Hi Mike, >> >> On Sun, Sep 17, 2017 at 9:47 AM, Mike Galbraith wrote: >> > On Sat, 2017-09-16 at 23:42 -0700, Joel Fernandes wrote: >> >> >> >> Yes I understand.

[PATCH] PM / PCI: Do not resume any devices in pci_pm_prepare()

From: Rafael J. Wysocki It should not be necessary to resume devices with ignore_children set in pci_pm_prepare(), because they should be resumed explcitly by their children drivers during suspend if need be and they will be resumed by pci_pm_suspend() after that

[PATCH] PM / PCI: Do not resume any devices in pci_pm_prepare()

From: Rafael J. Wysocki It should not be necessary to resume devices with ignore_children set in pci_pm_prepare(), because they should be resumed explcitly by their children drivers during suspend if need be and they will be resumed by pci_pm_suspend() after that anyway, so avoid doing that.

[PATCH 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support

This patch adds logic to correctly setup the write timing parameters when blowing an OTP fuse for the i.MX7S/D. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 61

[PATCH 1/7] nvmem: imx-ocotp: Restrict OTP write to IMX6 processors

i.MX7S/D have a different scheme for addressing the OTP registers inside the OCOTP block. Currently it's possible to address the wrong OTP registers given the disparity between IMX6 and IMX7 OTP addressing. Since OTP programming is one-time destructive its important we restrict this interface

[PATCH 2/7] nvmem: imx-ocotp: Pass parameters via a struct

It will be useful in later patches to know the register access mode and bit-shift to apply to a given input offset. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 32

[PATCH 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support

This patch adds logic to correctly setup the write timing parameters when blowing an OTP fuse for the i.MX7S/D. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 61 ++- 1 file

[PATCH 1/7] nvmem: imx-ocotp: Restrict OTP write to IMX6 processors

i.MX7S/D have a different scheme for addressing the OTP registers inside the OCOTP block. Currently it's possible to address the wrong OTP registers given the disparity between IMX6 and IMX7 OTP addressing. Since OTP programming is one-time destructive its important we restrict this interface

[PATCH 2/7] nvmem: imx-ocotp: Pass parameters via a struct

It will be useful in later patches to know the register access mode and bit-shift to apply to a given input offset. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 32 ++-- 1 file changed,

[PATCH 4/7] nvmem: imx-ocotp: Move i.MX6 write clock setup to dedicated function

The i.MX7S/D has a different set of timing requirements, as a pre-cursor to adding the i.MX7 timing parameters, move the i.MX6 stuff to a dedicated function. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue ---

[PATCH 4/7] nvmem: imx-ocotp: Move i.MX6 write clock setup to dedicated function

The i.MX7S/D has a different set of timing requirements, as a pre-cursor to adding the i.MX7 timing parameters, move the i.MX6 stuff to a dedicated function. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 47

[PATCH 7/7] nvmem: imx-ocotp: Update module description

This imx-ocotp driver encapsulates support for a subset of both i.MX6 and i.MX7 processors. Update the module description to reflect. Fixes: 711d45477931 ("nvmem: octop: Add i.MX7D support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 2 +- 1

[PATCH 3/7] nvmem: imx-ocotp: Add support for banked OTP addressing

The i.MX7S/D takes the bank address in the CTRLn.ADDR field and the data value in one of the DATAx {0, 1, 2, 3} register fields. The current write routine is based on writing the CTRLn.ADDR field and writing a single DATA register only. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support")

[PATCH 6/7] nvmem: imx-ocotp: Enable i.MX7D OTP write support

After applying patches for both banked access and write timings we can re-enable the OTP write interface on i.MX7D processors. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 2 -- 1 file

[PATCH 7/7] nvmem: imx-ocotp: Update module description

This imx-ocotp driver encapsulates support for a subset of both i.MX6 and i.MX7 processors. Update the module description to reflect. Fixes: 711d45477931 ("nvmem: octop: Add i.MX7D support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 3/7] nvmem: imx-ocotp: Add support for banked OTP addressing

The i.MX7S/D takes the bank address in the CTRLn.ADDR field and the data value in one of the DATAx {0, 1, 2, 3} register fields. The current write routine is based on writing the CTRLn.ADDR field and writing a single DATA register only. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support")

[PATCH 6/7] nvmem: imx-ocotp: Enable i.MX7D OTP write support

After applying patches for both banked access and write timings we can re-enable the OTP write interface on i.MX7D processors. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 2 -- 1 file changed, 2 deletions(-) diff

[PATCH 0/7] Fix i.MX7D OCOTP write support

The current OCOTP driver added support for i.MX7 read access and then added support for i.MX6 write access. Between the two commits the fact that the added write routine was only appropriate for i.MX6 was missed. As a result its certain that attempting to write i.MX7 OTP fuses on Linux would fail

[PATCH 0/7] Fix i.MX7D OCOTP write support

The current OCOTP driver added support for i.MX7 read access and then added support for i.MX6 write access. Between the two commits the fact that the added write routine was only appropriate for i.MX6 was missed. As a result its certain that attempting to write i.MX7 OTP fuses on Linux would fail

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

On Mon, 2017-09-18 at 10:55 -0400, Mimi Zohar wrote: > On Mon, 2017-09-18 at 12:13 +0200, Jan Kara wrote: > > On Mon 18-09-17 10:19:25, Steven Whitehouse wrote: > > > On 17/09/17 17:38, Al Viro wrote: > > > >On Sun, Sep 17, 2017 at 09:34:01AM -0700, Linus Torvalds wrote: > > > >>Now, I suspect

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

On Mon, 2017-09-18 at 10:55 -0400, Mimi Zohar wrote: > On Mon, 2017-09-18 at 12:13 +0200, Jan Kara wrote: > > On Mon 18-09-17 10:19:25, Steven Whitehouse wrote: > > > On 17/09/17 17:38, Al Viro wrote: > > > >On Sun, Sep 17, 2017 at 09:34:01AM -0700, Linus Torvalds wrote: > > > >>Now, I suspect

Re: [PATCH] MAINTAINERS: Hibernation or S2R doesn't cover entire power directory

On Wed, Sep 20, 2017 at 5:58 PM, Viresh Kumar wrote: > The command: > > $ scripts/get_maintainer.pl -f drivers/base/power/opp/core.c > > is incorrectly picking maintainers from Hibernation and Suspend to RAM > as well, simply because the entries in MAINTAINERS file

Re: [PATCH] MAINTAINERS: Hibernation or S2R doesn't cover entire power directory

On Wed, Sep 20, 2017 at 5:58 PM, Viresh Kumar wrote: > The command: > > $ scripts/get_maintainer.pl -f drivers/base/power/opp/core.c > > is incorrectly picking maintainers from Hibernation and Suspend to RAM > as well, simply because the entries in MAINTAINERS file contains the > entire power

Re: [char-misc 1/2] mei: always use domain runtime pm callbacks.

On Sun, Sep 24, 2017 at 10:35 AM, Tomas Winkler wrote: > From: Alexander Usyskin > > This patch fixes a regression caused by the new changes > in the run wake handlers, pci_dev_run_wake() return true > when wake is possible from the software

Re: [char-misc 1/2] mei: always use domain runtime pm callbacks.

On Sun, Sep 24, 2017 at 10:35 AM, Tomas Winkler wrote: > From: Alexander Usyskin > > This patch fixes a regression caused by the new changes > in the run wake handlers, pci_dev_run_wake() return true > when wake is possible from the software perspective > not whether it is actually enabled.

[GIT PULL] DeviceTree fixes for 4.14

Hi Linus, Please pull. Details below. Rob The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git

[GIT PULL] DeviceTree fixes for 4.14

Hi Linus, Please pull. Details below. Rob The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git

Re: [PATCH net-next 2/2] net: dsa: lan9303: Add basic offloading of unicast traffic

Den 23. sep. 2017 16:31, skrev Andrew Lunn: The point is: Once both external ports are in "forwarding", I see no way to prevent traffic flowing directly between the external ports. Generally, there are port vectors. Port X can send frames only to Port Y. If you don't have that, there are

Re: [PATCH net-next 2/2] net: dsa: lan9303: Add basic offloading of unicast traffic

Den 23. sep. 2017 16:31, skrev Andrew Lunn: The point is: Once both external ports are in "forwarding", I see no way to prevent traffic flowing directly between the external ports. Generally, there are port vectors. Port X can send frames only to Port Y. If you don't have that, there are

[PATCH v3 2/4] iio: light: vl6180: Avoid readback of integration time register

Instead of reading the value from the register on each query, store the set value. Signed-off-by: Stefan Brüns --- Changes in v3: - Use IIO_VAL_FRACTIONAL for integration time return value Changes in v2: None drivers/iio/light/vl6180.c | 15 +-- 1

[PATCH v3 2/4] iio: light: vl6180: Avoid readback of integration time register

Instead of reading the value from the register on each query, store the set value. Signed-off-by: Stefan Brüns --- Changes in v3: - Use IIO_VAL_FRACTIONAL for integration time return value Changes in v2: None drivers/iio/light/vl6180.c | 15 +-- 1 file changed, 9 insertions(+),

[PATCH v3 0/4] Currently, the vl6180 driver reports bogus in_illuminance_scale values

when the integration time or hardware gain are changed from its default value, i.e. it always reports a fixed value. To avoid readback of the register values in case integration time, gain or scale is queried, save the register values. Use the saved values to report the correct scale value.

[PATCH v3 0/4] Currently, the vl6180 driver reports bogus in_illuminance_scale values

when the integration time or hardware gain are changed from its default value, i.e. it always reports a fixed value. To avoid readback of the register values in case integration time, gain or scale is queried, save the register values. Use the saved values to report the correct scale value.

[PATCH v3 4/4] iio: light: vl6180: Correct ALS scale for non-default gain/integration time

The reported scale was only correct for the default settings of 100 ms integration time and gain 1. This aligns the reported scale with the behaviour of any other IIO driver and the documented ABI, but may require userspace changes if someone uses non-default settings. Signed-off-by: Stefan

[PATCH v3 4/4] iio: light: vl6180: Correct ALS scale for non-default gain/integration time

The reported scale was only correct for the default settings of 100 ms integration time and gain 1. This aligns the reported scale with the behaviour of any other IIO driver and the documented ABI, but may require userspace changes if someone uses non-default settings. Signed-off-by: Stefan

[PATCH v3 3/4] iio: light: vl6180: Cleanup als_gain lookup, avoid register readback

Instead of manually iterating the array of allowed gain values, use find_closest. Storing the current gain setting avoids accessing the hardware on each query. Signed-off-by: Stefan Brüns --- Changes in v3: None Changes in v2: - Add missing spaces

[PATCH v3 1/4] iio: light: vl6180: Move range check to integration time setter, cleanup

This improves code uniformity (range checks for als_gain are also done in the setter). Also unmangle rounding and calculation of register value. The calculated integration time it_ms is required in the next patch of the series. Signed-off-by: Stefan Brüns ---

[PATCH v3 3/4] iio: light: vl6180: Cleanup als_gain lookup, avoid register readback

Instead of manually iterating the array of allowed gain values, use find_closest. Storing the current gain setting avoids accessing the hardware on each query. Signed-off-by: Stefan Brüns --- Changes in v3: None Changes in v2: - Add missing spaces drivers/iio/light/vl6180.c | 85

[PATCH v3 1/4] iio: light: vl6180: Move range check to integration time setter, cleanup

This improves code uniformity (range checks for als_gain are also done in the setter). Also unmangle rounding and calculation of register value. The calculated integration time it_ms is required in the next patch of the series. Signed-off-by: Stefan Brüns --- Changes in v3: - Drop whitespace

Re: [PATCH] dt-bindings: i2c: Add armada-38x i2c binding

Hi Gregory, I got this information from Armada-38x functional errata document. I can add the "marvell,mv78230-i2c" compatible string to the appropriate device tree files but the i2c-mv64xxx driver enables an additional feature (offload i2c transactions) based on the compatible string

Re: [PATCH] dt-bindings: i2c: Add armada-38x i2c binding

Hi Gregory, I got this information from Armada-38x functional errata document. I can add the "marvell,mv78230-i2c" compatible string to the appropriate device tree files but the i2c-mv64xxx driver enables an additional feature (offload i2c transactions) based on the compatible string

ARM64: kernel panics in DABT in sys_msync path

Hi all, I found that running with qemu-10 with '-smp 4' option kernel v4.13 and v4.14-rc1 panics with LTP test rwtest03: rwtest -N rwtest03 -c -q -i 60s -n 2 -f buffered -s mmread,mmwrite -m random -Dv 10%25000:mm-buff-$$ [ 2068.307587] Unable to handle kernel paging request at virtual address

ARM64: kernel panics in DABT in sys_msync path

Hi all, I found that running with qemu-10 with '-smp 4' option kernel v4.13 and v4.14-rc1 panics with LTP test rwtest03: rwtest -N rwtest03 -c -q -i 60s -n 2 -f buffered -s mmread,mmwrite -m random -Dv 10%25000:mm-buff-$$ [ 2068.307587] Unable to handle kernel paging request at virtual address

[PATCH 3.18 01/42] ipv6: accept 64k - 1 packet length in ip6_find_1stfragopt()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 3de33e1ba0506723ab25734e098cf280ecc34756 ] A packet length of exactly IPV6_MAXPLEN is allowed, we should refuse parsing options only if

[PATCH 3.18 01/42] ipv6: accept 64k - 1 packet length in ip6_find_1stfragopt()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 3de33e1ba0506723ab25734e098cf280ecc34756 ] A packet length of exactly IPV6_MAXPLEN is allowed, we should refuse parsing options only if the size is 64KiB or

[PATCH 3.18 14/42] block: Relax a check in blk_start_queue()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 4ddd56b003f251091a67c15ae3fe4a5c5c5e390a upstream. Calling blk_start_queue() from interrupt context with the queue lock held and without

[PATCH 3.18 14/42] block: Relax a check in blk_start_queue()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 4ddd56b003f251091a67c15ae3fe4a5c5c5e390a upstream. Calling blk_start_queue() from interrupt context with the queue lock held and without disabling IRQs, as the skd

[PATCH 3.18 13/42] powerpc: Fix DAR reporting when alignment handler faults

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit f9effe925039cf54489b5c04e0d40073bb3a123d upstream. Anton noticed that if we fault part way through emulating an unaligned instruction, we don't

[PATCH 3.18 13/42] powerpc: Fix DAR reporting when alignment handler faults

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit f9effe925039cf54489b5c04e0d40073bb3a123d upstream. Anton noticed that if we fault part way through emulating an unaligned instruction, we don't update the DAR to

[PATCH 3.18 15/42] md/bitmap: disable bitmap_resize for file-backed bitmaps.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit e8a27f836f165c26f867ece7f31eb5c811692319 upstream. bitmap_resize() does not work for file-backed bitmaps. The buffer_heads are allocated and initialized when

[PATCH 3.18 15/42] md/bitmap: disable bitmap_resize for file-backed bitmaps.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit e8a27f836f165c26f867ece7f31eb5c811692319 upstream. bitmap_resize() does not work for file-backed bitmaps. The buffer_heads are allocated and initialized when the bitmap is

[PATCH 3.18 18/42] scsi: zfcp: fix queuecommand for scsi_eh commands when DIX enabled

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 71b8e45da51a7b64a23378221c0a5868bd79da4f upstream. Since commit db007fc5e20c ("[SCSI] Command protection operation"), scsi_eh_prep_cmnd() saves

[PATCH 3.18 18/42] scsi: zfcp: fix queuecommand for scsi_eh commands when DIX enabled

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 71b8e45da51a7b64a23378221c0a5868bd79da4f upstream. Since commit db007fc5e20c ("[SCSI] Command protection operation"), scsi_eh_prep_cmnd() saves scmd->prot_op and

[PATCH 3.18 02/42] qlge: avoid memcpy buffer overflow

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit e58f95831e7468d25eb6e41f234842ecfe6f014f ] gcc-8.0.0 (snapshot) points out that we copy a variable-length string into a fixed length field

[PATCH 3.18 20/42] scsi: zfcp: fix missing trace records for early returns in TMF eh handlers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 1a5d999ebfc7bfe28deb48931bb57faa8e4102b6 upstream. For problem determination we need to see that we were in scsi_eh as well as whether and why

[PATCH 3.18 02/42] qlge: avoid memcpy buffer overflow

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit e58f95831e7468d25eb6e41f234842ecfe6f014f ] gcc-8.0.0 (snapshot) points out that we copy a variable-length string into a fixed length field using memcpy() with

[PATCH 3.18 20/42] scsi: zfcp: fix missing trace records for early returns in TMF eh handlers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 1a5d999ebfc7bfe28deb48931bb57faa8e4102b6 upstream. For problem determination we need to see that we were in scsi_eh as well as whether and why we were successful or not.

[PATCH 3.18 23/42] scsi: zfcp: trace high part of "new" 64 bit SCSI LUN

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 5d4a3d0a2ff23799b956e5962b886287614e7fad upstream. Complements debugging aspects of the otherwise functionally complete v3.17 commit

[PATCH 3.18 23/42] scsi: zfcp: trace high part of "new" 64 bit SCSI LUN

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 5d4a3d0a2ff23799b956e5962b886287614e7fad upstream. Complements debugging aspects of the otherwise functionally complete v3.17 commit 9cb78c16f5da ("scsi: use 64-bit

[PATCH 3.18 22/42] scsi: zfcp: trace HBA FSF response by default on dismiss or timedout late response

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit fdb7cee3b9e3c561502e58137a837341f10cbf8b upstream. At the default trace level, we only trace unsuccessful events including FSF responses.

[PATCH 3.18 24/42] scsi: sg: remove save_scat_len

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 136e57bf43dc4babbfb8783abbf707d483cacbe3 upstream. Unused. Signed-off-by: Hannes Reinecke Reviewed-by: Johannes Thumshirn

[PATCH 4.4 10/66] ipv6: fix memory leak with multiple tables during netns destruction

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with

[PATCH 4.4 01/66] ipv6: accept 64k - 1 packet length in ip6_find_1stfragopt()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 3de33e1ba0506723ab25734e098cf280ecc34756 ] A packet length of exactly IPV6_MAXPLEN is allowed, we should refuse parsing options only if

[PATCH 3.18 22/42] scsi: zfcp: trace HBA FSF response by default on dismiss or timedout late response

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit fdb7cee3b9e3c561502e58137a837341f10cbf8b upstream. At the default trace level, we only trace unsuccessful events including FSF responses. zfcp_dbf_hba_fsf_response()

[PATCH 3.18 24/42] scsi: sg: remove save_scat_len

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 136e57bf43dc4babbfb8783abbf707d483cacbe3 upstream. Unused. Signed-off-by: Hannes Reinecke Reviewed-by: Johannes Thumshirn Tested-by: Johannes Thumshirn Reviewed-by:

[PATCH 4.4 10/66] ipv6: fix memory leak with multiple tables during netns destruction

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with fib6_alloc_table, we leak it

[PATCH 4.4 01/66] ipv6: accept 64k - 1 packet length in ip6_find_1stfragopt()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 3de33e1ba0506723ab25734e098cf280ecc34756 ] A packet length of exactly IPV6_MAXPLEN is allowed, we should refuse parsing options only if the size is 64KiB or

[PATCH 3.18 26/42] scsi: sg: off by one in sg_ioctl()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit bd46fc406b30d1db1aff8dabaff8d18bb423fdcf upstream. If "val" is SG_MAX_QUEUE then we are one element beyond the end of the "rinfo" array so the >

[PATCH 3.18 26/42] scsi: sg: off by one in sg_ioctl()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit bd46fc406b30d1db1aff8dabaff8d18bb423fdcf upstream. If "val" is SG_MAX_QUEUE then we are one element beyond the end of the "rinfo" array so the > should be >=. Fixes:

Re: [PATCH 1/2 v2] fdmap(2)

On Sun, Sep 24, 2017 at 1:06 PM, Alexey Dobriyan wrote: > From: Aliaksandr Patseyenak > > Implement system call for bulk retrieveing of opened descriptors > in binary form. > > Some daemons could use it to reliably close file descriptors >

Re: [PATCH 1/2 v2] fdmap(2)

On Sun, Sep 24, 2017 at 1:06 PM, Alexey Dobriyan wrote: > From: Aliaksandr Patseyenak > > Implement system call for bulk retrieveing of opened descriptors > in binary form. > > Some daemons could use it to reliably close file descriptors > before starting. Currently they close everything upto

[PATCH 4.4 14/66] md/raid5: release/flush io in raid5_do_work()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Song Liu commit 9c72a18e46ebe0f09484cce8ebf847abdab58498 upstream. In raid5, there are scenarios where some ios are deferred to a later time, and some IO need a flush to

[PATCH 4.4 12/66] f2fs: check hot_data for roll-forward recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 125c9fb1ccb53eb2ea9380df40f3c743f3fb2fed upstream. We need to check HOT_DATA to truncate any previous data block when doing roll-forward recovery.

[PATCH 4.4 14/66] md/raid5: release/flush io in raid5_do_work()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Song Liu commit 9c72a18e46ebe0f09484cce8ebf847abdab58498 upstream. In raid5, there are scenarios where some ios are deferred to a later time, and some IO need a flush to complete. To make sure

[PATCH 4.4 12/66] f2fs: check hot_data for roll-forward recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 125c9fb1ccb53eb2ea9380df40f3c743f3fb2fed upstream. We need to check HOT_DATA to truncate any previous data block when doing roll-forward recovery. Reviewed-by: Chao Yu

[PATCH 4.4 11/66] ipv6: fix typo in fib6_net_exit()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 32a805baf0fb70b6dbedefcd7249ac7f580f9e3b ] IPv6 FIB should use FIB6_TABLE_HASHSZ, not FIB_TABLE_HASHSZ. Fixes: ba1cc08d9488 ("ipv6: fix

[PATCH 4.4 11/66] ipv6: fix typo in fib6_net_exit()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 32a805baf0fb70b6dbedefcd7249ac7f580f9e3b ] IPv6 FIB should use FIB6_TABLE_HASHSZ, not FIB_TABLE_HASHSZ. Fixes: ba1cc08d9488 ("ipv6: fix memory leak with

[PATCH 4.4 19/66] tty: fix __tty_insert_flip_char regression

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 8a5a90a2a477b86a3dc2eaa5a706db9bfdd647ca upstream. Sergey noticed a small but fatal mistake in __tty_insert_flip_char, leading to an oops in an interrupt

[PATCH 4.4 19/66] tty: fix __tty_insert_flip_char regression

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 8a5a90a2a477b86a3dc2eaa5a706db9bfdd647ca upstream. Sergey noticed a small but fatal mistake in __tty_insert_flip_char, leading to an oops in an interrupt handler when

[PATCH 4.4 17/66] tty: improve tty_insert_flip_char() fast path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 979990c6284814617d8f2179d197f72ff62b5d85 upstream. kernelci.org reports a crazy stack usage for the VT code when CONFIG_KASAN is enabled:

[PATCH 4.4 17/66] tty: improve tty_insert_flip_char() fast path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 979990c6284814617d8f2179d197f72ff62b5d85 upstream. kernelci.org reports a crazy stack usage for the VT code when CONFIG_KASAN is enabled: drivers/tty/vt/keyboard.c: In

[PATCH 4.4 02/66] ipv6: add rcu grace period before freeing fib6_node

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Wang [ Upstream commit c5cff8561d2d0006e972bd114afd51f082fee77c ] We currently keep rt->rt6i_node pointing to the fib6_node for the route. And some functions make use

[PATCH 4.4 16/66] mm: prevent double decrease of nr_reserved_highatomic

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Minchan Kim commit 4855e4a7f29d6d10b0b9c84e189c770c9a94e91e upstream. There is race between page freeing and unreserved highatomic. CPU 0 CPU

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