Re: [PATCH 4.4 026/114] btrfs: cleaner_kthread() doesnt need explicit freeze

On Thu, Nov 08, 2018 at 01:50:41PM -0800, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > [ Upstream commit 838fe1887765f4cc679febea60d87d2a06bd300e ] Please check the discussion under

[PATCH net-next v2 2/2] net: phy: remove flag PHY_HAS_INTERRUPT from driver configs

Now that flag PHY_HAS_INTERRUPT has been replaced with a check for callbacks config_intr and ack_interrupt, we can remove setting this flag from all driver configs. Last but not least remove flag PHY_HAS_INTERRUPT completely. Signed-off-by: Heiner Kallweit --- v2: - remove flag from all driver

Re: [PATCH v5 09/17] tpm: move tpm_validate_commmand() to tpm2-space.c

On Thu, Nov 08, 2018 at 05:03:29PM +, Winkler, Tomas wrote: > You initialized cc under if only > > + > > + i = tpm2_find_cc(chip, cc); > > + if (i < 0) { > > + dev_dbg(>dev, "0x%04X is an invalid > > command\n", > > + cc); > > +

Re: [PATCH v5 09/17] tpm: move tpm_validate_commmand() to tpm2-space.c

On Thu, Nov 08, 2018 at 05:03:29PM +, Winkler, Tomas wrote: > You initialized cc under if only > > + > > + i = tpm2_find_cc(chip, cc); > > + if (i < 0) { > > + dev_dbg(>dev, "0x%04X is an invalid > > command\n", > > + cc); > > +

Re: [PATCH v5 16/17] tpm: take TPM chip power gating out of tpm_transmit()

On Thu, Nov 08, 2018 at 06:38:59PM +, Winkler, Tomas wrote: > > Call tpm_chip_start() and tpm_chip_stop() in > > > > * tpm_try_get_ops() and tpm_put_ops() > > * tpm_chip_register() > > * tpm2_del_space() > > > > And remove these calls from tpm_transmit(). The core reason for this change > >

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 02:42:55PM -0800, Greg Kroah-Hartman wrote: > On Thu, Nov 08, 2018 at 03:32:58PM -0700, Keith Busch wrote: > > On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > > > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > > > I'm having second

Re: [PATCH v5 16/17] tpm: take TPM chip power gating out of tpm_transmit()

On Thu, Nov 08, 2018 at 06:38:59PM +, Winkler, Tomas wrote: > > Call tpm_chip_start() and tpm_chip_stop() in > > > > * tpm_try_get_ops() and tpm_put_ops() > > * tpm_chip_register() > > * tpm2_del_space() > > > > And remove these calls from tpm_transmit(). The core reason for this change > >

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 02:42:55PM -0800, Greg Kroah-Hartman wrote: > On Thu, Nov 08, 2018 at 03:32:58PM -0700, Keith Busch wrote: > > On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > > > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > > > I'm having second

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, Nov 8, 2018 at 12:14 PM Theodore Y. Ts'o wrote: > > On Thu, Nov 08, 2018 at 09:19:33AM -0800, Dan Williams wrote: > > > > I know at least StGit mail does not grok that "#"notation. I've > > stopped using it in favor of a "Fixes:" tag. I would think "Fixes:" is > > preferred over "# " if

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, Nov 8, 2018 at 12:14 PM Theodore Y. Ts'o wrote: > > On Thu, Nov 08, 2018 at 09:19:33AM -0800, Dan Williams wrote: > > > > I know at least StGit mail does not grok that "#"notation. I've > > stopped using it in favor of a "Fixes:" tag. I would think "Fixes:" is > > preferred over "# " if

Re: [PATCH] mm:vmalloc add vm_struct for vm_map_ram

On Thu, 8 Nov 2018 19:14:49 +0800 Zhaoyang Huang wrote: > There is no caller and pages information etc for the area which is > created by vm_map_ram as well as the page count > VMAP_MAX_ALLOC. > Add them on in this commit. Well I can kind of see what this is doing - it increases the amount of

Re: [PATCH] mm:vmalloc add vm_struct for vm_map_ram

On Thu, 8 Nov 2018 19:14:49 +0800 Zhaoyang Huang wrote: > There is no caller and pages information etc for the area which is > created by vm_map_ram as well as the page count > VMAP_MAX_ALLOC. > Add them on in this commit. Well I can kind of see what this is doing - it increases the amount of

[PATCH 3.18 012/144] team: Forbid enslaving team device to itself

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 471b83bd8bbe4e89743683ef8ecb78f7029d8288 ] team's ndo_add_slave() acquires 'team->lock' and later tries to open the newly enslaved device via dev_open(). This

[PATCH 3.18 007/144] ip_tunnel: be careful when accessing the inner header

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit ccfec9e5cb2d48df5a955b7bf47f7782157d3bc2] Cong noted that we need the same checks introduced by commit 76c0ddd8c3a6 ("ip6_tunnel: be careful when accessing the

[PATCH 3.18 004/144] mach64: detect the dot clock divider correctly on sparc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 76ebebd2464c5c8a4453c98b6dbf9c95a599e810 upstream. On Sun Ultra 5, it happens that the dot clock is not set up properly for some videomodes. For example, if we set the

[PATCH 3.18 003/144] stmmac: fix valid numbers of unicast filter entries

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jongsung Kim [ Upstream commit edf2ef7242805e53ec2e0841db26e06d8bc7da70 ] Synopsys DWC Ethernet MAC can be configured to have 1..32, 64, or 128 unicast filter entries. (Table 7-8 MAC Address

[PATCH 3.18 012/144] team: Forbid enslaving team device to itself

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 471b83bd8bbe4e89743683ef8ecb78f7029d8288 ] team's ndo_add_slave() acquires 'team->lock' and later tries to open the newly enslaved device via dev_open(). This

[PATCH 3.18 007/144] ip_tunnel: be careful when accessing the inner header

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit ccfec9e5cb2d48df5a955b7bf47f7782157d3bc2] Cong noted that we need the same checks introduced by commit 76c0ddd8c3a6 ("ip6_tunnel: be careful when accessing the

[PATCH 3.18 004/144] mach64: detect the dot clock divider correctly on sparc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 76ebebd2464c5c8a4453c98b6dbf9c95a599e810 upstream. On Sun Ultra 5, it happens that the dot clock is not set up properly for some videomodes. For example, if we set the

[PATCH 3.18 003/144] stmmac: fix valid numbers of unicast filter entries

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jongsung Kim [ Upstream commit edf2ef7242805e53ec2e0841db26e06d8bc7da70 ] Synopsys DWC Ethernet MAC can be configured to have 1..32, 64, or 128 unicast filter entries. (Table 7-8 MAC Address

[PATCH 3.18 000/144] 3.18.125-stable review

This is the start of the stable review cycle for the 3.18.125 release. There are 144 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat Nov 10 21:50:17 UTC 2018. Anything

[PATCH 3.18 000/144] 3.18.125-stable review

This is the start of the stable review cycle for the 3.18.125 release. There are 144 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat Nov 10 21:50:17 UTC 2018. Anything

[PATCH 3.18 026/144] ax88179_178a: Check for supported Wake-on-LAN modes

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5ba6b4aa9a410c5e2c6417df52b5e2118ea9b467 ] The driver currently silently accepts unsupported Wake-on-LAN modes (other than WAKE_PHY or WAKE_MAGIC) without reporting that to the

[PATCH 3.18 024/144] xfrm: validate template mode

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32bf94fb5c2ec4ec842152d0e5937cd4bb6738fa ] XFRM mode parameters passed as part of the user templates in the IP_XFRM_POLICY are never properly validated. Passing values other than

[PATCH 3.18 023/144] ARM: 8799/1: mm: fix pci_ioremap_io() offset check

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a58ac65e2d7969bcdf1b6acb70fa4d12a88e53e ] IO_SPACE_LIMIT is the ending address of the PCI IO space, i.e something like 0xf (and not 0x10). Therefore, when offset = 0xf

[PATCH 3.18 026/144] ax88179_178a: Check for supported Wake-on-LAN modes

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5ba6b4aa9a410c5e2c6417df52b5e2118ea9b467 ] The driver currently silently accepts unsupported Wake-on-LAN modes (other than WAKE_PHY or WAKE_MAGIC) without reporting that to the

[PATCH 3.18 024/144] xfrm: validate template mode

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32bf94fb5c2ec4ec842152d0e5937cd4bb6738fa ] XFRM mode parameters passed as part of the user templates in the IP_XFRM_POLICY are never properly validated. Passing values other than

[PATCH 3.18 023/144] ARM: 8799/1: mm: fix pci_ioremap_io() offset check

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a58ac65e2d7969bcdf1b6acb70fa4d12a88e53e ] IO_SPACE_LIMIT is the ending address of the PCI IO space, i.e something like 0xf (and not 0x10). Therefore, when offset = 0xf

[PATCH 3.18 030/144] perf/ring_buffer: Prevent concurent ring buffer access

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cd6fb677ce7e460c25bdd66f689734102ec7d642 ] Some of the scheduling tracepoints allow the perf_tp_event code to write to ring buffer under different cpu than the code is running on.

[PATCH 3.18 030/144] perf/ring_buffer: Prevent concurent ring buffer access

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cd6fb677ce7e460c25bdd66f689734102ec7d642 ] Some of the scheduling tracepoints allow the perf_tp_event code to write to ring buffer under different cpu than the code is running on.

[PATCH 3.18 031/144] net: cxgb3_main: fix a missing-check bug

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c05d88818ab6571816b93edce4d53703870d7ae ] In cxgb_extension_ioctl(), the command of the ioctl is firstly copied from the user-space buffer 'useraddr' to 'cmd' and checked through

[PATCH 3.18 021/144] xfrm6: call kfree_skb when skb is toobig

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 215ab0f021c9fea3c18b75e7d522400ee6a49990 ] After commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ("vti6: fix PMTU caching and reporting on xmit"), some too big skbs might be

[PATCH 3.18 020/144] xfrm: Validate address prefix lengths in the xfrm selector.

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 3.18 015/144] rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 0e1d6eca5113858ed2caea61a5adc03c595f6096 ] We have an impressive number of syzkaller bugs that are linked to the fact that syzbot was able to create a

[PATCH 3.18 031/144] net: cxgb3_main: fix a missing-check bug

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c05d88818ab6571816b93edce4d53703870d7ae ] In cxgb_extension_ioctl(), the command of the ioctl is firstly copied from the user-space buffer 'useraddr' to 'cmd' and checked through

[PATCH 3.18 021/144] xfrm6: call kfree_skb when skb is toobig

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 215ab0f021c9fea3c18b75e7d522400ee6a49990 ] After commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ("vti6: fix PMTU caching and reporting on xmit"), some too big skbs might be

[PATCH 3.18 020/144] xfrm: Validate address prefix lengths in the xfrm selector.

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 3.18 015/144] rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 0e1d6eca5113858ed2caea61a5adc03c595f6096 ] We have an impressive number of syzkaller bugs that are linked to the fact that syzbot was able to create a

[PATCH 3.18 013/144] net: mvpp2: Extract the correct ethtype from the skb for tx csum offload

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Chevallier [ Upstream commit 35f3625c21852ad839f20c91c7d81c4c1101e207 ] When offloading the L3 and L4 csum computation on TX, we need to extract the l3_proto from the ethtype,

[PATCH 3.18 013/144] net: mvpp2: Extract the correct ethtype from the skb for tx csum offload

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Chevallier [ Upstream commit 35f3625c21852ad839f20c91c7d81c4c1101e207 ] When offloading the L3 and L4 csum computation on TX, we need to extract the l3_proto from the ethtype,

[PATCH 3.18 042/144] pinctrl: at91: fix null pointer dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1ab36387ea4face01aac3560b396b1e2ce07c4ff ] Not all gpio banks are necessarily enabled, in the current code this can lead to null pointer dereferences. [ 51.13] Unable to

[PATCH 3.18 044/144] ARM: shmobile: r8a7740: Instantiate GIC from C board code in legacy builds

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d034f53cc6c5c09a4e10cb9716986f3844c58514 ] As of commit 9a1091ef0017c40a ("irqchip: gic: Support hierarchy irq domain."), armadillo-legacy hangs during boot with: sh-tmu.0:

[PATCH 3.18 033/144] ocfs2: fix journal commit deadlock in ocfs2_convert_inline_data_to_extents

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 15eba0fe3eeaeb1b80489c1ebb9d47d6d7003f57 ] Similar to ocfs2_write_end_nolock() which is metioned at commit 136f49b91710 ("ocfs2: fix journal commit deadlock"), we should unlock

[PATCH 3.18 045/144] usb: musb: Fix a few off-by-one lengths

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e87c3f80ad0490d26ffe04754b7d094463b40f30 ] !strncmp(buf, "force host", 9) is true if and only if buf starts with "force hos". This was obviously not what was intended. The same

[PATCH 3.18 046/144] usb: gadget: f_uac1: access freed memory at f_audio_free_inst

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4fde6204df052bb89ba3d915ed6ed9f306f3cfa1 ] At f_audio_free_inst, it tries to access struct gaudio *card which is freed at f_audio_free, it causes below oops if the audio device is

[PATCH 3.18 042/144] pinctrl: at91: fix null pointer dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1ab36387ea4face01aac3560b396b1e2ce07c4ff ] Not all gpio banks are necessarily enabled, in the current code this can lead to null pointer dereferences. [ 51.13] Unable to

[PATCH 3.18 044/144] ARM: shmobile: r8a7740: Instantiate GIC from C board code in legacy builds

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d034f53cc6c5c09a4e10cb9716986f3844c58514 ] As of commit 9a1091ef0017c40a ("irqchip: gic: Support hierarchy irq domain."), armadillo-legacy hangs during boot with: sh-tmu.0:

[PATCH 3.18 033/144] ocfs2: fix journal commit deadlock in ocfs2_convert_inline_data_to_extents

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 15eba0fe3eeaeb1b80489c1ebb9d47d6d7003f57 ] Similar to ocfs2_write_end_nolock() which is metioned at commit 136f49b91710 ("ocfs2: fix journal commit deadlock"), we should unlock

[PATCH 3.18 045/144] usb: musb: Fix a few off-by-one lengths

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e87c3f80ad0490d26ffe04754b7d094463b40f30 ] !strncmp(buf, "force host", 9) is true if and only if buf starts with "force hos". This was obviously not what was intended. The same

[PATCH 3.18 046/144] usb: gadget: f_uac1: access freed memory at f_audio_free_inst

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4fde6204df052bb89ba3d915ed6ed9f306f3cfa1 ] At f_audio_free_inst, it tries to access struct gaudio *card which is freed at f_audio_free, it causes below oops if the audio device is

[PATCH 3.18 043/144] PCI: Mark Atheros AR9580 to avoid bus reset

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8e2e03179923479ca0c0b6fdc7c93ecf89bce7a8 ] Similar to the AR93xx and the AR94xx series, the AR95xx also have the same quirk for the Bus Reset. It will lead to instant system reset

[PATCH 3.18 043/144] PCI: Mark Atheros AR9580 to avoid bus reset

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8e2e03179923479ca0c0b6fdc7c93ecf89bce7a8 ] Similar to the AR93xx and the AR94xx series, the AR95xx also have the same quirk for the Bus Reset. It will lead to instant system reset

[PATCH 3.18 051/144] iio: iio: Fix iio_channel_read return if channel havnt info

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 65de7654d39c70c2b942f801cea01590cf7e3458 ] When xilinx-xadc is used with hwmon driver to read voltage, offset used for temperature is always applied whatever the channel.

[PATCH 3.18 050/144] phy: phy-ti-pipe3: fix inconsistent enumeration of PCIe gen2 cards

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0bc09f9cdc589e0b54724096138996a00b19babb ] Prior to DRA74x silicon rev 1.1, pcie_pcs register bits 8-15 and bits 16-23 were used to configure RC delay count for phy1 and phy2

[PATCH 3.18 051/144] iio: iio: Fix iio_channel_read return if channel havnt info

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 65de7654d39c70c2b942f801cea01590cf7e3458 ] When xilinx-xadc is used with hwmon driver to read voltage, offset used for temperature is always applied whatever the channel.

[PATCH 3.18 050/144] phy: phy-ti-pipe3: fix inconsistent enumeration of PCIe gen2 cards

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0bc09f9cdc589e0b54724096138996a00b19babb ] Prior to DRA74x silicon rev 1.1, pcie_pcs register bits 8-15 and bits 16-23 were used to configure RC delay count for phy1 and phy2

[PATCH 3.18 035/144] USB: qcserial: Fix support for HP lt4112 LTE/HSPA+ Gobi 4G Modem

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 59536da34513c594af2a6fd35ba65ea45b6960a1 ] The DEVICE_HWI type was added under the faulty assumption that Huawei devices based on Qualcomm chipsets and firmware use the static USB

[PATCH 3.18 035/144] USB: qcserial: Fix support for HP lt4112 LTE/HSPA+ Gobi 4G Modem

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 59536da34513c594af2a6fd35ba65ea45b6960a1 ] The DEVICE_HWI type was added under the faulty assumption that Huawei devices based on Qualcomm chipsets and firmware use the static USB

[PATCH 3.18 052/144] ARM: dra7xx: Fix counter frequency drift for AM572x errata i856

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afc9d590b8a150cfeaac0078ef5de6fb21a5ea6a ] Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external crystal is not enabled at power up. Instead the CPU falls back

Re: [PATCH 3.18 053/144] ARM: OMAP2+: Fix n900 board name for legacy user space

On Thu, Nov 08, 2018 at 11:05:30PM +0100, Pavel Machek wrote: > On Thu 2018-11-08 13:50:24, Greg Kroah-Hartman wrote: > > 3.18-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > [ Upstream commit 71c4f6027da75c6c1fd92e05b63108a09ec2b109 ] >

[PATCH 3.18 040/144] ahci_xgene: Fix the DMA state machine lockup for the ATA_CMD_PACKET PIO mode command.

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1102407bb714dcebb43f385335bcb72f6b8843bc ] This patch addresses the issue with ATA_CMD_PACKET pio mode command for enumeration and device detection with ATAPI devices. The X-Gene

[PATCH 3.18 036/144] cxl: Fix issues when unmapping contexts

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0712dc7e73e59d79bcead5d5520acf4e9e917e87 ] An issue was introduced with "cxl: Unmap MMIO regions when detaching a context" (b123429e6a9e8d03aacf888d23262835f0081448) where closing a

[PATCH 3.18 053/144] ARM: OMAP2+: Fix n900 board name for legacy user space

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 71c4f6027da75c6c1fd92e05b63108a09ec2b109 ] N900 legacy user space apps need the board name in /proc/cpuinfo to work properly for the Hardware entry. For other boards this should

[PATCH 3.18 053/144] ARM: OMAP2+: Fix n900 board name for legacy user space

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 71c4f6027da75c6c1fd92e05b63108a09ec2b109 ] N900 legacy user space apps need the board name in /proc/cpuinfo to work properly for the Hardware entry. For other boards this should

[PATCH 3.18 052/144] ARM: dra7xx: Fix counter frequency drift for AM572x errata i856

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afc9d590b8a150cfeaac0078ef5de6fb21a5ea6a ] Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external crystal is not enabled at power up. Instead the CPU falls back

Re: [PATCH 3.18 053/144] ARM: OMAP2+: Fix n900 board name for legacy user space

On Thu, Nov 08, 2018 at 11:05:30PM +0100, Pavel Machek wrote: > On Thu 2018-11-08 13:50:24, Greg Kroah-Hartman wrote: > > 3.18-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > [ Upstream commit 71c4f6027da75c6c1fd92e05b63108a09ec2b109 ] >

[PATCH 3.18 040/144] ahci_xgene: Fix the DMA state machine lockup for the ATA_CMD_PACKET PIO mode command.

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1102407bb714dcebb43f385335bcb72f6b8843bc ] This patch addresses the issue with ATA_CMD_PACKET pio mode command for enumeration and device detection with ATAPI devices. The X-Gene

[PATCH 3.18 036/144] cxl: Fix issues when unmapping contexts

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0712dc7e73e59d79bcead5d5520acf4e9e917e87 ] An issue was introduced with "cxl: Unmap MMIO regions when detaching a context" (b123429e6a9e8d03aacf888d23262835f0081448) where closing a

[PATCH 3.18 037/144] s390/ftrace/jprobes: Fix conflict between jprobes and function graph tracing

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e64a5470dcd2900ab8f8f83638c00098b10e6300 ] This fixes the same issue Steven already fixed for x86 in following commit: 237d28db036e ftrace/jprobes/x86: Fix conflict between

[PATCH 3.18 037/144] s390/ftrace/jprobes: Fix conflict between jprobes and function graph tracing

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e64a5470dcd2900ab8f8f83638c00098b10e6300 ] This fixes the same issue Steven already fixed for x86 in following commit: 237d28db036e ftrace/jprobes/x86: Fix conflict between

[PATCH 3.18 068/144] ARM: at91/dt: sam9263: Add missing clocks to lcdc node

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 55eb9c343fdd3611ae3de6ab8a8512f303d3f581 ] atmel_lcdfb needs also uses hclk clock, but AT91SAM9263 doesn't have that specific clock, so use lcd_clk twice. The same was done in

[PATCH 3.18 071/144] tracing: Fix enabling of syscall events on the command line

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce1039bd3a89e99e4f624e75fb1777fc92d76eb3 ] Commit 5f893b2639b2 "tracing: Move enabling tracepoints to just after rcu_init()" broke the enabling of system call events from the

[PATCH 3.18 055/144] NFSv4/v4.1: Verify the client owner id during trunking detection

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 55b9df93ddd684cbc4c2dee9b8a99f6e48348212 ] While we normally expect the NFSv4 client to always send the same client owner to all servers, there are a couple of situations where that

[PATCH 3.18 072/144] perf/rapl: Fix sysfs_show() initialization for RAPL PMU

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 433678bdc6ed39f053c55da96b51de5bf0aeebb1 ] This patch fixes a problem with the initialization of the sysfs_show() routine for the RAPL PMU. The current code was wrongly relying on

[PATCH 3.18 068/144] ARM: at91/dt: sam9263: Add missing clocks to lcdc node

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 55eb9c343fdd3611ae3de6ab8a8512f303d3f581 ] atmel_lcdfb needs also uses hclk clock, but AT91SAM9263 doesn't have that specific clock, so use lcd_clk twice. The same was done in

[PATCH 3.18 071/144] tracing: Fix enabling of syscall events on the command line

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce1039bd3a89e99e4f624e75fb1777fc92d76eb3 ] Commit 5f893b2639b2 "tracing: Move enabling tracepoints to just after rcu_init()" broke the enabling of system call events from the

[PATCH 3.18 055/144] NFSv4/v4.1: Verify the client owner id during trunking detection

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 55b9df93ddd684cbc4c2dee9b8a99f6e48348212 ] While we normally expect the NFSv4 client to always send the same client owner to all servers, there are a couple of situations where that

[PATCH 3.18 072/144] perf/rapl: Fix sysfs_show() initialization for RAPL PMU

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 433678bdc6ed39f053c55da96b51de5bf0aeebb1 ] This patch fixes a problem with the initialization of the sysfs_show() routine for the RAPL PMU. The current code was wrongly relying on

[PATCH 3.18 070/144] fbdev/broadsheetfb: fix memory leak

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ef6899cdc8608e2f018e590683f04bb04a069704 ] static code analysis from cppcheck reports: [drivers/video/fbdev/broadsheetfb.c:673]: (error) Memory leak: sector_buffer sector_buffer

[PATCH 3.18 056/144] NFS: Ignore transport protocol when detecting server trunking

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a01edf0058df98d6cc734c5a4ecc51f929a86ec ] Detect server trunking across transport protocols. Otherwise, an RDMA mount and a TCP mount of the same server will end up with separate

[PATCH 3.18 070/144] fbdev/broadsheetfb: fix memory leak

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ef6899cdc8608e2f018e590683f04bb04a069704 ] static code analysis from cppcheck reports: [drivers/video/fbdev/broadsheetfb.c:673]: (error) Memory leak: sector_buffer sector_buffer

[PATCH 3.18 056/144] NFS: Ignore transport protocol when detecting server trunking

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a01edf0058df98d6cc734c5a4ecc51f929a86ec ] Detect server trunking across transport protocols. Otherwise, an RDMA mount and a TCP mount of the same server will end up with separate

[PATCH 3.18 074/144] perf machine: Fix __machine__findnew_thread() error path

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 260d819e3abdbdaa2b88fb983d1314f1b263f9e2 ] When thread__init_map_groups() fails, a new thread should be removed from the rbtree since it's gonna be freed. Also update last match

[PATCH 3.18 073/144] perf/x86/intel: Fix bug for "cycles:p" and "cycles:pp" on SLM

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 33636732dcd7cc738a5913bb730d663c6b03c8fb ] cycles:p and cycles:pp do not work on SLM since commit: 86a04461a99f ("perf/x86: Revamp PEBS event selection") UOPS_RETIRED.ALL is

[PATCH 3.18 075/144] perf tools: Fix statfs.f_type data type mismatch build error with uclibc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit db1806edcfef007d9594435a331dcf7e7f1b8fac ] ARC Linux uses the no legacy syscalls abi and corresponding uClibc headers statfs defines f_type to be U32 which causes perf build

[PATCH 3.18 058/144] arm: dts: Use pmu_system_controller phandle for dp phy

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e93e54544adf3aa6908b821e896cb17a562cb683 ] DP PHY now require pmu-system-controller to handle PMU register to control PHY's power isolation. Adding the same to dp-phy node.

[PATCH 3.18 074/144] perf machine: Fix __machine__findnew_thread() error path

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 260d819e3abdbdaa2b88fb983d1314f1b263f9e2 ] When thread__init_map_groups() fails, a new thread should be removed from the rbtree since it's gonna be freed. Also update last match

[PATCH 3.18 073/144] perf/x86/intel: Fix bug for "cycles:p" and "cycles:pp" on SLM

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 33636732dcd7cc738a5913bb730d663c6b03c8fb ] cycles:p and cycles:pp do not work on SLM since commit: 86a04461a99f ("perf/x86: Revamp PEBS event selection") UOPS_RETIRED.ALL is

[PATCH 3.18 075/144] perf tools: Fix statfs.f_type data type mismatch build error with uclibc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit db1806edcfef007d9594435a331dcf7e7f1b8fac ] ARC Linux uses the no legacy syscalls abi and corresponding uClibc headers statfs defines f_type to be U32 which causes perf build

[PATCH 3.18 058/144] arm: dts: Use pmu_system_controller phandle for dp phy

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e93e54544adf3aa6908b821e896cb17a562cb683 ] DP PHY now require pmu-system-controller to handle PMU register to control PHY's power isolation. Adding the same to dp-phy node.

Re: [driver-core PATCH v6 3/9] device core: Consolidate locking and unlocking of parent and device

Hi, Alex, On 11/08/2018 10:06 AM, Alexander Duyck wrote: +/* + * __device_driver_lock - release locks needed to manipulate dev->drv You meant to say __device_driver_unlock, right? + * @dev: Device we will update driver info for + * @parent: Parent device. Needed if the bus requires parent

Re: [driver-core PATCH v6 3/9] device core: Consolidate locking and unlocking of parent and device

Hi, Alex, On 11/08/2018 10:06 AM, Alexander Duyck wrote: +/* + * __device_driver_lock - release locks needed to manipulate dev->drv You meant to say __device_driver_unlock, right? + * @dev: Device we will update driver info for + * @parent: Parent device. Needed if the bus requires parent

[PATCH 3.18 059/144] scsi: ->queue_rq cant sleep

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 70a0f2c1898c6abf53670e55642b6e840b003892 ] The blk-mq ->queue_rq method is always called from process context, but might have preemption disabled. This means we still always have

[PATCH 3.18 059/144] scsi: ->queue_rq cant sleep

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 70a0f2c1898c6abf53670e55642b6e840b003892 ] The blk-mq ->queue_rq method is always called from process context, but might have preemption disabled. This means we still always have

[PATCH 3.18 087/144] Btrfs: avoid syncing log in the fast fsync path when not necessary

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b659ef027792219b590d67a2baf1643a93727d29 ] Commit 3a8b36f37806 ("Btrfs: fix data loss in the fast fsync path") added a performance regression for that causes an unnecessary sync of

[PATCH 3.18 054/144] NFSv4: Cache the NFSv4/v4.1 client owner_id in the struct nfs_client

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ceb3a16c070c403f5f9ca46b46cf2bb79ea11750 ] Ensure that we cache the NFSv4/v4.1 client owner_id so that we can verify it when we're doing trunking detection. Signed-off-by: Trond

[PATCH 3.18 087/144] Btrfs: avoid syncing log in the fast fsync path when not necessary

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b659ef027792219b590d67a2baf1643a93727d29 ] Commit 3a8b36f37806 ("Btrfs: fix data loss in the fast fsync path") added a performance regression for that causes an unnecessary sync of

[PATCH 3.18 054/144] NFSv4: Cache the NFSv4/v4.1 client owner_id in the struct nfs_client

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ceb3a16c070c403f5f9ca46b46cf2bb79ea11750 ] Ensure that we cache the NFSv4/v4.1 client owner_id so that we can verify it when we're doing trunking detection. Signed-off-by: Trond

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 03:32:58PM -0700, Keith Busch wrote: > On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > > I'm having second thoughts about this. One thing I'm uncomfortable > > > with is that

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 03:32:58PM -0700, Keith Busch wrote: > On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > > I'm having second thoughts about this. One thing I'm uncomfortable > > > with is that

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