[PATCH 4.9 68/94] drm/gma500/psb: Actually use VBT mode when it is found

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Patrik Jakobsson commit 82bc9a42cf854fdf63155759c0aa790bd1f361b0 upstream. With LVDS we were incorrectly picking the pre-programmed mode instead of the prefered

[PATCH 4.9 78/94] xfs: drop iolock from reclaim context to appease lockdep

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 3b4683c294095b5f777c03307ef8c60f47320e12 upstream. Lockdep complains about use of the iolock in inode reclaim context because it doesn't understand that

[PATCH 4.9 68/94] drm/gma500/psb: Actually use VBT mode when it is found

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Patrik Jakobsson commit 82bc9a42cf854fdf63155759c0aa790bd1f361b0 upstream. With LVDS we were incorrectly picking the pre-programmed mode instead of the prefered mode provided by VBT. Make sure

[PATCH 4.9 78/94] xfs: drop iolock from reclaim context to appease lockdep

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 3b4683c294095b5f777c03307ef8c60f47320e12 upstream. Lockdep complains about use of the iolock in inode reclaim context because it doesn't understand that reclaim has the

[PATCH 4.9 70/94] xfs: use ->b_state to fix buffer I/O accounting release race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 63db7c815bc0997c29e484d2409684fdd9fcd93b upstream. We've had user reports of unmount hangs in xfs_wait_buftarg() that analysis shows is due to

[PATCH 4.9 70/94] xfs: use ->b_state to fix buffer I/O accounting release race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 63db7c815bc0997c29e484d2409684fdd9fcd93b upstream. We've had user reports of unmount hangs in xfs_wait_buftarg() that analysis shows is due to btp->bt_io_count == -1.

[PATCH 4.9 73/94] xfs: rework the inline directory verifiers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 78420281a9d74014af7616958806c3aba056319e upstream. The inline directory verifiers should be called on the inode fork data, which means after

[PATCH 4.9 73/94] xfs: rework the inline directory verifiers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 78420281a9d74014af7616958806c3aba056319e upstream. The inline directory verifiers should be called on the inode fork data, which means after iformat_local on the read

[PATCH 4.9 72/94] xfs: verify inline directory data forks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 630a04e79dd41ff746b545d4fc052e0abb836120 upstream. When we're reading or writing the data fork of an inline directory, check the contents to

[PATCH 4.9 72/94] xfs: verify inline directory data forks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 630a04e79dd41ff746b545d4fc052e0abb836120 upstream. When we're reading or writing the data fork of an inline directory, check the contents to make sure we're not

[PATCH 4.9 79/94] xfs: fix integer truncation in xfs_bmap_remap_alloc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 52813fb13ff90bd9c39a93446cbf1103c290b6e9 upstream. bno should be a xfs_fsblock_t, which is 64-bit wides instead of a xfs_aglock_t, which truncates the

[PATCH 4.9 79/94] xfs: fix integer truncation in xfs_bmap_remap_alloc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 52813fb13ff90bd9c39a93446cbf1103c290b6e9 upstream. bno should be a xfs_fsblock_t, which is 64-bit wides instead of a xfs_aglock_t, which truncates the value to 32

[PATCH 4.9 90/94] xfs: bad assertion for delalloc an extent that start at i_size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zorro Lang commit 892d2a5f705723b2cb488bfb38bcbdcf83273184 upstream. By run fsstress long enough time enough in RHEL-7, I find an assertion failure (harder to reproduce on

[PATCH 4.11 004/115] s390/qeth: handle sysfs error during initialization

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit 9111e7880ccf419548c7b0887df020b08eadb075 ] When setting up the device from within the layer discipline's probe routine, creating the

[PATCH 4.11 008/115] bpf, arm64: fix faulty emission of map access in tail calls

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit d8b54110ee944de522ccd3531191f39986ec20f9 ] Shubham was recently asking on netdev why in arm64 JIT we don't multiply the index for

[PATCH 4.9 90/94] xfs: bad assertion for delalloc an extent that start at i_size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zorro Lang commit 892d2a5f705723b2cb488bfb38bcbdcf83273184 upstream. By run fsstress long enough time enough in RHEL-7, I find an assertion failure (harder to reproduce on linux-4.11, but

[PATCH 4.11 004/115] s390/qeth: handle sysfs error during initialization

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit 9111e7880ccf419548c7b0887df020b08eadb075 ] When setting up the device from within the layer discipline's probe routine, creating the layer-specific sysfs

[PATCH 4.11 008/115] bpf, arm64: fix faulty emission of map access in tail calls

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit d8b54110ee944de522ccd3531191f39986ec20f9 ] Shubham was recently asking on netdev why in arm64 JIT we don't multiply the index for accessing the tail call

[PATCH 4.9 69/94] xfs: Fix missed holes in SEEK_HOLE implementation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 5375023ae1266553a7baa0845e82917d8803f48c upstream. XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command:

[PATCH 4.9 81/94] xfs: prevent multi-fsb dir readahead from reading random blocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit cb52ee334a45ae6c78a3999e4b473c43ddc528f4 upstream. Directory block readahead uses a complex iteration mechanism to map between high-level directory

[PATCH 4.9 80/94] xfs: handle array index overrun in xfs_dir2_leaf_readbuf()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit 023cc840b40fad95c6fe26fff1d380a8c9d45939 upstream. Carlos had a case where "find" seemed to start spinning forever and never return. This was on a

[PATCH 4.9 69/94] xfs: Fix missed holes in SEEK_HOLE implementation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 5375023ae1266553a7baa0845e82917d8803f48c upstream. XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c

[PATCH 4.9 81/94] xfs: prevent multi-fsb dir readahead from reading random blocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit cb52ee334a45ae6c78a3999e4b473c43ddc528f4 upstream. Directory block readahead uses a complex iteration mechanism to map between high-level directory blocks and underlying

[PATCH 4.9 80/94] xfs: handle array index overrun in xfs_dir2_leaf_readbuf()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit 023cc840b40fad95c6fe26fff1d380a8c9d45939 upstream. Carlos had a case where "find" seemed to start spinning forever and never return. This was on a filesystem with

[PATCH 4.9 83/94] xfs: support ability to wait on new inodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 756baca27fff3ecaeab9dbc7a5ee35a1d7bc0c7f upstream. Inodes that are inserted into the perag tree but still under construction are flagged with the

[PATCH 4.9 83/94] xfs: support ability to wait on new inodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 756baca27fff3ecaeab9dbc7a5ee35a1d7bc0c7f upstream. Inodes that are inserted into the perag tree but still under construction are flagged with the XFS_INEW bit. Most

[PATCH 4.11 005/115] s390/qeth: unbreak OSM and OSN support

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 2d2ebb3ed0c6acfb014f98e427298673a5d07b82 ] commit b4d72c08b358 ("qeth: bridgeport support - basic control") broke the support for

[PATCH 4.9 74/94] xfs: fix kernel memory exposure problems

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit bf9216f922612d2db7666aae01e65064da2ffb3a upstream. Fix a memory exposure problems in inumbers where we allocate an array of structures with

[PATCH 4.11 029/115] net/mlx5: Avoid using pending command interface slots

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Mohamad Haj Yahia [ Upstream commit 73dd3a4839c1d27c36d4dcc92e1ff44225ecbeb7 ] Currently when firmware command gets stuck or it takes long time to complete, the driver

[PATCH 4.11 000/115] 4.11.4-stable review

This is the start of the stable review cycle for the 4.11.4 release. There are 115 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 Wed Jun 7 15:30:31 UTC 2017. Anything

[PATCH 4.9 84/94] xfs: update ag iterator to support wait on new inodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit ae2c4ac2dd39b23a87ddb14ceddc3f2872c6aef5 upstream. The AG inode iterator currently skips new inodes as such inodes are inserted into the inode radix

[PATCH 4.9 74/94] xfs: fix kernel memory exposure problems

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit bf9216f922612d2db7666aae01e65064da2ffb3a upstream. Fix a memory exposure problems in inumbers where we allocate an array of structures with holes, fail to zero the

[PATCH 4.11 029/115] net/mlx5: Avoid using pending command interface slots

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Mohamad Haj Yahia [ Upstream commit 73dd3a4839c1d27c36d4dcc92e1ff44225ecbeb7 ] Currently when firmware command gets stuck or it takes long time to complete, the driver command will get

[PATCH 4.11 000/115] 4.11.4-stable review

This is the start of the stable review cycle for the 4.11.4 release. There are 115 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 Wed Jun 7 15:30:31 UTC 2017. Anything

[PATCH 4.9 84/94] xfs: update ag iterator to support wait on new inodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit ae2c4ac2dd39b23a87ddb14ceddc3f2872c6aef5 upstream. The AG inode iterator currently skips new inodes as such inodes are inserted into the inode radix tree before they are

[PATCH 4.11 005/115] s390/qeth: unbreak OSM and OSN support

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 2d2ebb3ed0c6acfb014f98e427298673a5d07b82 ] commit b4d72c08b358 ("qeth: bridgeport support - basic control") broke the support for OSM and OSN devices as

[PATCH 4.11 012/115] tipc: make macro tipc_wait_for_cond() smp safe

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jon Paul Maloy [ Upstream commit 844cf763fba654436d3a4279b6a672c196cf1901 ] The macro tipc_wait_for_cond() is embedding the macro sk_wait_event() to fulfil its task.

[PATCH 4.9 92/94] xfs: avoid mount-time deadlock in CoW extent recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 3ecb3ac7b950ff8f6c6a61e8b7b0d6e3546429a0 upstream. If a malicious user corrupts the refcount btree to cause a cycle between different levels of

Re: [PATCH v3 2/5] dt-bindings: qcom: Add IPQ8074 bindings

On Thu, Jun 01, 2017 at 04:57:59PM +0530, Varadarajan Narayanan wrote: > Signed-off-by: Varadarajan Narayanan > --- > Documentation/devicetree/bindings/arm/qcom.txt | 2 ++ > 1 file changed, 2 insertions(+) I acked v2. Please add acks when posting new versions. Rob

[PATCH 4.9 92/94] xfs: avoid mount-time deadlock in CoW extent recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 3ecb3ac7b950ff8f6c6a61e8b7b0d6e3546429a0 upstream. If a malicious user corrupts the refcount btree to cause a cycle between different levels of the tree, the next mount

Re: [PATCH v3 2/5] dt-bindings: qcom: Add IPQ8074 bindings

On Thu, Jun 01, 2017 at 04:57:59PM +0530, Varadarajan Narayanan wrote: > Signed-off-by: Varadarajan Narayanan > --- > Documentation/devicetree/bindings/arm/qcom.txt | 2 ++ > 1 file changed, 2 insertions(+) I acked v2. Please add acks when posting new versions. Rob

[PATCH 4.11 012/115] tipc: make macro tipc_wait_for_cond() smp safe

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jon Paul Maloy [ Upstream commit 844cf763fba654436d3a4279b6a672c196cf1901 ] The macro tipc_wait_for_cond() is embedding the macro sk_wait_event() to fulfil its task. The latter, in turn, is

[PATCH 4.11 009/115] netem: fix skb_orphan_partial()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit f6ba8d33cfbb46df569972e64dbb5bb7e929bfd9 ] I should have known that lowering skb->truesize was dangerous :/ In case packets are not

[PATCH 4.11 009/115] netem: fix skb_orphan_partial()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit f6ba8d33cfbb46df569972e64dbb5bb7e929bfd9 ] I should have known that lowering skb->truesize was dangerous :/ In case packets are not leaving the host via a

[PATCH 4.11 001/115] dccp/tcp: do not inherit mc_list from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 657831ffc38e30092a2d5f03d385d710eb88b09a ] syzkaller found a way to trigger double frees from ip_mc_drop_socket() It turns out that leave

[PATCH 4.11 001/115] dccp/tcp: do not inherit mc_list from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 657831ffc38e30092a2d5f03d385d710eb88b09a ] syzkaller found a way to trigger double frees from ip_mc_drop_socket() It turns out that leave a copy of parent

[PATCH 4.11 011/115] tcp: avoid fragmenting peculiar skbs in SACK

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Yuchung Cheng [ Upstream commit b451e5d24ba6687c6f0e7319c727a709a1846c06 ] This patch fixes a bug in splitting an SKB during SACK processing. Specifically if an skb

[PATCH 4.11 011/115] tcp: avoid fragmenting peculiar skbs in SACK

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Yuchung Cheng [ Upstream commit b451e5d24ba6687c6f0e7319c727a709a1846c06 ] This patch fixes a bug in splitting an SKB during SACK processing. Specifically if an skb contains multiple packets

[PATCH 4.9 93/94] xfs: fix unaligned access in xfs_btree_visit_blocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit a4d768e702de224cc85e0c8eac9311763403b368 upstream. This structure copy was throwing unaligned access warnings on sparc64: Kernel unaligned access at

[PATCH 4.9 93/94] xfs: fix unaligned access in xfs_btree_visit_blocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit a4d768e702de224cc85e0c8eac9311763403b368 upstream. This structure copy was throwing unaligned access warnings on sparc64: Kernel unaligned access at TPC[1043c088]

[PATCH 4.9 89/94] xfs: BMAPX shouldnt barf on inline-format directories

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 6eadbf4c8ba816c10d1c97bed9aa861d9fd17809 upstream. When we're fulfilling a BMAPX request, jump out early if the data fork is in local format.

[PATCH 4.9 89/94] xfs: BMAPX shouldnt barf on inline-format directories

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 6eadbf4c8ba816c10d1c97bed9aa861d9fd17809 upstream. When we're fulfilling a BMAPX request, jump out early if the data fork is in local format. This prevents us from

[PATCH 4.11 007/115] s390/qeth: add missing hash table initializations

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit ebccc7397e4a49ff64c8f44a54895de9d32fe742 ] commit 5f78e29ceebf ("qeth: optimize IP handling in rx_mode callback") added new hash

[PATCH 4.11 003/115] ipv6/dccp: do not inherit ipv6_mc_list from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 83eaddab4378db256d00d295bda6ca997cd13a52 ] Like commit 657831ffc38e ("dccp/tcp: do not inherit mc_list from parent") we should clear

[PATCH 4.11 003/115] ipv6/dccp: do not inherit ipv6_mc_list from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 83eaddab4378db256d00d295bda6ca997cd13a52 ] Like commit 657831ffc38e ("dccp/tcp: do not inherit mc_list from parent") we should clear ipv6_mc_list etc. for IPv6

[PATCH 4.11 007/115] s390/qeth: add missing hash table initializations

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit ebccc7397e4a49ff64c8f44a54895de9d32fe742 ] commit 5f78e29ceebf ("qeth: optimize IP handling in rx_mode callback") added new hash tables, but missed to

[PATCH 4.11 017/115] net/mlx5e: Fix ethtool pause support and advertise reporting

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Gal Pressman [ Upstream commit e3c19503712d6360239b19c14cded56dd63c40d7 ] Pause bit should set when RX pause is on, not TX pause. Also, setting Asym_Pause is incorrect,

Re: [PATCH v3 3/5] clk: qcom: ipq8074: Add Global Clock Controller support

On Thu, Jun 01, 2017 at 04:58:00PM +0530, Varadarajan Narayanan wrote: > From: Abhishek Sahu > > This patch adds support for the global clock controller found on > the IPQ8074 based devices. This includes UART, I2C, SPI etc. > > Signed-off-by: Abhishek Sahu

[PATCH 4.11 017/115] net/mlx5e: Fix ethtool pause support and advertise reporting

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Gal Pressman [ Upstream commit e3c19503712d6360239b19c14cded56dd63c40d7 ] Pause bit should set when RX pause is on, not TX pause. Also, setting Asym_Pause is incorrect, and should be turned

Re: [PATCH v3 3/5] clk: qcom: ipq8074: Add Global Clock Controller support

On Thu, Jun 01, 2017 at 04:58:00PM +0530, Varadarajan Narayanan wrote: > From: Abhishek Sahu > > This patch adds support for the global clock controller found on > the IPQ8074 based devices. This includes UART, I2C, SPI etc. > > Signed-off-by: Abhishek Sahu > Signed-off-by: Varadarajan

[PATCH 4.11 027/115] ipv6: fix out of bound writes in __ip6_append_data()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 232cd35d0804cc241eb887bb8d4d9b3b9881c64a ] Andrey Konovalov and idaif...@gmail.com reported crashes caused by one skb shared_info being

[PATCH 4.11 027/115] ipv6: fix out of bound writes in __ip6_append_data()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 232cd35d0804cc241eb887bb8d4d9b3b9881c64a ] Andrey Konovalov and idaif...@gmail.com reported crashes caused by one skb shared_info being overwritten from

[PATCH 4.11 020/115] net/smc: Add warning about remote memory exposure

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig [ Upstream commit 19a0f7e37c0761a0a1cbf550705a6063c9675223 ] The driver explicitly bypasses APIs to register all memory once a connection is made, and thus

[PATCH 4.11 020/115] net/smc: Add warning about remote memory exposure

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig [ Upstream commit 19a0f7e37c0761a0a1cbf550705a6063c9675223 ] The driver explicitly bypasses APIs to register all memory once a connection is made, and thus allows remote

Re: [6/6] mm: memcontrol: account slab stats per lruvec

mir Davydov <vdavydov@gmail.com> Presumably this is already known, but a remarkable number of crashes in next-20170605 bisects to this patch. Guenter --- Qemu test results: total: 122 pass: 51 fail: 71 Failed tests: arm:vexpress-a9:vexpress_defconfig:vexpress-v2p-c

Re: [6/6] mm: memcontrol: account slab stats per lruvec

s already known, but a remarkable number of crashes in next-20170605 bisects to this patch. Guenter --- Qemu test results: total: 122 pass: 51 fail: 71 Failed tests: arm:vexpress-a9:vexpress_defconfig:vexpress-v2p-ca9 arm:vexpress-a15:vexpress_defconfig:vexpre

[PATCH 4.11 018/115] tcp: eliminate negative reordering in tcp_clean_rtx_queue

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Soheil Hassas Yeganeh [ Upstream commit bafbb9c73241760023d8981191ddd30bb1c6dbac ] tcp_ack() can call tcp_fragment() which may dededuct the value tp->fackets_out when MSS

[PATCH 4.11 018/115] tcp: eliminate negative reordering in tcp_clean_rtx_queue

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Soheil Hassas Yeganeh [ Upstream commit bafbb9c73241760023d8981191ddd30bb1c6dbac ] tcp_ack() can call tcp_fragment() which may dededuct the value tp->fackets_out when MSS changes. When

[PATCH 4.11 021/115] net: Improve handling of failures on link and route dumps

4.11-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit f6c5775ff0bfa62b072face6bf1d40f659f194b2 ] In general, rtnetlink dumps do not anticipate failure to dump a single object (e.g., link or

[PATCH 4.11 021/115] net: Improve handling of failures on link and route dumps

4.11-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit f6c5775ff0bfa62b072face6bf1d40f659f194b2 ] In general, rtnetlink dumps do not anticipate failure to dump a single object (e.g., link or route) on a single pass.

[PATCH 4.11 022/115] ipv6: Prevent overrun when parsing v6 header options

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Craig Gallek [ Upstream commit 2423496af35d94a87156b063ea5cedffc10a70a1 ] The KASAN warning repoted below was discovered with a syzkaller program. The reproducer is

[PATCH 4.11 022/115] ipv6: Prevent overrun when parsing v6 header options

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Craig Gallek [ Upstream commit 2423496af35d94a87156b063ea5cedffc10a70a1 ] The KASAN warning repoted below was discovered with a syzkaller program. The reproducer is basically: int s =

Re: [PATCH v6 00/11] Broadcom Stingray SOC Initial Support

On 06/01/2017 11:34 PM, Anup Patel wrote: > This patchset adds initial support of Broadcom Stingray SOC > by reusing existing Broadcom iProc device drivers. > > Most of the patches in this patchset are DT patches except > the Stingray clock tree support which just one patch. > > This patchset is

Re: [PATCH v6 00/11] Broadcom Stingray SOC Initial Support

On 06/01/2017 11:34 PM, Anup Patel wrote: > This patchset adds initial support of Broadcom Stingray SOC > by reusing existing Broadcom iProc device drivers. > > Most of the patches in this patchset are DT patches except > the Stingray clock tree support which just one patch. > > This patchset is

[PATCH 4.11 015/115] net/packet: fix missing net_device reference release

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Douglas Caetano dos Santos [ Upstream commit d19b183cdc1fa3d70d6abe2a4c369e748cd7ebb8 ] When using a TX ring buffer, if an error occurs processing a control message

[PATCH 4.11 015/115] net/packet: fix missing net_device reference release

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Douglas Caetano dos Santos [ Upstream commit d19b183cdc1fa3d70d6abe2a4c369e748cd7ebb8 ] When using a TX ring buffer, if an error occurs processing a control message (e.g. invalid message),

[PATCH 4.11 043/115] sparc: Fix -Wstringop-overflow warning

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Orlando Arias [ Upstream commit deba804c90642c8ed0f15ac1083663976d578f54 ] Greetings, GCC 7 introduced the -Wstringop-overflow flag to detect buffer overflows in

[PATCH 4.11 043/115] sparc: Fix -Wstringop-overflow warning

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Orlando Arias [ Upstream commit deba804c90642c8ed0f15ac1083663976d578f54 ] Greetings, GCC 7 introduced the -Wstringop-overflow flag to detect buffer overflows in calls to string handling

[PATCH 4.11 024/115] bridge: netlink: check vlan_default_pvid range

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Jungel [ Upstream commit a285860211bf257b0e6d522dac6006794be348af ] Currently it is allowed to set the default pvid of a bridge to a value above VLAN_VID_MASK

[PATCH 4.11 024/115] bridge: netlink: check vlan_default_pvid range

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Jungel [ Upstream commit a285860211bf257b0e6d522dac6006794be348af ] Currently it is allowed to set the default pvid of a bridge to a value above VLAN_VID_MASK (0xfff). This patch adds

[PATCH 4.11 023/115] ipv6: Check ip6_find_1stfragopt() return value properly.

4.11-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 7dd7eb9513bd02184d45f000ab69d78cb1fa1531 ] Do not use unsigned variables to see if it returns a negative error or not. Fixes:

[PATCH 4.11 023/115] ipv6: Check ip6_find_1stfragopt() return value properly.

4.11-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 7dd7eb9513bd02184d45f000ab69d78cb1fa1531 ] Do not use unsigned variables to see if it returns a negative error or not. Fixes: 2423496af35d ("ipv6:

[PATCH 4.11 046/115] powerpc: Fix booting P9 hash with CONFIG_PPC_RADIX_MMU=N

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit d957fb4d173647640a2b83e7c7e56a580e7fc7e7 upstream. Currently if you disable CONFIG_PPC_RADIX_MMU you'll crash on boot on a P9. This is because we

[PATCH 4.11 046/115] powerpc: Fix booting P9 hash with CONFIG_PPC_RADIX_MMU=N

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit d957fb4d173647640a2b83e7c7e56a580e7fc7e7 upstream. Currently if you disable CONFIG_PPC_RADIX_MMU you'll crash on boot on a P9. This is because we still set

Re: [PATCH v3 19/27] thunderbolt: Add new Thunderbolt PCI IDs

On Mon, Jun 05, 2017 at 03:50:24PM +, mario.limoncie...@dell.com wrote: > And presumably that's mostly for debugging purposes and will lead > to additional quirks to get "automatic" to do the right thing on those > machines that's it's found to be needed or more beneficial. I would say that

Re: [PATCH v3 19/27] thunderbolt: Add new Thunderbolt PCI IDs

On Mon, Jun 05, 2017 at 03:50:24PM +, mario.limoncie...@dell.com wrote: > And presumably that's mostly for debugging purposes and will lead > to additional quirks to get "automatic" to do the right thing on those > machines that's it's found to be needed or more beneficial. I would say that

[PATCH 4.11 034/115] geneve: fix fill_info when using collect_metadata

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Garver [ Upstream commit 11387fe4a98f75d1f4cdb3efe3b42b19205c9df5 ] Since 9b4437a5b870 ("geneve: Unify LWT and netdev handling.") fill_info does not return

[PATCH 4.11 034/115] geneve: fix fill_info when using collect_metadata

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Garver [ Upstream commit 11387fe4a98f75d1f4cdb3efe3b42b19205c9df5 ] Since 9b4437a5b870 ("geneve: Unify LWT and netdev handling.") fill_info does not return UDP_ZERO_CSUM6_RX when using

Re: [PATCH v3 1/5] acpi, nfit: Switch to use new generic UUID API

On Mon, Jun 5, 2017 at 9:40 AM, Andy Shevchenko wrote: > There are new types and helpers that are supposed to be used in new code. > > As a preparation to get rid of legacy types and API functions do > the conversion here. > > Reviewed-by: Dan Williams

Re: [PATCH v3 1/5] acpi, nfit: Switch to use new generic UUID API

On Mon, Jun 5, 2017 at 9:40 AM, Andy Shevchenko wrote: > There are new types and helpers that are supposed to be used in new code. > > As a preparation to get rid of legacy types and API functions do > the conversion here. > > Reviewed-by: Dan Williams > Signed-off-by: Andy Shevchenko > --- >

[PATCH 4.11 035/115] tcp: avoid fastopen API to be used on AF_UNSPEC

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Wei Wang [ Upstream commit ba615f675281d76fd19aa03558777f81fb6b6084 ] Fastopen API should be used to perform fastopen operations on the TCP socket. It does not make sense

[PATCH 4.11 058/115] Revert "ACPI / button: Change default behavior to lid_init_state=open"

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 878d8db039daac0938238e9a40a5bd6e50ee3c9b upstream. Revert commit 77e9a4aa9de1 (ACPI / button: Change default behavior to

[PATCH 4.11 035/115] tcp: avoid fastopen API to be used on AF_UNSPEC

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Wei Wang [ Upstream commit ba615f675281d76fd19aa03558777f81fb6b6084 ] Fastopen API should be used to perform fastopen operations on the TCP socket. It does not make sense to use fastopen API

[PATCH 4.11 058/115] Revert "ACPI / button: Change default behavior to lid_init_state=open"

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 878d8db039daac0938238e9a40a5bd6e50ee3c9b upstream. Revert commit 77e9a4aa9de1 (ACPI / button: Change default behavior to lid_init_state=open) which changed the

[PATCH 4.11 036/115] sctp: fix ICMP processing if skb is non-linear

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Davide Caratti [ Upstream commit 804ec7ebe8ea003999ca8d1bfc499edc6a9e07df ] sometimes ICMP replies to INIT chunks are ignored by the client, even if the encapsulated

[PATCH 4.11 036/115] sctp: fix ICMP processing if skb is non-linear

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Davide Caratti [ Upstream commit 804ec7ebe8ea003999ca8d1bfc499edc6a9e07df ] sometimes ICMP replies to INIT chunks are ignored by the client, even if the encapsulated SCTP headers match an

[PATCH 4.11 038/115] ipv4: add reference counting to metrics

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 3fb07daff8e99243366a081e5129560734de4ada ] Andrey Konovalov reported crashes in ipv4_mtu() I could reproduce the issue with KASAN

Re: [PATCH v3 2/2] ARM: dts: Add the ethernet and ethernet PHY to the cygnus core DT.

On 04/28/2017 03:22 PM, Eric Anholt wrote: > Cygnus has a single amac controller connected to the B53 switch with 2 > PHYs. On the BCM911360_EP platform, those two PHYs are connected to > the external ethernet jacks. > > v2: Call the node "switch", just call the ports "port" (suggestions by >

[PATCH 4.11 038/115] ipv4: add reference counting to metrics

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 3fb07daff8e99243366a081e5129560734de4ada ] Andrey Konovalov reported crashes in ipv4_mtu() I could reproduce the issue with KASAN kernels, between

Re: [PATCH v3 2/2] ARM: dts: Add the ethernet and ethernet PHY to the cygnus core DT.

On 04/28/2017 03:22 PM, Eric Anholt wrote: > Cygnus has a single amac controller connected to the B53 switch with 2 > PHYs. On the BCM911360_EP platform, those two PHYs are connected to > the external ethernet jacks. > > v2: Call the node "switch", just call the ports "port" (suggestions by >

<    5   6   7   8   9   10   11   12   13   14   >