Re: [PATCH] staging: lustre: o2iblnd: fix race at kiblnd_connect_peer

Please ignore this patch. Turns out it depends on a series which has not been submitted yet. I’ll resend this one once all of those are done. Doug > On Mar 9, 2018, at 3:29 PM, Doug Oucharek wrote: > > cmid will be destroyed at OFED if kiblnd_cm_callback return error. > if

Re: [PATCH] staging: lustre: o2iblnd: fix race at kiblnd_connect_peer

Please ignore this patch. Turns out it depends on a series which has not been submitted yet. I’ll resend this one once all of those are done. Doug > On Mar 9, 2018, at 3:29 PM, Doug Oucharek wrote: > > cmid will be destroyed at OFED if kiblnd_cm_callback return error. > if error happen

[PATCH] x86/microcode/AMD: check microcode file sanity before loading it

Currently, it is very easy to make the AMD microcode update driver crash or spin on a malformed microcode file since it does very little consistency checking on data loaded from such file. This commit introduces various checks, mostly on length-type fields, so all corrupted microcode files are

[PATCH 4.9 44/65] net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 08f5138512180a479ce6b9d23b825c9f4cd3be77 ] This condition wasn't adjusted when PHY_IGNORE_INTERRUPT (-2) was added long ago. In case of

[PATCH 4.9 44/65] net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 08f5138512180a479ce6b9d23b825c9f4cd3be77 ] This condition wasn't adjusted when PHY_IGNORE_INTERRUPT (-2) was added long ago. In case of PHY_IGNORE_INTERRUPT

[PATCH] x86/microcode/AMD: check microcode file sanity before loading it

Currently, it is very easy to make the AMD microcode update driver crash or spin on a malformed microcode file since it does very little consistency checking on data loaded from such file. This commit introduces various checks, mostly on length-type fields, so all corrupted microcode files are

[PATCH 4.9 24/65] PCI/ASPM: Deal with missing root ports in link state handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit ee8bdfb6568d86bb93f55f8d99c4c643e77304ee upstream. Even though it is unconventional, some PCIe host implementations omit the root ports

[PATCH 4.9 45/65] tcp: Honor the eor bit in tcp_mtu_probe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Lesokhin [ Upstream commit 808cf9e38cd7923036a99f459ccc8cf2955e47af ] Avoid SKB coalescing if eor bit is set in one of the relevant SKBs. Fixes: c134ecb87817 ("tcp:

[PATCH 4.9 24/65] PCI/ASPM: Deal with missing root ports in link state handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit ee8bdfb6568d86bb93f55f8d99c4c643e77304ee upstream. Even though it is unconventional, some PCIe host implementations omit the root ports entirely, and simply consist of a

[PATCH 4.9 45/65] tcp: Honor the eor bit in tcp_mtu_probe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Lesokhin [ Upstream commit 808cf9e38cd7923036a99f459ccc8cf2955e47af ] Avoid SKB coalescing if eor bit is set in one of the relevant SKBs. Fixes: c134ecb87817 ("tcp: Make use of MSG_EOR

RE: [PATCH V2 2/3] efi: Introduce efi_rts_workqueue and some infrastructure to invoke all efi_runtime_services()

> > That's true! AFAIK, we don't have any issues handling NMI while in efi_pgd. > > We might have issues only when, we are already in efi_pgd, NMI comes > > along > > Can you trigger this? Or is it something hypothetical? > AFAIK, it's hypothetical. I did try to trigger the issue, but failed

RE: [PATCH V2 2/3] efi: Introduce efi_rts_workqueue and some infrastructure to invoke all efi_runtime_services()

> > That's true! AFAIK, we don't have any issues handling NMI while in efi_pgd. > > We might have issues only when, we are already in efi_pgd, NMI comes > > along > > Can you trigger this? Or is it something hypothetical? > AFAIK, it's hypothetical. I did try to trigger the issue, but failed

[PATCH 4.9 49/65] s390/qeth: fix underestimated count of buffer elements

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit 89271c65edd599207dd982007900506283c90ae3 ] For a memory range/skb where the last byte falls onto a page boundary (ie. 'end' is of the

[PATCH 4.9 49/65] s390/qeth: fix underestimated count of buffer elements

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit 89271c65edd599207dd982007900506283c90ae3 ] For a memory range/skb where the last byte falls onto a page boundary (ie. 'end' is of the form xxx...xxx001), the

[PATCH 4.9 48/65] sctp: fix dst refcnt leak in sctp_v6_get_dst()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 957d761cf91cdbb175ad7d8f5472336a4d54dbf2 ] When going through the bind address list in sctp_v6_get_dst() and the previously found

[PATCH 4.9 50/65] s390/qeth: fix SETIP command handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 1c5b2216fbb973a9410e0b06389740b5c1289171 ] send_control_data() applies some special handling to SETIP v4 IPA commands. But current

[PATCH 4.9 50/65] s390/qeth: fix SETIP command handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 1c5b2216fbb973a9410e0b06389740b5c1289171 ] send_control_data() applies some special handling to SETIP v4 IPA commands. But current code parses *all* command

[PATCH 4.9 48/65] sctp: fix dst refcnt leak in sctp_v6_get_dst()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 957d761cf91cdbb175ad7d8f5472336a4d54dbf2 ] When going through the bind address list in sctp_v6_get_dst() and the previously found address is better ('matchlen

[PATCH 4.9 54/65] s390/qeth: fix IP address lookup for L3 devices

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit c5c48c58b259bb8f0482398370ee539d7a12df3e ] Current code ("qeth_l3_ip_from_hash()") matches a queried address object against objects

[PATCH 4.9 54/65] s390/qeth: fix IP address lookup for L3 devices

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit c5c48c58b259bb8f0482398370ee539d7a12df3e ] Current code ("qeth_l3_ip_from_hash()") matches a queried address object against objects in the IP table by IP

[PATCH 4.9 53/65] s390/qeth: fix double-free on IP add/remove race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 14d066c3531a87f727968cacd85bd95c75f59843 ] Registering an IPv4 address with the HW takes quite a while, so we temporarily drop the

[PATCH 4.9 53/65] s390/qeth: fix double-free on IP add/remove race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 14d066c3531a87f727968cacd85bd95c75f59843 ] Registering an IPv4 address with the HW takes quite a while, so we temporarily drop the ip_htable lock. Any

Re: [PATCH v3] kernel.h: Skip single-eval logic on literals in min()/max()

On Fri, 9 Mar 2018 16:28:51 -0800 Linus Torvalds wrote: > On Fri, Mar 9, 2018 at 4:07 PM, Andrew Morton > wrote: > > > > A brief poke failed to reveal a workaround - gcc-4.4.4 doesn't appear > > to know that __builtin_constant_p(x) is

Re: [PATCH v3] kernel.h: Skip single-eval logic on literals in min()/max()

On Fri, 9 Mar 2018 16:28:51 -0800 Linus Torvalds wrote: > On Fri, Mar 9, 2018 at 4:07 PM, Andrew Morton > wrote: > > > > A brief poke failed to reveal a workaround - gcc-4.4.4 doesn't appear > > to know that __builtin_constant_p(x) is a constant. Or something. > > LOL. > > I suspect it

[PATCH 4.9 52/65] s390/qeth: fix IP removal on offline cards

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 98d823ab1fbdcb13abc25b420f9bb71bade42056 ] If the HW is not reachable, then none of the IPs in qeth's internal table has been

[PATCH 4.9 52/65] s390/qeth: fix IP removal on offline cards

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 98d823ab1fbdcb13abc25b420f9bb71bade42056 ] If the HW is not reachable, then none of the IPs in qeth's internal table has been registered with the HW yet. So

[PATCH 4.9 56/65] sctp: verify size of a new chunk in _sctp_make_chunk()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 07f2c7ab6f8d0a7e7c5764c4e6cc9c52951b9d9c ] When SCTP makes INIT or INIT_ACK packet the total chunk length can exceed

[PATCH 4.9 55/65] s390/qeth: fix IPA command submission race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit d22ffb5a712f9211ffd104c38fc17cbfb1b5e2b0 ] If multiple IPA commands are build & sent out concurrently, fill_ipacmd_header() may

[PATCH 4.9 56/65] sctp: verify size of a new chunk in _sctp_make_chunk()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 07f2c7ab6f8d0a7e7c5764c4e6cc9c52951b9d9c ] When SCTP makes INIT or INIT_ACK packet the total chunk length can exceed SCTP_MAX_CHUNK_LEN which leads to kernel

[PATCH 4.9 55/65] s390/qeth: fix IPA command submission race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit d22ffb5a712f9211ffd104c38fc17cbfb1b5e2b0 ] If multiple IPA commands are build & sent out concurrently, fill_ipacmd_header() may assign a seqno value to a

[PATCH 4.9 25/65] dm io: fix duplicate bio completion due to missing ref count

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit feb7695fe9fb83084aa29de0094774f4c9d4c9fc upstream. If only a subset of the devices associated with multiple regions support a given special operation

[PATCH 4.9 25/65] dm io: fix duplicate bio completion due to missing ref count

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit feb7695fe9fb83084aa29de0094774f4c9d4c9fc upstream. If only a subset of the devices associated with multiple regions support a given special operation (eg. DISCARD) then the

[PATCH 4.9 28/65] x86/mm: Give each mm TLB flush generation a unique ID

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit f39681ed0f48498b80455095376f11535feea332 upstream. This adds two new variables to mmu_context_t: ctx_id and tlb_gen. ctx_id uniquely identifies the

[PATCH 4.9 28/65] x86/mm: Give each mm TLB flush generation a unique ID

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit f39681ed0f48498b80455095376f11535feea332 upstream. This adds two new variables to mmu_context_t: ctx_id and tlb_gen. ctx_id uniquely identifies the mm_struct and will

[PATCH 4.9 26/65] ARM: dts: LogicPD SOM-LV: Fix I2C1 pinmux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Ford commit 84c7efd607e7fb6933920322086db64654f669b2 upstream. The pinmuxing was missing for I2C1 which was causing intermittent issues with the PMIC which is

[PATCH 4.9 27/65] ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Ford commit 74402055a2d3ec998a1ded599e86185a27d9bbf4 upstream. The pinmuxing was missing for I2C1 which was causing intermittent issues with the PMIC which is

[PATCH 4.9 26/65] ARM: dts: LogicPD SOM-LV: Fix I2C1 pinmux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Ford commit 84c7efd607e7fb6933920322086db64654f669b2 upstream. The pinmuxing was missing for I2C1 which was causing intermittent issues with the PMIC which is connected to I2C1. The

[PATCH 4.9 27/65] ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Ford commit 74402055a2d3ec998a1ded599e86185a27d9bbf4 upstream. The pinmuxing was missing for I2C1 which was causing intermittent issues with the PMIC which is connected to I2C1. The

[PATCH 4.9 31/65] netlink: put module reference if dump start fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason A. Donenfeld commit b87b6194be631c94785fe93398651e804ed43e28 upstream. Before, if cb->start() failed, the module reference would never be put, because cb->cb_running is

[PATCH 4.9 31/65] netlink: put module reference if dump start fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason A. Donenfeld commit b87b6194be631c94785fe93398651e804ed43e28 upstream. Before, if cb->start() failed, the module reference would never be put, because cb->cb_running is intentionally

Re: [PATCH v3] kernel.h: Skip single-eval logic on literals in min()/max()

On Fri, Mar 9, 2018 at 4:07 PM, Andrew Morton wrote: > > A brief poke failed to reveal a workaround - gcc-4.4.4 doesn't appear > to know that __builtin_constant_p(x) is a constant. Or something. LOL. I suspect it might be that it wants to evaluate

Re: [PATCH v3] kernel.h: Skip single-eval logic on literals in min()/max()

On Fri, Mar 9, 2018 at 4:07 PM, Andrew Morton wrote: > > A brief poke failed to reveal a workaround - gcc-4.4.4 doesn't appear > to know that __builtin_constant_p(x) is a constant. Or something. LOL. I suspect it might be that it wants to evaluate __builtin_choose_expr() at an earlier stage

[PATCH] staging: lustre: o2iblnd: fix race at kiblnd_connect_peer

cmid will be destroyed at OFED if kiblnd_cm_callback return error. if error happen before the end of kiblnd_connect_peer, it will touch destroyed cmid and fail as (o2iblnd_cb.c:1315:kiblnd_connect_peer()) ASSERTION( cmid->device != ((void *)0) ) failed: Signed-off-by: Alexander Boyko

[PATCH] staging: lustre: o2iblnd: fix race at kiblnd_connect_peer

cmid will be destroyed at OFED if kiblnd_cm_callback return error. if error happen before the end of kiblnd_connect_peer, it will touch destroyed cmid and fail as (o2iblnd_cb.c:1315:kiblnd_connect_peer()) ASSERTION( cmid->device != ((void *)0) ) failed: Signed-off-by: Alexander Boyko

[PATCH 4.9 60/65] bpf: fix mlock precharge on arraymaps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in

[PATCH 4.9 60/65] bpf: fix mlock precharge on arraymaps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in progress by Dennis Zhou to

[PATCH 4.9 63/65] bpf: add schedule points in percpu arrays management

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to

[PATCH 4.9 63/65] bpf: add schedule points in percpu arrays management

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to allocate a huge percpu

[PATCH 4.9 58/65] mpls, nospec: Sanitize array index in mpls_label_ok()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 3968523f855050b8195134da951b87c20bd66130 upstream. mpls_label_ok() validates that the 'platform_label' array index from a userspace netlink

[PATCH 4.9 62/65] bpf, arm64: fix out of bounds access in tail call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper. The

[PATCH 4.9 58/65] mpls, nospec: Sanitize array index in mpls_label_ok()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 3968523f855050b8195134da951b87c20bd66130 upstream. mpls_label_ok() validates that the 'platform_label' array index from a userspace netlink message payload is valid. Under

[PATCH 4.9 62/65] bpf, arm64: fix out of bounds access in tail call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper. The crash would not occur

[PATCH 4.9 64/65] bpf, ppc64: fix out of bounds access in tail call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit d269176e766c71c998cb75b4ea8cbc321cc0019d ] While working on 16338a9b3ac3 ("bpf, arm64: fix out of bounds access in tail call") I noticed

[PATCH 4.9 61/65] bpf, x64: implement retpoline for tail call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a493a87f38cfa48caaa95c9347be2d914c6fdf29 ] Implement a retpoline [0] for the BPF tail call JIT'ing that converts the indirect jump via

[PATCH 4.9 64/65] bpf, ppc64: fix out of bounds access in tail call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit d269176e766c71c998cb75b4ea8cbc321cc0019d ] While working on 16338a9b3ac3 ("bpf, arm64: fix out of bounds access in tail call") I noticed that ppc64 JIT is

[PATCH 4.9 61/65] bpf, x64: implement retpoline for tail call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a493a87f38cfa48caaa95c9347be2d914c6fdf29 ] Implement a retpoline [0] for the BPF tail call JIT'ing that converts the indirect jump via jmp %rax that is used

[PATCH 4.14 2/9] bpf: fix memory leak in lpm_trie map_free callback function

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 9a3efb6b661f71d5675369ace9257833f0e78ef3 ] There is a memory leak happening in lpm_trie map_free callback function trie_free. The trie structure

[PATCH 4.14 4/9] bpf, x64: implement retpoline for tail call

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a493a87f38cfa48caaa95c9347be2d914c6fdf29 ] Implement a retpoline [0] for the BPF tail call JIT'ing that converts the indirect jump via

[PATCH 4.14 2/9] bpf: fix memory leak in lpm_trie map_free callback function

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 9a3efb6b661f71d5675369ace9257833f0e78ef3 ] There is a memory leak happening in lpm_trie map_free callback function trie_free. The trie structure itself does

[PATCH 4.14 4/9] bpf, x64: implement retpoline for tail call

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a493a87f38cfa48caaa95c9347be2d914c6fdf29 ] Implement a retpoline [0] for the BPF tail call JIT'ing that converts the indirect jump via jmp %rax that is used

[PATCH 4.14 5/9] bpf, arm64: fix out of bounds access in tail call

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper.

[PATCH 4.14 5/9] bpf, arm64: fix out of bounds access in tail call

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper. The crash would not

[PATCH 4.15 01/11] bpf: fix mlock precharge on arraymaps

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in

[PATCH 4.15 01/11] bpf: fix mlock precharge on arraymaps

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in progress by Dennis Zhou to

[PATCH 4.14 8/9] bpf, ppc64: fix out of bounds access in tail call

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit d269176e766c71c998cb75b4ea8cbc321cc0019d ] While working on 16338a9b3ac3 ("bpf, arm64: fix out of bounds access in tail call") I

[PATCH 4.14 0/9] 4.14.26-stable review

This is the start of the stable review cycle for the 4.14.26 release. There are 9 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 Mon Mar 12 00:18:16 UTC 2018. Anything

[PATCH 4.14 8/9] bpf, ppc64: fix out of bounds access in tail call

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit d269176e766c71c998cb75b4ea8cbc321cc0019d ] While working on 16338a9b3ac3 ("bpf, arm64: fix out of bounds access in tail call") I noticed that ppc64 JIT is

[PATCH 4.14 0/9] 4.14.26-stable review

This is the start of the stable review cycle for the 4.14.26 release. There are 9 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 Mon Mar 12 00:18:16 UTC 2018. Anything

[PATCH 4.14 7/9] bpf: allow xadd only on aligned memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit ca36960211eb228bcbc7aaebfa0d027368a94c60 ] The requirements around atomic_add() / atomic64_add() resp. their JIT implementations differ

[PATCH 4.14 7/9] bpf: allow xadd only on aligned memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit ca36960211eb228bcbc7aaebfa0d027368a94c60 ] The requirements around atomic_add() / atomic64_add() resp. their JIT implementations differ across architectures.

[PATCH 4.15 04/11] bpf, x64: implement retpoline for tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a493a87f38cfa48caaa95c9347be2d914c6fdf29 ] Implement a retpoline [0] for the BPF tail call JIT'ing that converts the indirect jump via

[PATCH 4.15 03/11] bpf: fix rcu lockdep warning for lpm_trie map_free callback

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 6c5f61023c5b0edb0c8a64c902fe97c6453b1852 ] Commit 9a3efb6b661f ("bpf: fix memory leak in lpm_trie map_free callback function") fixed a memory

[PATCH 4.15 04/11] bpf, x64: implement retpoline for tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a493a87f38cfa48caaa95c9347be2d914c6fdf29 ] Implement a retpoline [0] for the BPF tail call JIT'ing that converts the indirect jump via jmp %rax that is used

[PATCH 4.15 03/11] bpf: fix rcu lockdep warning for lpm_trie map_free callback

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 6c5f61023c5b0edb0c8a64c902fe97c6453b1852 ] Commit 9a3efb6b661f ("bpf: fix memory leak in lpm_trie map_free callback function") fixed a memory leak and removed

[PATCH 4.15 02/11] bpf: fix memory leak in lpm_trie map_free callback function

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 9a3efb6b661f71d5675369ace9257833f0e78ef3 ] There is a memory leak happening in lpm_trie map_free callback function trie_free. The trie structure

[PATCH 4.15 08/11] bpf, ppc64: fix out of bounds access in tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit d269176e766c71c998cb75b4ea8cbc321cc0019d ] While working on 16338a9b3ac3 ("bpf, arm64: fix out of bounds access in tail call") I

[PATCH 4.15 02/11] bpf: fix memory leak in lpm_trie map_free callback function

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 9a3efb6b661f71d5675369ace9257833f0e78ef3 ] There is a memory leak happening in lpm_trie map_free callback function trie_free. The trie structure itself does

[PATCH 4.15 08/11] bpf, ppc64: fix out of bounds access in tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit d269176e766c71c998cb75b4ea8cbc321cc0019d ] While working on 16338a9b3ac3 ("bpf, arm64: fix out of bounds access in tail call") I noticed that ppc64 JIT is

[PATCH 4.15 09/11] scsi: mpt3sas: fix oops in error handlers after shutdown/unload

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Mauricio Faria de Oliveira commit 9ff549ffb4fb4cc9a4b24d1de9dc3e68287797c4 upstream. This patch adds checks for 'ioc->remove_host' in the SCSI error handlers, so

[PATCH 4.15 07/11] bpf: allow xadd only on aligned memory

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit ca36960211eb228bcbc7aaebfa0d027368a94c60 ] The requirements around atomic_add() / atomic64_add() resp. their JIT implementations differ

[PATCH 4.15 00/11] 4.15.9-stable review

This is the start of the stable review cycle for the 4.15.9 release. There are 11 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 Mon Mar 12 00:18:21 UTC 2018. Anything

[PATCH 4.15 09/11] scsi: mpt3sas: fix oops in error handlers after shutdown/unload

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Mauricio Faria de Oliveira commit 9ff549ffb4fb4cc9a4b24d1de9dc3e68287797c4 upstream. This patch adds checks for 'ioc->remove_host' in the SCSI error handlers, so not to access

[PATCH 4.15 07/11] bpf: allow xadd only on aligned memory

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit ca36960211eb228bcbc7aaebfa0d027368a94c60 ] The requirements around atomic_add() / atomic64_add() resp. their JIT implementations differ across architectures.

[PATCH 4.15 00/11] 4.15.9-stable review

This is the start of the stable review cycle for the 4.15.9 release. There are 11 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 Mon Mar 12 00:18:21 UTC 2018. Anything

[PATCH 4.15 06/11] bpf: add schedule points in percpu arrays management

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to

[PATCH 4.15 06/11] bpf: add schedule points in percpu arrays management

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to allocate a huge percpu

[PATCH 4.15 05/11] bpf, arm64: fix out of bounds access in tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper.

[PATCH 4.15 05/11] bpf, arm64: fix out of bounds access in tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper. The crash would not

[PATCH 4.14 6/9] bpf: add schedule points in percpu arrays management

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to

[PATCH 4.14 6/9] bpf: add schedule points in percpu arrays management

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to allocate a huge percpu

[PATCH 4.9 30/65] md: only allow remove_and_add_spares when no sync_thread running.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 39772f0a7be3b3dc26c74ea13fe7847fd1522c8b upstream. The locking protocols in md assume that a device will never be removed from an array during

[PATCH 4.9 59/65] bpf: fix wrong exposure of map_flags into fdinfo for lpm

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a316338cb71a3260201490e615f2f6d5c0d8fb2c ] trie_alloc() always needs to have BPF_F_NO_PREALLOC passed in via attr->map_flags, since it

[PATCH 4.9 59/65] bpf: fix wrong exposure of map_flags into fdinfo for lpm

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a316338cb71a3260201490e615f2f6d5c0d8fb2c ] trie_alloc() always needs to have BPF_F_NO_PREALLOC passed in via attr->map_flags, since it does not support

[PATCH 4.9 30/65] md: only allow remove_and_add_spares when no sync_thread running.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 39772f0a7be3b3dc26c74ea13fe7847fd1522c8b upstream. The locking protocols in md assume that a device will never be removed from an array during resync/recovery/reshape. When

[PATCH 4.15 10/11] scsi: mpt3sas: wait for and flush running commands on shutdown/unload

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Sreekanth Reddy commit c666d3be99c000bb889a33353e9be0fa5808d3de upstream. This patch finishes all outstanding SCSI IO commands (but not other commands, e.g.,

[PATCH 4.14 3/9] bpf: fix rcu lockdep warning for lpm_trie map_free callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 6c5f61023c5b0edb0c8a64c902fe97c6453b1852 ] Commit 9a3efb6b661f ("bpf: fix memory leak in lpm_trie map_free callback function") fixed a memory

[PATCH 4.14 1/9] bpf: fix mlock precharge on arraymaps

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in

[PATCH 4.15 10/11] scsi: mpt3sas: wait for and flush running commands on shutdown/unload

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Sreekanth Reddy commit c666d3be99c000bb889a33353e9be0fa5808d3de upstream. This patch finishes all outstanding SCSI IO commands (but not other commands, e.g., task management) in the shutdown

[PATCH 4.14 3/9] bpf: fix rcu lockdep warning for lpm_trie map_free callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 6c5f61023c5b0edb0c8a64c902fe97c6453b1852 ] Commit 9a3efb6b661f ("bpf: fix memory leak in lpm_trie map_free callback function") fixed a memory leak and removed

[PATCH 4.14 1/9] bpf: fix mlock precharge on arraymaps

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in progress by Dennis Zhou to

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