[PATCH 2/9] ASoC: tlv320aic3x: Fix typo in DT binding documentation

The property used to specify a GPIO intended for reset is "reset-gpio", this binding uses "gpio-reset", as almost all other bindings use the former name this use of the latter is certainly not intended and was a typo. It is not compatible with newer methods used to fetch GPIO pins and to prevent

[PATCH 2/9] ASoC: tlv320aic3x: Fix typo in DT binding documentation

The property used to specify a GPIO intended for reset is "reset-gpio", this binding uses "gpio-reset", as almost all other bindings use the former name this use of the latter is certainly not intended and was a typo. It is not compatible with newer methods used to fetch GPIO pins and to prevent

[PATCH 7/9] ARM: dts: omap3-n900: Fix the audio CODEC's reset pin

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: 14e3e295b2b9 ("ARM: dts: omap3-n900: Add TLV320AIC3X support") Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/omap3-n900.dts | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 7/9] ARM: dts: omap3-n900: Fix the audio CODEC's reset pin

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: 14e3e295b2b9 ("ARM: dts: omap3-n900: Add TLV320AIC3X support") Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/omap3-n900.dts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 1/9] ASoC: tlv320aic31xx: Fix typo in DT binding documentation

The property used to specify a GPIO intended for reset is "reset-gpio", this binding uses "gpio-reset", as almost all other bindings use the former name this use of the latter is certainly not intended and was a typo. It is not compatible with newer methods used to fetch GPIO pins and to prevent

[PATCH 3/9] ASoC: cs42l56: bindings: sound: Fix reset GPIO name in example DT binding

The binding states the reset GPIO property shall be named "cirrus,gpio-nreset" and this is what the driver looks for, but the example uses "gpio-reset". Fix this here. Fixes: 3bb40619aca8 ("ASoC: cs42l56: bindings: sound: Add bindings for CS42L56 CODEC") Signed-off-by: Andrew F. Davis

[PATCH 1/9] ASoC: tlv320aic31xx: Fix typo in DT binding documentation

The property used to specify a GPIO intended for reset is "reset-gpio", this binding uses "gpio-reset", as almost all other bindings use the former name this use of the latter is certainly not intended and was a typo. It is not compatible with newer methods used to fetch GPIO pins and to prevent

[PATCH 3/9] ASoC: cs42l56: bindings: sound: Fix reset GPIO name in example DT binding

The binding states the reset GPIO property shall be named "cirrus,gpio-nreset" and this is what the driver looks for, but the example uses "gpio-reset". Fix this here. Fixes: 3bb40619aca8 ("ASoC: cs42l56: bindings: sound: Add bindings for CS42L56 CODEC") Signed-off-by: Andrew F. Davis ---

[PATCH 9/9] ASoC: tlv320aic3x: Fix the reset GPIO OF name

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: c24fdc886fde ("ASoC: tlv320aic3x: Add device tree bindings") Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic3x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 9/9] ASoC: tlv320aic3x: Fix the reset GPIO OF name

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: c24fdc886fde ("ASoC: tlv320aic3x: Add device tree bindings") Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic3x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 5/9] ARM: dts: imx6: RDU2: Fix the audio CODEC's reset pin

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: d763762e3b58 ("ARM: dts: imx6: add ZII RDU2 boards") Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 5/9] ARM: dts: imx6: RDU2: Fix the audio CODEC's reset pin

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: d763762e3b58 ("ARM: dts: imx6: add ZII RDU2 boards") Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 6/9] ARM: dts: imx: Fix the audio CODEC's reset pin

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: 50bffb78e2ee ("ARM: dts: imx: add Gateworks Ventana GW5903 support") Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/imx6qdl-gw5903.dtsi | 2 +- 1 file changed, 1 insertion(+),

[PATCH 6/9] ARM: dts: imx: Fix the audio CODEC's reset pin

The correct DT property for specifying a GPIO used for reset is "reset-gpio", fix this here. Fixes: 50bffb78e2ee ("ARM: dts: imx: add Gateworks Ventana GW5903 support") Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/imx6qdl-gw5903.dtsi | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 0/9] Remove use of "gpio-reset" from DT

Hello all, I was working on fixing up the tlv320aic31xx driver when I noticed its gpio reset was not working, it was due to this driver looking for "gpio-reset" instead of the usual "reset-gpio". A quick check shows this mistake is rare and only copied by one other audio CODECs: $ git grep

[PATCH AUTOSEL for-4.4 30/39] ixgbe: handle close/suspend race with netif_device_detach/present

From: Emil Tantilov [ Upstream commit f7f37e7ff2b9b7eff7fbd035569cab35896869a3 ] When an interface is part of a namespace it is possible that ixgbe_close() may be called while __ixgbe_shutdown() is running which ends up in a double free WARN and/or a BUG in

[PATCH 0/9] Remove use of "gpio-reset" from DT

Hello all, I was working on fixing up the tlv320aic31xx driver when I noticed its gpio reset was not working, it was due to this driver looking for "gpio-reset" instead of the usual "reset-gpio". A quick check shows this mistake is rare and only copied by one other audio CODECs: $ git grep

[PATCH AUTOSEL for-4.4 30/39] ixgbe: handle close/suspend race with netif_device_detach/present

From: Emil Tantilov [ Upstream commit f7f37e7ff2b9b7eff7fbd035569cab35896869a3 ] When an interface is part of a namespace it is possible that ixgbe_close() may be called while __ixgbe_shutdown() is running which ends up in a double free WARN and/or a BUG in free_msi_irqs(). To handle this

[PATCH AUTOSEL for-4.4 29/39] ixgbe: fix AER error handling

From: Emil Tantilov [ Upstream commit 126db13fa0e6d05c9f94e0125f61e773bd5ab079 ] Make sure that we free the IRQs in ixgbe_io_error_detected() when responding to an PCIe AER error and also restore them when the interface recovers from it. Previously it was possible to

[PATCH AUTOSEL for-4.4 29/39] ixgbe: fix AER error handling

From: Emil Tantilov [ Upstream commit 126db13fa0e6d05c9f94e0125f61e773bd5ab079 ] Make sure that we free the IRQs in ixgbe_io_error_detected() when responding to an PCIe AER error and also restore them when the interface recovers from it. Previously it was possible to trigger BUG_ON() check in

[PATCH AUTOSEL for-4.4 24/39] backlight: lcd: Fix race condition during register

From: Uwe Kleine-König [ Upstream commit cc21942bce652d1a92dae85b785378256e1df1f7 ] Once device_register is called for a device its attributes might be accessed. As the callbacks of a lcd device's attributes make use of the lcd_ops, the respective member must be

[PATCH AUTOSEL for-4.4 24/39] backlight: lcd: Fix race condition during register

From: Uwe Kleine-König [ Upstream commit cc21942bce652d1a92dae85b785378256e1df1f7 ] Once device_register is called for a device its attributes might be accessed. As the callbacks of a lcd device's attributes make use of the lcd_ops, the respective member must be setup before calling

[PATCH AUTOSEL for-4.4 21/39] scsi: lpfc: Clear the VendorVersion in the PLOGI/PLOGI ACC payload

From: James Smart [ Upstream commit e0165f20447c8ca1d367725ee94d8ec9f38ca275 ] Clear the VendorVersion in the PLOGI/PLOGI ACC payload Vendor version info may have been set on fabric login. Before sending PLOGI payloads, ensure that it's cleared. Signed-off-by: Dick

[PATCH AUTOSEL for-4.4 21/39] scsi: lpfc: Clear the VendorVersion in the PLOGI/PLOGI ACC payload

From: James Smart [ Upstream commit e0165f20447c8ca1d367725ee94d8ec9f38ca275 ] Clear the VendorVersion in the PLOGI/PLOGI ACC payload Vendor version info may have been set on fabric login. Before sending PLOGI payloads, ensure that it's cleared. Signed-off-by: Dick Kennedy Signed-off-by:

[PATCH AUTOSEL for-4.4 05/39] ARM: OMAP2+: Fix init for multiple quirks for the same SoC

From: Tony Lindgren [ Upstream commit 6e613ebf4405fc09e2a8c16ed193b47f80a3cbed ] It's possible that there are multiple quirks that need to be initialized for the same SoC. Fix the issue by not returning on the first match. Signed-off-by: Tony Lindgren

[PATCH AUTOSEL for-4.4 05/39] ARM: OMAP2+: Fix init for multiple quirks for the same SoC

From: Tony Lindgren [ Upstream commit 6e613ebf4405fc09e2a8c16ed193b47f80a3cbed ] It's possible that there are multiple quirks that need to be initialized for the same SoC. Fix the issue by not returning on the first match. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin ---

[PATCH AUTOSEL for-4.4 04/39] ARM: dts: Fix am335x and dm814x scm syscon to probe children

From: Tony Lindgren [ Upstream commit 1aa09df0854efe16b7a80358a18f0a0bebafd246 ] Without these changes children of the scn syscon won't probe. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin ---

[PATCH AUTOSEL for-4.4 07/39] ata: ATA_BMDMA should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 7bc7ab1e63dfe004931502f90ce7020e375623da ] If NO_DMA=y: ERROR: "dmam_alloc_coherent" [drivers/ata/libata.ko] undefined! Add a dependency on HAS_DMA to fix this. Signed-off-by: Geert Uytterhoeven

[PATCH AUTOSEL for-4.4 04/39] ARM: dts: Fix am335x and dm814x scm syscon to probe children

From: Tony Lindgren [ Upstream commit 1aa09df0854efe16b7a80358a18f0a0bebafd246 ] Without these changes children of the scn syscon won't probe. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin --- arch/arm/boot/dts/am33xx.dtsi | 3 ++- arch/arm/boot/dts/dm814x.dtsi | 3 ++- 2 files

[PATCH AUTOSEL for-4.4 07/39] ata: ATA_BMDMA should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 7bc7ab1e63dfe004931502f90ce7020e375623da ] If NO_DMA=y: ERROR: "dmam_alloc_coherent" [drivers/ata/libata.ko] undefined! Add a dependency on HAS_DMA to fix this. Signed-off-by: Geert Uytterhoeven Signed-off-by: Tejun Heo Signed-off-by: Sasha

[PATCH AUTOSEL for-4.4 22/39] ALSA: vx: Don't try to update capture stream before running

From: Takashi Iwai [ Upstream commit ed3c177d960bb5881b945ca6f784868126bb90db ] The update of stream costs significantly, and we should avoid it unless the stream really has started. Check pipe->running flag instead of pipe->prepared. Signed-off-by: Takashi Iwai

[PATCH AUTOSEL for-4.4 22/39] ALSA: vx: Don't try to update capture stream before running

From: Takashi Iwai [ Upstream commit ed3c177d960bb5881b945ca6f784868126bb90db ] The update of stream costs significantly, and we should avoid it unless the stream really has started. Check pipe->running flag instead of pipe->prepared. Signed-off-by: Takashi Iwai Signed-off-by: Sasha Levin

[PATCH AUTOSEL for-3.18 13/27] scsi: lpfc: FCoE VPort enable-disable does not bring up the VPort

From: James Smart [ Upstream commit 104450eb08ca662e6b1d02da11aca9598e978f3e ] FCoE VPort enable-disable does not bring up the VPort. VPI structure needed to be initialized before being re-registered. Signed-off-by: Dick Kennedy

[PATCH AUTOSEL for-3.18 13/27] scsi: lpfc: FCoE VPort enable-disable does not bring up the VPort

From: James Smart [ Upstream commit 104450eb08ca662e6b1d02da11aca9598e978f3e ] FCoE VPort enable-disable does not bring up the VPort. VPI structure needed to be initialized before being re-registered. Signed-off-by: Dick Kennedy Signed-off-by: James Smart Reviewed-by: Hannes Reinecke

Re: [PATCH] x86/mm: Unbreak modules that rely on external PAGE_KERNEL availability

On Wed, Nov 8, 2017 at 1:15 PM, Borislav Petkov wrote: > > Right, AFAIRC, the main reason for this being an export was because if > we hid it in a function, you'd have all those function calls as part of > the _PAGE_* macros and that's just crap. Yes, that would be worse. I was

Re: [PATCH] x86/mm: Unbreak modules that rely on external PAGE_KERNEL availability

On Wed, Nov 8, 2017 at 1:15 PM, Borislav Petkov wrote: > > Right, AFAIRC, the main reason for this being an export was because if > we hid it in a function, you'd have all those function calls as part of > the _PAGE_* macros and that's just crap. Yes, that would be worse. I was thinking that

[PATCH AUTOSEL for-3.18 04/27] ata: ATA_BMDMA should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 7bc7ab1e63dfe004931502f90ce7020e375623da ] If NO_DMA=y: ERROR: "dmam_alloc_coherent" [drivers/ata/libata.ko] undefined! Add a dependency on HAS_DMA to fix this. Signed-off-by: Geert Uytterhoeven

[PATCH AUTOSEL for-3.18 04/27] ata: ATA_BMDMA should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 7bc7ab1e63dfe004931502f90ce7020e375623da ] If NO_DMA=y: ERROR: "dmam_alloc_coherent" [drivers/ata/libata.ko] undefined! Add a dependency on HAS_DMA to fix this. Signed-off-by: Geert Uytterhoeven Signed-off-by: Tejun Heo Signed-off-by: Sasha

[PATCH AUTOSEL for-3.18 05/27] ata: SATA_HIGHBANK should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 2a736e0585e585c2566b5119af8381910a170e44 ] If NO_DMA=y: ERROR: "bad_dma_ops" [drivers/ata/sata_highbank.ko] undefined! Add a dependency on HAS_DMA to fix this. Signed-off-by: Geert Uytterhoeven

[PATCH AUTOSEL for-3.18 05/27] ata: SATA_HIGHBANK should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 2a736e0585e585c2566b5119af8381910a170e44 ] If NO_DMA=y: ERROR: "bad_dma_ops" [drivers/ata/sata_highbank.ko] undefined! Add a dependency on HAS_DMA to fix this. Signed-off-by: Geert Uytterhoeven Signed-off-by: Tejun Heo Signed-off-by: Sasha

[PATCH AUTOSEL for-3.18 01/27] extcon: palmas: Check the parent instance to prevent the NULL

From: Roger Quadros [ Upstream commit 9fe172b9be532acc23e35ba693700383ab775e66 ] extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later

[PATCH AUTOSEL for-3.18 01/27] extcon: palmas: Check the parent instance to prevent the NULL

From: Roger Quadros [ Upstream commit 9fe172b9be532acc23e35ba693700383ab775e66 ] extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later in the probe()

[PATCH AUTOSEL for-3.18 14/27] scsi: lpfc: Correct host name in symbolic_name field

From: James Smart [ Upstream commit 6c9231f604c2575be24c96d38deb70f145172f92 ] Correct host name in symbolic_name field of nameserver registrations Signed-off-by: Dick Kennedy Signed-off-by: James Smart

[PATCH AUTOSEL for-3.18 14/27] scsi: lpfc: Correct host name in symbolic_name field

From: James Smart [ Upstream commit 6c9231f604c2575be24c96d38deb70f145172f92 ] Correct host name in symbolic_name field of nameserver registrations Signed-off-by: Dick Kennedy Signed-off-by: James Smart Reviewed-by: Hannes Reinecke Signed-off-by: Martin K. Petersen Signed-off-by: Sasha

[PATCH AUTOSEL for-4.4 09/39] ata: SATA_MV should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 62989cebd367a1aae1e009e1a5b1ec046a4c8fdc ] If NO_DMA=y: ERROR: "dma_pool_alloc" [drivers/ata/sata_mv.ko] undefined! ERROR: "dmam_pool_create" [drivers/ata/sata_mv.ko] undefined! ERROR: "dma_pool_free"

[PATCH AUTOSEL for-3.18 17/27] ALSA: vx: Fix possible transfer overflow

From: Takashi Iwai [ Upstream commit 874e1f6fad9a5184b67f4cee37c1335cd2cc5677 ] The pseudo DMA transfer codes in VX222 and VX-pocket driver have a slight bug where they check the buffer boundary wrongly, and may overflow. Also, the zero sample count might be handled badly for

[PATCH AUTOSEL for-4.4 09/39] ata: SATA_MV should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 62989cebd367a1aae1e009e1a5b1ec046a4c8fdc ] If NO_DMA=y: ERROR: "dma_pool_alloc" [drivers/ata/sata_mv.ko] undefined! ERROR: "dmam_pool_create" [drivers/ata/sata_mv.ko] undefined! ERROR: "dma_pool_free" [drivers/ata/sata_mv.ko] undefined!

[PATCH AUTOSEL for-3.18 17/27] ALSA: vx: Fix possible transfer overflow

From: Takashi Iwai [ Upstream commit 874e1f6fad9a5184b67f4cee37c1335cd2cc5677 ] The pseudo DMA transfer codes in VX222 and VX-pocket driver have a slight bug where they check the buffer boundary wrongly, and may overflow. Also, the zero sample count might be handled badly for the playback

[PATCH AUTOSEL for-4.4 12/39] igb: close/suspend race in netif_device_detach

From: Todd Fujinaka [ Upstream commit 9474933caf21a4cb5147223dca1551f527aaac36 ] Similar to ixgbe, when an interface is part of a namespace it is possible that igb_close() may be called while __igb_shutdown() is running which ends up in a double free WARN and/or a BUG

[PATCH AUTOSEL for-4.4 12/39] igb: close/suspend race in netif_device_detach

From: Todd Fujinaka [ Upstream commit 9474933caf21a4cb5147223dca1551f527aaac36 ] Similar to ixgbe, when an interface is part of a namespace it is possible that igb_close() may be called while __igb_shutdown() is running which ends up in a double free WARN and/or a BUG in free_msi_irqs().

[PATCH AUTOSEL for-4.4 13/39] igb: Fix hw_dbg logging in igb_update_flash_i210

From: Hannu Lounento [ Upstream commit 76ed5a8f47476e4984cc8c0c1bc4cee62650f7fd ] Fix an if statement with hw_dbg lines where the logic was inverted with regards to the corresponding return value used in the if statement. Signed-off-by: Hannu Lounento

[PATCH AUTOSEL for-4.4 13/39] igb: Fix hw_dbg logging in igb_update_flash_i210

From: Hannu Lounento [ Upstream commit 76ed5a8f47476e4984cc8c0c1bc4cee62650f7fd ] Fix an if statement with hw_dbg lines where the logic was inverted with regards to the corresponding return value used in the if statement. Signed-off-by: Hannu Lounento Signed-off-by: Peter Senna Tschudin

Re: [PATCH] xen/privcmd: remove unused variable pageidx

On 11/08/2017 08:30 AM, Juergen Gross wrote: > On 08/11/17 14:00, Colin King wrote: >> From: Colin Ian King >> >> Variable pageidx is assigned a value but it is never read, hence it >> is redundant and can be removed. Cleans up clang warning: >> >>

Re: [PATCH] xen/privcmd: remove unused variable pageidx

On 11/08/2017 08:30 AM, Juergen Gross wrote: > On 08/11/17 14:00, Colin King wrote: >> From: Colin Ian King >> >> Variable pageidx is assigned a value but it is never read, hence it >> is redundant and can be removed. Cleans up clang warning: >> >> drivers/xen/privcmd.c:199:2: warning: Value

[PATCH AUTOSEL for-4.4 01/39] extcon: palmas: Check the parent instance to prevent the NULL

From: Roger Quadros [ Upstream commit 9fe172b9be532acc23e35ba693700383ab775e66 ] extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later

[PATCH AUTOSEL for-4.4 01/39] extcon: palmas: Check the parent instance to prevent the NULL

From: Roger Quadros [ Upstream commit 9fe172b9be532acc23e35ba693700383ab775e66 ] extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later in the probe()

Re: [PATCH v2 0/5] xen: grant table interface v2 support

On 11/06/2017 03:46 PM, Boris Ostrovsky wrote: > On 11/02/2017 05:19 AM, Juergen Gross wrote: >> In order to support Linux to run as a pv guest on machines with huge >> memory (>16TB) or as a hvm guest with more than 16TB of memory the >> kernel has to support grant table interface v2, as v1 is

Re: [PATCH v2 0/5] xen: grant table interface v2 support

On 11/06/2017 03:46 PM, Boris Ostrovsky wrote: > On 11/02/2017 05:19 AM, Juergen Gross wrote: >> In order to support Linux to run as a pv guest on machines with huge >> memory (>16TB) or as a hvm guest with more than 16TB of memory the >> kernel has to support grant table interface v2, as v1 is

Re: [PATCH v4] xen: support priv-mapping in an HVM tools domain

On 11/03/2017 04:51 PM, Boris Ostrovsky wrote: > On 11/03/2017 01:04 PM, Paul Durrant wrote: >> If the domain has XENFEAT_auto_translated_physmap then use of the PV- >> specific HYPERVISOR_mmu_update hypercall is clearly incorrect. >> >> This patch adds checks in xen_remap_domain_gfn_array() and

Re: [PATCH v4] xen: support priv-mapping in an HVM tools domain

On 11/03/2017 04:51 PM, Boris Ostrovsky wrote: > On 11/03/2017 01:04 PM, Paul Durrant wrote: >> If the domain has XENFEAT_auto_translated_physmap then use of the PV- >> specific HYPERVISOR_mmu_update hypercall is clearly incorrect. >> >> This patch adds checks in xen_remap_domain_gfn_array() and

[PATCH AUTOSEL for-4.4 32/39] ixgbe: add mask for 64 RSS queues

From: Emil Tantilov [ Upstream commit 2bf1a87b903bd81b1448a1cef73de59fb6c4d340 ] The indirection table was reported incorrectly for X550 and newer where we can support up to 64 RSS queues. Reported-by Krishneil Singh Signed-off-by: Emil

[PATCH AUTOSEL for-4.4 36/39] MIPS: init: Ensure bootmem does not corrupt reserved memory

From: Marcin Nowakowski [ Upstream commit d9b5b658210f28ed9f70c757d553e679d76e2986 ] Current init code initialises bootmem allocator with all of the low memory that it assumes is available, but does not check for reserved memory block, which can lead to corruption

[PATCH AUTOSEL for-4.4 35/39] MIPS: End asm function prologue macros with .insn

From: Paul Burton [ Upstream commit 08889582b8aa0bbc01a1e5a0033b9f98d2e11caa ] When building a kernel targeting a microMIPS ISA, recent GNU linkers will fail the link if they cannot determine that the target of a branch or jump is microMIPS code, with errors such as the

[PATCH AUTOSEL for-4.4 32/39] ixgbe: add mask for 64 RSS queues

From: Emil Tantilov [ Upstream commit 2bf1a87b903bd81b1448a1cef73de59fb6c4d340 ] The indirection table was reported incorrectly for X550 and newer where we can support up to 64 RSS queues. Reported-by Krishneil Singh Signed-off-by: Emil Tantilov Tested-by: Andrew Bowers Signed-off-by: Jeff

[PATCH AUTOSEL for-4.4 36/39] MIPS: init: Ensure bootmem does not corrupt reserved memory

From: Marcin Nowakowski [ Upstream commit d9b5b658210f28ed9f70c757d553e679d76e2986 ] Current init code initialises bootmem allocator with all of the low memory that it assumes is available, but does not check for reserved memory block, which can lead to corruption of data that may be stored

[PATCH AUTOSEL for-4.4 35/39] MIPS: End asm function prologue macros with .insn

From: Paul Burton [ Upstream commit 08889582b8aa0bbc01a1e5a0033b9f98d2e11caa ] When building a kernel targeting a microMIPS ISA, recent GNU linkers will fail the link if they cannot determine that the target of a branch or jump is microMIPS code, with errors such as the following:

Re: [PATCH] xen/pvcalls-front: mark expected switch fall-through

On 11/03/2017 04:04 AM, Juergen Gross wrote: > On 02/11/17 19:51, Gustavo A. R. Silva wrote: >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Notice that in this particular case I placed the "fall through" comment >> on its

Re: [PATCH] xen/pvcalls-front: mark expected switch fall-through

On 11/03/2017 04:04 AM, Juergen Gross wrote: > On 02/11/17 19:51, Gustavo A. R. Silva wrote: >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Notice that in this particular case I placed the "fall through" comment >> on its

Re: [PATCH] xen/pvcalls: remove redundant check for irq >= 0

On 11/03/2017 06:01 AM, Juergen Gross wrote: > On 03/11/17 10:20, Colin King wrote: >> From: Colin Ian King >> >> This is a moot point, but irq is always less than zero at the label >> out_error, so the check for irq >= 0 is redundant and can be removed. >> >> Detected

Re: [PATCH] xen/pvcalls: remove redundant check for irq >= 0

On 11/03/2017 06:01 AM, Juergen Gross wrote: > On 03/11/17 10:20, Colin King wrote: >> From: Colin Ian King >> >> This is a moot point, but irq is always less than zero at the label >> out_error, so the check for irq >= 0 is redundant and can be removed. >> >> Detected by CoverityScan,

[PATCH AUTOSEL for-4.4 33/39] ixgbe: do not disable FEC from the driver

From: Emil Tantilov [ Upstream commit 1fe954b2097bb907b4578e6a74e4c1d23785a601 ] FEC is configured by the NVM and the driver should not be overriding it. Signed-off-by: Emil Tantilov Tested-by: Krishneil Singh

[PATCH AUTOSEL for-4.4 33/39] ixgbe: do not disable FEC from the driver

From: Emil Tantilov [ Upstream commit 1fe954b2097bb907b4578e6a74e4c1d23785a601 ] FEC is configured by the NVM and the driver should not be overriding it. Signed-off-by: Emil Tantilov Tested-by: Krishneil Singh Signed-off-by: Jeff Kirsher Signed-off-by: Sasha Levin ---

Re: [PATCH] xen/pvcalls: fix unsigned less than zero error check

On 11/03/2017 05:01 AM, Juergen Gross wrote: > On 03/11/17 09:42, Colin King wrote: >> From: Colin Ian King >> >> The check on bedata->ref is never true because ref is an unsigned >> integer. Fix this by assigning signed int ret to the return of the >> call to

Re: [PATCH] xen/pvcalls: fix unsigned less than zero error check

On 11/03/2017 05:01 AM, Juergen Gross wrote: > On 03/11/17 09:42, Colin King wrote: >> From: Colin Ian King >> >> The check on bedata->ref is never true because ref is an unsigned >> integer. Fix this by assigning signed int ret to the return of the >> call to gnttab_claim_grant_reference so the

Re: [PATCH] xen: xenbus_probe_frontend: mark expected switch fall-throughs

On 11/03/2017 04:03 AM, Juergen Gross wrote: > On 02/11/17 19:41, Gustavo A. R. Silva wrote: >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Addresses-Coverity-ID: 146562 >> Addresses-Coverity-ID: 146563 >> Signed-off-by:

[PATCH AUTOSEL for-3.18 23/27] MIPS: End asm function prologue macros with .insn

From: Paul Burton [ Upstream commit 08889582b8aa0bbc01a1e5a0033b9f98d2e11caa ] When building a kernel targeting a microMIPS ISA, recent GNU linkers will fail the link if they cannot determine that the target of a branch or jump is microMIPS code, with errors such as the

Re: [PATCH] xen: xenbus_probe_frontend: mark expected switch fall-throughs

On 11/03/2017 04:03 AM, Juergen Gross wrote: > On 02/11/17 19:41, Gustavo A. R. Silva wrote: >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Addresses-Coverity-ID: 146562 >> Addresses-Coverity-ID: 146563 >> Signed-off-by:

[PATCH AUTOSEL for-3.18 23/27] MIPS: End asm function prologue macros with .insn

From: Paul Burton [ Upstream commit 08889582b8aa0bbc01a1e5a0033b9f98d2e11caa ] When building a kernel targeting a microMIPS ISA, recent GNU linkers will fail the link if they cannot determine that the target of a branch or jump is microMIPS code, with errors such as the following:

[PATCH AUTOSEL for-4.4 19/39] scsi: lpfc: Correct host name in symbolic_name field

From: James Smart [ Upstream commit 6c9231f604c2575be24c96d38deb70f145172f92 ] Correct host name in symbolic_name field of nameserver registrations Signed-off-by: Dick Kennedy Signed-off-by: James Smart

[PATCH AUTOSEL for-4.4 19/39] scsi: lpfc: Correct host name in symbolic_name field

From: James Smart [ Upstream commit 6c9231f604c2575be24c96d38deb70f145172f92 ] Correct host name in symbolic_name field of nameserver registrations Signed-off-by: Dick Kennedy Signed-off-by: James Smart Reviewed-by: Hannes Reinecke Signed-off-by: Martin K. Petersen Signed-off-by: Sasha

[PATCH AUTOSEL for-4.4 38/39] MIPS: Netlogic: Exclude netlogic,xlp-pic code from XLR builds

From: Paul Burton [ Upstream commit 9799270affc53414da96e77e454a5616b39cdab0 ] Code in arch/mips/netlogic/common/irq.c which handles the XLP PIC fails to build in XLR configurations due to cpu_is_xlp9xx not being defined, leading to the following build failure:

[PATCH AUTOSEL for-4.4 38/39] MIPS: Netlogic: Exclude netlogic,xlp-pic code from XLR builds

From: Paul Burton [ Upstream commit 9799270affc53414da96e77e454a5616b39cdab0 ] Code in arch/mips/netlogic/common/irq.c which handles the XLP PIC fails to build in XLR configurations due to cpu_is_xlp9xx not being defined, leading to the following build failure:

[PATCH AUTOSEL for-3.18 06/27] ata: SATA_MV should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 62989cebd367a1aae1e009e1a5b1ec046a4c8fdc ] If NO_DMA=y: ERROR: "dma_pool_alloc" [drivers/ata/sata_mv.ko] undefined! ERROR: "dmam_pool_create" [drivers/ata/sata_mv.ko] undefined! ERROR: "dma_pool_free"

[PATCH AUTOSEL for-3.18 06/27] ata: SATA_MV should depend on HAS_DMA

From: Geert Uytterhoeven [ Upstream commit 62989cebd367a1aae1e009e1a5b1ec046a4c8fdc ] If NO_DMA=y: ERROR: "dma_pool_alloc" [drivers/ata/sata_mv.ko] undefined! ERROR: "dmam_pool_create" [drivers/ata/sata_mv.ko] undefined! ERROR: "dma_pool_free" [drivers/ata/sata_mv.ko] undefined!

[PATCH AUTOSEL for-3.18 10/27] igb: Fix hw_dbg logging in igb_update_flash_i210

From: Hannu Lounento [ Upstream commit 76ed5a8f47476e4984cc8c0c1bc4cee62650f7fd ] Fix an if statement with hw_dbg lines where the logic was inverted with regards to the corresponding return value used in the if statement. Signed-off-by: Hannu Lounento

[PATCH AUTOSEL for-3.18 10/27] igb: Fix hw_dbg logging in igb_update_flash_i210

From: Hannu Lounento [ Upstream commit 76ed5a8f47476e4984cc8c0c1bc4cee62650f7fd ] Fix an if statement with hw_dbg lines where the logic was inverted with regards to the corresponding return value used in the if statement. Signed-off-by: Hannu Lounento Signed-off-by: Peter Senna Tschudin

[PATCH AUTOSEL for-4.9 01/53] extcon: Remove potential problem when calling extcon_register_notifier()

From: Chanwoo Choi [ Upstream commit 01b4c9a1ae07a25d208cad0da7dd288007a22984 ] This patch removes the potential problem of extcon_register_notifier() when edev parameter is NULL. When edev is NULL, this function returns the first extcon device which includes the

[PATCH AUTOSEL for-4.9 01/53] extcon: Remove potential problem when calling extcon_register_notifier()

From: Chanwoo Choi [ Upstream commit 01b4c9a1ae07a25d208cad0da7dd288007a22984 ] This patch removes the potential problem of extcon_register_notifier() when edev parameter is NULL. When edev is NULL, this function returns the first extcon device which includes the sepecific external connector of

Re: [PATCH v6 1/1] xen/time: do not decrease steal time after live migration on xen

On 10/31/2017 09:46 PM, Dongli Zhang wrote: > After guest live migration on xen, steal time in /proc/stat > (cpustat[CPUTIME_STEAL]) might decrease because steal returned by > xen_steal_lock() might be less than this_rq()->prev_steal_time which is > derived from previous return value of

Re: [PATCH v6 1/1] xen/time: do not decrease steal time after live migration on xen

On 10/31/2017 09:46 PM, Dongli Zhang wrote: > After guest live migration on xen, steal time in /proc/stat > (cpustat[CPUTIME_STEAL]) might decrease because steal returned by > xen_steal_lock() might be less than this_rq()->prev_steal_time which is > derived from previous return value of

Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl

On Wed, Nov 08, 2017 at 11:10:56PM +1100, Michael Ellerman wrote: > "Tobin C. Harding" writes: > > Currently we are leaking addresses from the kernel to user space. This > > script is an attempt to find some of those leakages. Script parses > > `dmesg` output and /proc and /sys

Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl

On Wed, Nov 08, 2017 at 11:10:56PM +1100, Michael Ellerman wrote: > "Tobin C. Harding" writes: > > Currently we are leaking addresses from the kernel to user space. This > > script is an attempt to find some of those leakages. Script parses > > `dmesg` output and /proc and /sys files for hex

[PATCH AUTOSEL for-4.9 05/53] ARM: dts: Fix compatible for ti81xx uarts for 8250

From: Tony Lindgren [ Upstream commit f62280efe8934a1275fd148ef302d1afec8cd3df ] When using 8250_omap driver, we need to specify the right compatible value for the UART to work on dm814x and dm816x. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin

[PATCH AUTOSEL for-4.9 05/53] ARM: dts: Fix compatible for ti81xx uarts for 8250

From: Tony Lindgren [ Upstream commit f62280efe8934a1275fd148ef302d1afec8cd3df ] When using 8250_omap driver, we need to specify the right compatible value for the UART to work on dm814x and dm816x. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin --- arch/arm/boot/dts/dm814x.dtsi |

[PATCH AUTOSEL for-4.9 03/53] fm10k: request reset when mbx->state changes

From: Ngai-Mint Kwan [ Upstream commit 2f3fc1e6200309ccf87f61dea56e57e563c4f800 ] Multiple IES API resets can cause a race condition where the mailbox interrupt request bits can be cleared before being handled. This can leave certain mailbox messages from the PF to be

[PATCH AUTOSEL for-4.9 03/53] fm10k: request reset when mbx->state changes

From: Ngai-Mint Kwan [ Upstream commit 2f3fc1e6200309ccf87f61dea56e57e563c4f800 ] Multiple IES API resets can cause a race condition where the mailbox interrupt request bits can be cleared before being handled. This can leave certain mailbox messages from the PF to be untreated and the PF will

Re: [PATCH] x86/mm: Unbreak modules that rely on external PAGE_KERNEL availability

On Wed, Nov 08, 2017 at 01:09:29PM -0800, Linus Torvalds wrote: > Generally we should export _functionality_, not data. Right, AFAIRC, the main reason for this being an export was because if we hid it in a function, you'd have all those function calls as part of the _PAGE_* macros and that's just

Re: [PATCH] x86/mm: Unbreak modules that rely on external PAGE_KERNEL availability

On Wed, Nov 08, 2017 at 01:09:29PM -0800, Linus Torvalds wrote: > Generally we should export _functionality_, not data. Right, AFAIRC, the main reason for this being an export was because if we hid it in a function, you'd have all those function calls as part of the _PAGE_* macros and that's just

[PATCH AUTOSEL for-4.9 02/53] extcon: palmas: Check the parent instance to prevent the NULL

From: Roger Quadros [ Upstream commit 9fe172b9be532acc23e35ba693700383ab775e66 ] extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later

[PATCH AUTOSEL for-4.9 02/53] extcon: palmas: Check the parent instance to prevent the NULL

From: Roger Quadros [ Upstream commit 9fe172b9be532acc23e35ba693700383ab775e66 ] extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later in the probe()

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