[PATCH 3.18 03/21] cfg80211: further limit wiphy names to 64 bytes

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 814596495dd2b9d4aab92d8f89cf19060d25d2ea upstream. wiphy names were recently limited to 128 bytes by commit a7cfebcb7594 ("cfg80211: limit wiphy names to 128 bytes"). As

[PATCH 3.18 04/21] tcp: avoid integer overflows in tcp_rcv_space_adjust()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 607065bad9931e72207b0cac365d7d4abc06bd99 upstream. When using large tcp_rmem[2] values (I did tests with 500 MB), I noticed overflows while computing rcvwin. Lets fix

[PATCH 3.18 05/21] MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit c7e814628df65f424fe197dde73bfc67e4a244d7 upstream. Use 64-bit accesses for 64-bit floating-point general registers with PTRACE_PEEKUSR, removing the truncation of

[PATCH 3.18 08/21] mm: fix the NULL mapping case in __isolate_lru_page()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hugh Dickins commit 145e1a71e090575c74969e3daa8136d1e5b99fc8 upstream. George Boole would have noticed a slight error in 4.16 commit 69d763fc6d3a ("mm: pin address_space before dereferencing

[PATCH 3.18 00/21] 3.18.113-stable review

This is the start of the stable review cycle for the 3.18.113 release. There are 21 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 Thu Jun 14 16:48:15 UTC 2018. Anything

[PATCH 3.18 09/21] mmap: introduce sane default mmap limits

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit be83bbf806822b1b89e0a0f23cd87cddc409e429 upstream. The internal VM "mmap()" interfaces are based on the mmap target doing everything using page indexes rather than byte

[PATCH 3.18 09/21] mmap: introduce sane default mmap limits

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit be83bbf806822b1b89e0a0f23cd87cddc409e429 upstream. The internal VM "mmap()" interfaces are based on the mmap target doing everything using page indexes rather than byte

[PATCH 3.18 05/21] MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit c7e814628df65f424fe197dde73bfc67e4a244d7 upstream. Use 64-bit accesses for 64-bit floating-point general registers with PTRACE_PEEKUSR, removing the truncation of

[PATCH 3.18 08/21] mm: fix the NULL mapping case in __isolate_lru_page()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hugh Dickins commit 145e1a71e090575c74969e3daa8136d1e5b99fc8 upstream. George Boole would have noticed a slight error in 4.16 commit 69d763fc6d3a ("mm: pin address_space before dereferencing

[PATCH 3.18 00/21] 3.18.113-stable review

This is the start of the stable review cycle for the 3.18.113 release. There are 21 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 Thu Jun 14 16:48:15 UTC 2018. Anything

[PATCH 3.18 19/21] net/mlx4: Fix irq-unsafe spinlock usage

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d546b67cda015fb92bfee93d5dc0ceadb91deaee ] spin_lock/unlock was used instead of spin_un/lock_irq in a procedure used in process space, on a spinlock which

[PATCH 3.18 19/21] net/mlx4: Fix irq-unsafe spinlock usage

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d546b67cda015fb92bfee93d5dc0ceadb91deaee ] spin_lock/unlock was used instead of spin_un/lock_irq in a procedure used in process space, on a spinlock which

[PATCH 3.18 12/21] bnx2x: use the right constant

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall [ Upstream commit dd612f18a49b63af8b3a5f572d999bdb197385bc ] Nearby code that also tests port suggests that the P0 constant should be used when port is zero. The semantic match

[PATCH 3.18 12/21] bnx2x: use the right constant

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall [ Upstream commit dd612f18a49b63af8b3a5f572d999bdb197385bc ] Nearby code that also tests port suggests that the P0 constant should be used when port is zero. The semantic match

[PATCH 3.18 17/21] net/packet: refine check for priv area size

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit eb73190f4fbeedf762394e92d6a4ec9ace684c88 ] syzbot was able to trick af_packet again [1] Various commits tried to address the problem in the past, but failed to

[PATCH 3.18 17/21] net/packet: refine check for priv area size

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit eb73190f4fbeedf762394e92d6a4ec9ace684c88 ] syzbot was able to trick af_packet again [1] Various commits tried to address the problem in the past, but failed to

[PATCH 3.18 15/21] ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 848235edb5c93ed086700584c8ff64f6d7fc778d ] Currently, raw6_sk(sk)->ip6mr_table is set unconditionally during ip6_mroute_setsockopt(MRT6_TABLE). A subsequent

[PATCH 3.18 15/21] ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 848235edb5c93ed086700584c8ff64f6d7fc778d ] Currently, raw6_sk(sk)->ip6mr_table is set unconditionally during ip6_mroute_setsockopt(MRT6_TABLE). A subsequent

[PATCH 3.18 11/21] drm: set FMODE_UNSIGNED_OFFSET for drm files

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie commit 76ef6b28ea4f81c3d511866a9b31392caa833126 upstream. Since we have the ttm and gem vma managers using a subset of the file address space for objects, and these start at

[PATCH 3.18 11/21] drm: set FMODE_UNSIGNED_OFFSET for drm files

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie commit 76ef6b28ea4f81c3d511866a9b31392caa833126 upstream. Since we have the ttm and gem vma managers using a subset of the file address space for objects, and these start at

[PATCH 4.4 24/24] net: metrics: add proper netlink validation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 5b5e7a0de2bbf2a1afcd9f49e940010e9fb80d53 ] Before using nla_get_u32(), better make sure the attribute is of the proper size. Code recently was changed, but bug

[PATCH 4.4 24/24] net: metrics: add proper netlink validation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 5b5e7a0de2bbf2a1afcd9f49e940010e9fb80d53 ] Before using nla_get_u32(), better make sure the attribute is of the proper size. Code recently was changed, but bug

[PATCH 4.4 23/24] net: phy: broadcom: Fix bcm_write_exp()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit 79fb218d97980d4fee9a64f4c8ff05289364ba25 ] On newer PHYs, we need to select the expansion register to write with setting bits [11:8] to 0xf. This was done

[PATCH 4.4 23/24] net: phy: broadcom: Fix bcm_write_exp()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit 79fb218d97980d4fee9a64f4c8ff05289364ba25 ] On newer PHYs, we need to select the expansion register to write with setting bits [11:8] to 0xf. This was done

[PATCH 4.4 20/24] net/mlx4: Fix irq-unsafe spinlock usage

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d546b67cda015fb92bfee93d5dc0ceadb91deaee ] spin_lock/unlock was used instead of spin_un/lock_irq in a procedure used in process space, on a spinlock which

[PATCH 4.4 06/24] xfs: fix incorrect log_flushed on fsync

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Amir Goldstein commit 47c7d0b19502583120c3f396c7559e7a77288a68 upstream. When calling into _xfs_log_force{,_lsn}() with a pointer to log_flushed variable, log_flushed will be set to 1 if: 1.

[PATCH 4.4 06/24] xfs: fix incorrect log_flushed on fsync

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Amir Goldstein commit 47c7d0b19502583120c3f396c7559e7a77288a68 upstream. When calling into _xfs_log_force{,_lsn}() with a pointer to log_flushed variable, log_flushed will be set to 1 if: 1.

[PATCH 4.4 20/24] net/mlx4: Fix irq-unsafe spinlock usage

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d546b67cda015fb92bfee93d5dc0ceadb91deaee ] spin_lock/unlock was used instead of spin_un/lock_irq in a procedure used in process space, on a spinlock which

[PATCH 4.4 00/24] 4.4.137-stable review

This is the start of the stable review cycle for the 4.4.137 release. There are 24 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 Thu Jun 14 16:48:07 UTC 2018. Anything

[PATCH 4.4 11/24] enic: set DMA mask to 47 bit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Govindarajulu Varadarajan [ Upstream commit 322eaa06d55ebc1402a4a8d140945cff536638b4 ] In commit 624dbf55a359b ("driver/net: enic: Try DMA 64 first, then failover to DMA") DMA mask was changed

[PATCH 4.4 00/24] 4.4.137-stable review

This is the start of the stable review cycle for the 4.4.137 release. There are 24 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 Thu Jun 14 16:48:07 UTC 2018. Anything

[PATCH 4.4 11/24] enic: set DMA mask to 47 bit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Govindarajulu Varadarajan [ Upstream commit 322eaa06d55ebc1402a4a8d140945cff536638b4 ] In commit 624dbf55a359b ("driver/net: enic: Try DMA 64 first, then failover to DMA") DMA mask was changed

[PATCH 4.4 10/24] dccp: dont free ccid2_hc_tx_sock struct in dccp_disconnect()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 2677d20677314101293e6da0094ede7b5526d2b1 ] Syzbot reported the use-after-free in timer_is_static_object() [1]. This can happen because the structure for the

[PATCH 4.9 19/31] qed: Fix mask for physical address in ILT entry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shahed Shaikh [ Upstream commit fdd13dd350dda1826579eb5c333d76b14513b812 ] ILT entry requires 12 bit right shifted physical address. Existing mask for ILT entry of physical address i.e.

[PATCH 4.9 20/31] sctp: not allow transport timeout value less than HZ/5 for hb_timer

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 1d88ba1ebb2763aa86172cd7ca05dedbeccc0d35 ] syzbot reported a rcu_sched self-detected stall on CPU which is caused by too small value set on rto_min with SCTP_RTOINFO

[PATCH 4.9 02/31] tpm: self test failure should not cause suspend to fail

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chris Chiu commit 0803d7befa15cab5717d667a97a66214d2a4c083 upstream. The Acer Acer Veriton X4110G has a TPM device detected as: tpm_tis 00:0b: 1.2 TPM (device-id 0xFE, rev-id 71) After the

[PATCH 4.4 10/24] dccp: dont free ccid2_hc_tx_sock struct in dccp_disconnect()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 2677d20677314101293e6da0094ede7b5526d2b1 ] Syzbot reported the use-after-free in timer_is_static_object() [1]. This can happen because the structure for the

[PATCH 4.9 19/31] qed: Fix mask for physical address in ILT entry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shahed Shaikh [ Upstream commit fdd13dd350dda1826579eb5c333d76b14513b812 ] ILT entry requires 12 bit right shifted physical address. Existing mask for ILT entry of physical address i.e.

[PATCH 4.9 20/31] sctp: not allow transport timeout value less than HZ/5 for hb_timer

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 1d88ba1ebb2763aa86172cd7ca05dedbeccc0d35 ] syzbot reported a rcu_sched self-detected stall on CPU which is caused by too small value set on rto_min with SCTP_RTOINFO

[PATCH 4.9 02/31] tpm: self test failure should not cause suspend to fail

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chris Chiu commit 0803d7befa15cab5717d667a97a66214d2a4c083 upstream. The Acer Acer Veriton X4110G has a TPM device detected as: tpm_tis 00:0b: 1.2 TPM (device-id 0xFE, rev-id 71) After the

[PATCH 4.4 15/24] netdev-FAQ: clarify DaveMs position for stable backports

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 75d4e704fa8d2cf33ff295e5b441317603d7f9fd ] Per discussion with David at netconf 2018, let's clarify DaveM's position of handling stable backports in netdev-FAQ.

[PATCH 4.4 15/24] netdev-FAQ: clarify DaveMs position for stable backports

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 75d4e704fa8d2cf33ff295e5b441317603d7f9fd ] Per discussion with David at netconf 2018, let's clarify DaveM's position of handling stable backports in netdev-FAQ.

[PATCH 4.9 24/31] net/mlx4: Fix irq-unsafe spinlock usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d546b67cda015fb92bfee93d5dc0ceadb91deaee ] spin_lock/unlock was used instead of spin_un/lock_irq in a procedure used in process space, on a spinlock which

[PATCH 4.9 25/31] rtnetlink: validate attributes in do_setlink()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 644c7eebbfd59e72982d11ec6cc7d39af12450ae ] It seems that rtnl_group_changelink() can call do_setlink while a prior call to validate_linkmsg(dev = NULL, ...)

[PATCH 4.9 23/31] vrf: check the original netdevice for generating redirect

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Suryaputra [ Upstream commit 2f17becfbea5e9a0529b51da7345783e96e69516 ] Use the right device to determine if redirect should be sent especially when using vrf. Same as well as when

[PATCH 4.9 22/31] vhost: synchronize IOTLB message with dev cleanup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 1b15ad683ab42a203f98b67045b40720e99d0e9a ] DaeRyong Jeong reports a race between vhost_dev_cleanup() and vhost_process_iotlb_msg(): Thread interleaving: CPU0

[PATCH 4.9 24/31] net/mlx4: Fix irq-unsafe spinlock usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d546b67cda015fb92bfee93d5dc0ceadb91deaee ] spin_lock/unlock was used instead of spin_un/lock_irq in a procedure used in process space, on a spinlock which

[PATCH 4.9 25/31] rtnetlink: validate attributes in do_setlink()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 644c7eebbfd59e72982d11ec6cc7d39af12450ae ] It seems that rtnl_group_changelink() can call do_setlink while a prior call to validate_linkmsg(dev = NULL, ...)

[PATCH 4.9 23/31] vrf: check the original netdevice for generating redirect

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Suryaputra [ Upstream commit 2f17becfbea5e9a0529b51da7345783e96e69516 ] Use the right device to determine if redirect should be sent especially when using vrf. Same as well as when

[PATCH 4.9 22/31] vhost: synchronize IOTLB message with dev cleanup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 1b15ad683ab42a203f98b67045b40720e99d0e9a ] DaeRyong Jeong reports a race between vhost_dev_cleanup() and vhost_process_iotlb_msg(): Thread interleaving: CPU0

[PATCH 4.9 28/31] KVM: VMX: Expose SSBD properly to guests, 4.9 supplement

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings Fix an additional misuse of X86_FEATURE_SSBD in guest_cpuid_has_spec_ctrl(). This function was introduced in the backport of SSBD support to 4.9 and is not present upstream, so

[PATCH 4.9 30/31] objtool: Fix gcov check for older versions of GCC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 867ac9d737094e46a6c33213f16dd1ec9e8bd5d5 upstream. Objtool tries to silence 'unreachable instruction' warnings when it detects gcov is enabled, because gcov produces a

[PATCH 4.9 28/31] KVM: VMX: Expose SSBD properly to guests, 4.9 supplement

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings Fix an additional misuse of X86_FEATURE_SSBD in guest_cpuid_has_spec_ctrl(). This function was introduced in the backport of SSBD support to 4.9 and is not present upstream, so

[PATCH 4.9 30/31] objtool: Fix gcov check for older versions of GCC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 867ac9d737094e46a6c33213f16dd1ec9e8bd5d5 upstream. Objtool tries to silence 'unreachable instruction' warnings when it detects gcov is enabled, because gcov produces a

[PATCH 4.9 03/31] mmap: introduce sane default mmap limits

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit be83bbf806822b1b89e0a0f23cd87cddc409e429 upstream. The internal VM "mmap()" interfaces are based on the mmap target doing everything using page indexes rather than byte

[PATCH 4.9 04/31] mmap: relax file size limit for regular files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 423913ad4ae5b3e8fb8983f70969fb522261ba26 upstream. Commit be83bbf80682 ("mmap: introduce sane default mmap limits") was introduced to catch problems in various ad-hoc

[PATCH 4.9 29/31] dm bufio: avoid false-positive Wmaybe-uninitialized warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 590347e4000356f55eb10b03ced2686bd74dab40 upstream. gcc-6.3 and earlier show a new warning after a seemingly unrelated change to the arm64 PAGE_KERNEL definition: In file

[PATCH 4.9 04/31] mmap: relax file size limit for regular files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 423913ad4ae5b3e8fb8983f70969fb522261ba26 upstream. Commit be83bbf80682 ("mmap: introduce sane default mmap limits") was introduced to catch problems in various ad-hoc

[PATCH 4.9 29/31] dm bufio: avoid false-positive Wmaybe-uninitialized warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 590347e4000356f55eb10b03ced2686bd74dab40 upstream. gcc-6.3 and earlier show a new warning after a seemingly unrelated change to the arm64 PAGE_KERNEL definition: In file

[PATCH 4.9 03/31] mmap: introduce sane default mmap limits

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit be83bbf806822b1b89e0a0f23cd87cddc409e429 upstream. The internal VM "mmap()" interfaces are based on the mmap target doing everything using page indexes rather than byte

[PATCH 4.9 08/31] bnx2x: use the right constant

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall [ Upstream commit dd612f18a49b63af8b3a5f572d999bdb197385bc ] Nearby code that also tests port suggests that the P0 constant should be used when port is zero. The semantic match

[PATCH 4.9 08/31] bnx2x: use the right constant

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall [ Upstream commit dd612f18a49b63af8b3a5f572d999bdb197385bc ] Nearby code that also tests port suggests that the P0 constant should be used when port is zero. The semantic match

[PATCH 4.9 09/31] dccp: dont free ccid2_hc_tx_sock struct in dccp_disconnect()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 2677d20677314101293e6da0094ede7b5526d2b1 ] Syzbot reported the use-after-free in timer_is_static_object() [1]. This can happen because the structure for the

[PATCH] staging:iio:accel:adis16203: sign extend function rather code duplication

Use sign_extend32 kernel function instead of code duplication. This function is also safe for 16 bits. Signed-off-by: Karim Eshapa --- drivers/staging/iio/accel/adis16203.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/staging/iio/accel/adis16203.c

[PATCH 4.9 09/31] dccp: dont free ccid2_hc_tx_sock struct in dccp_disconnect()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 2677d20677314101293e6da0094ede7b5526d2b1 ] Syzbot reported the use-after-free in timer_is_static_object() [1]. This can happen because the structure for the

[PATCH] staging:iio:accel:adis16203: sign extend function rather code duplication

Use sign_extend32 kernel function instead of code duplication. This function is also safe for 16 bits. Signed-off-by: Karim Eshapa --- drivers/staging/iio/accel/adis16203.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/staging/iio/accel/adis16203.c

[PATCH 4.9 05/31] btrfs: define SUPER_FLAG_METADUMP_V2

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anand Jain commit e2731e55884f2138a252b0a3d7b24d57e49c3c59 upstream. btrfs-progs uses super flag bit BTRFS_SUPER_FLAG_METADUMP_V2 (1ULL << 34). So just define that in kernel so that we know

[PATCH 4.9 07/31] drm: set FMODE_UNSIGNED_OFFSET for drm files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie commit 76ef6b28ea4f81c3d511866a9b31392caa833126 upstream. Since we have the ttm and gem vma managers using a subset of the file address space for objects, and these start at

[PATCH 4.9 05/31] btrfs: define SUPER_FLAG_METADUMP_V2

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anand Jain commit e2731e55884f2138a252b0a3d7b24d57e49c3c59 upstream. btrfs-progs uses super flag bit BTRFS_SUPER_FLAG_METADUMP_V2 (1ULL << 34). So just define that in kernel so that we know

[PATCH 4.9 07/31] drm: set FMODE_UNSIGNED_OFFSET for drm files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie commit 76ef6b28ea4f81c3d511866a9b31392caa833126 upstream. Since we have the ttm and gem vma managers using a subset of the file address space for objects, and these start at

[PATCH 4.9 27/31] net: metrics: add proper netlink validation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 5b5e7a0de2bbf2a1afcd9f49e940010e9fb80d53 ] Before using nla_get_u32(), better make sure the attribute is of the proper size. Code recently was changed, but bug

[PATCH 4.9 26/31] net: phy: broadcom: Fix bcm_write_exp()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit 79fb218d97980d4fee9a64f4c8ff05289364ba25 ] On newer PHYs, we need to select the expansion register to write with setting bits [11:8] to 0xf. This was done

[PATCH 4.9 26/31] net: phy: broadcom: Fix bcm_write_exp()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit 79fb218d97980d4fee9a64f4c8ff05289364ba25 ] On newer PHYs, we need to select the expansion register to write with setting bits [11:8] to 0xf. This was done

[PATCH 4.9 27/31] net: metrics: add proper netlink validation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 5b5e7a0de2bbf2a1afcd9f49e940010e9fb80d53 ] Before using nla_get_u32(), better make sure the attribute is of the proper size. Code recently was changed, but bug

Re: [PATCH 0/3] sched/swait: Convert to full exclusive mode

" On Tue, Jun 12, 2018 at 1:39 AM Peter Zijlstra wrote: > > As mentioned by Linus, swait is exclusive mode and had better behave like it > and be named like it. Ack on the patches. I do note how quilt emails are really hard to read, because that: Content-Disposition: inline makes gmail

Re: [PATCH 0/3] sched/swait: Convert to full exclusive mode

" On Tue, Jun 12, 2018 at 1:39 AM Peter Zijlstra wrote: > > As mentioned by Linus, swait is exclusive mode and had better behave like it > and be named like it. Ack on the patches. I do note how quilt emails are really hard to read, because that: Content-Disposition: inline makes gmail

[PATCH 4.9 21/31] team: use netdev_features_t instead of u32

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 25ea66544bfd1d9df1b7e1502f8717e85fa1e6e6 ] This code was introduced in 2011 around the same time that we made netdev_features_t a u64 type. These days a u32 is

[PATCH 4.9 21/31] team: use netdev_features_t instead of u32

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 25ea66544bfd1d9df1b7e1502f8717e85fa1e6e6 ] This code was introduced in 2011 around the same time that we made netdev_features_t a u64 type. These days a u32 is

[PATCH 4.9 18/31] packet: fix reserve calculation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 9aad13b087ab0a588cd68259de618f100053360e ] Commit b84bbaf7a6c8 ("packet: in packet_snd start writing at link layer allocation") ensures that packet_snd

[PATCH 4.9 18/31] packet: fix reserve calculation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 9aad13b087ab0a588cd68259de618f100053360e ] Commit b84bbaf7a6c8 ("packet: in packet_snd start writing at link layer allocation") ensures that packet_snd

[PATCH 4.9 15/31] netdev-FAQ: clarify DaveMs position for stable backports

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 75d4e704fa8d2cf33ff295e5b441317603d7f9fd ] Per discussion with David at netconf 2018, let's clarify DaveM's position of handling stable backports in netdev-FAQ.

[PATCH 4.9 15/31] netdev-FAQ: clarify DaveMs position for stable backports

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 75d4e704fa8d2cf33ff295e5b441317603d7f9fd ] Per discussion with David at netconf 2018, let's clarify DaveM's position of handling stable backports in netdev-FAQ.

[PATCH 4.9 13/31] isdn: eicon: fix a missing-check bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit 6009d1fe6ba3bb2dab55921da60465329cc1cd89 ] In divasmain.c, the function divas_write() firstly invokes the function diva_xdi_open_adapter() to open the adapter

[PATCH 4.9 00/31] 4.9.108-stable review

This is the start of the stable review cycle for the 4.9.108 release. There are 31 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 Thu Jun 14 16:46:09 UTC 2018. Anything

[PATCH 4.9 01/31] tpm: do not suspend/resume if power stays on

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Enric Balletbo i Serra commit b5d0ebc99bf5d0801a5ecbe958caa3d68b8eaee8 upstream. The suspend/resume behavior of the TPM can be controlled by setting "powered-while-suspended" in the DTS. This

[PATCH 4.9 11/31] ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 848235edb5c93ed086700584c8ff64f6d7fc778d ] Currently, raw6_sk(sk)->ip6mr_table is set unconditionally during ip6_mroute_setsockopt(MRT6_TABLE). A subsequent

[PATCH 4.9 13/31] isdn: eicon: fix a missing-check bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit 6009d1fe6ba3bb2dab55921da60465329cc1cd89 ] In divasmain.c, the function divas_write() firstly invokes the function diva_xdi_open_adapter() to open the adapter

[PATCH 4.9 00/31] 4.9.108-stable review

This is the start of the stable review cycle for the 4.9.108 release. There are 31 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 Thu Jun 14 16:46:09 UTC 2018. Anything

[PATCH 4.9 01/31] tpm: do not suspend/resume if power stays on

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Enric Balletbo i Serra commit b5d0ebc99bf5d0801a5ecbe958caa3d68b8eaee8 upstream. The suspend/resume behavior of the TPM can be controlled by setting "powered-while-suspended" in the DTS. This

[PATCH 4.9 11/31] ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 848235edb5c93ed086700584c8ff64f6d7fc778d ] Currently, raw6_sk(sk)->ip6mr_table is set unconditionally during ip6_mroute_setsockopt(MRT6_TABLE). A subsequent

Re: [PATCH] irqchip/gic-v3: do not access GICR_WAKER if its secured register.

On Tue, 12 Jun 2018 15:55:16 +0100, Srinivas Kandagatla wrote: > > GICR_WAKER can be a secured register, check this before accessing it > as its done in power management code. NAK. >From the GICv3 spec: * When GICD_CTLR.DS==1, this register is always accessible. * When GICD_CTLR.DS==0, this

Re: [PATCH] irqchip/gic-v3: do not access GICR_WAKER if its secured register.

On Tue, 12 Jun 2018 15:55:16 +0100, Srinivas Kandagatla wrote: > > GICR_WAKER can be a secured register, check this before accessing it > as its done in power management code. NAK. >From the GICv3 spec: * When GICD_CTLR.DS==1, this register is always accessible. * When GICD_CTLR.DS==0, this

Re: [PATCH v4 2/7] clk: at91: add I2S clock mux driver

Quoting Codrin Ciubotariu (2018-06-04 01:20:29) > On 31.05.2018 18:26, Stephen Boyd wrote: > > Quoting Codrin Ciubotariu (2018-05-25 05:34:23) > > > >> + .get_parent = clk_i2s_mux_get_parent, > >> + .set_parent = clk_i2s_mux_set_parent, > >> + .determine_rate =

Re: [PATCH v4 2/7] clk: at91: add I2S clock mux driver

Quoting Codrin Ciubotariu (2018-06-04 01:20:29) > On 31.05.2018 18:26, Stephen Boyd wrote: > > Quoting Codrin Ciubotariu (2018-05-25 05:34:23) > > > >> + .get_parent = clk_i2s_mux_get_parent, > >> + .set_parent = clk_i2s_mux_set_parent, > >> + .determine_rate =

[PATCH v2 3/4] smpboot: Remove cpumask from the API

Now that the sole use of the whole smpboot_*cpumask() API is gone, remove it. Suggested-by: Oleg Nesterov Signed-off-by: Peter Zijlstra (Intel) --- include/linux/smpboot.h | 15 - kernel/smpboot.c| 54 2 files changed, 6

Re: Restartable Sequences system call merged into Linux

- On Jun 12, 2018, at 9:11 AM, Florian Weimer fwei...@redhat.com wrote: > On 06/11/2018 10:04 PM, Mathieu Desnoyers wrote: >> - On Jun 11, 2018, at 3:55 PM, Florian Weimer fwei...@redhat.com wrote: >> >>> On 06/11/2018 09:49 PM, Mathieu Desnoyers wrote: It should be noted that there

[PATCH v2 4/4] kthread: Simplify kthread_park() completion

Oleg explains the reason we could hit park+park is that smpboot_update_cpumask_percpu_thread()'s for_each_cpu_and(cpu, , cpu_online_mask) smpboot_park_kthread(); turns into: for ((cpu) = 0; (cpu) < 1; (cpu)++, (void)mask, (void)and) smpboot_park_kthread(); on UP, ignoring

[PATCH v2 1/4] kthread, sched: Fix kthread_parkme() (again...)

Gaurav reports that commit: 85f1abe0019f ("kthread, sched/wait: Fix kthread_parkme() completion issue") isn't working for him. Because of the following race: > controller Thread CPUHP Thread > takedown_cpu > kthread_park > kthread_parkme > Set KTHREAD_SHOULD_PARK

[PATCH v2 0/4] kthread/smpboot: More fixes...

Changes since last time: - folded the smp_call_on_cpu() fix - re-add missing softlockup_threads_initialized check - rewrote changelog for completion revert

[PATCH v2 2/4] watchdog/softlockup: Replace "watchdog/%u" threads with cpu_stop_work

Oleg suggested to replace the "watchdog/%u" threads with cpu_stop_work. That removes one thread per cpu while at the same time fixes softlockup vs SCHED_DEADLINE. But more importantly, it does away with the single smpboot_update_cpumask_percpu_thread() user, which allows cleanups/shrinkage of the

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