[PATCH 4.9 27/66] mm: fix 100% CPU kswapd busyloop on unreclaimable nodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Weiner commit c73322d098e4b6f5f0f0fa1330bf57e218775539 upstream. Patch series "mm: kswapd spinning on unreclaimable nodes - fixes and cleanups". Jia reported a

[PATCH 4.9 27/66] mm: fix 100% CPU kswapd busyloop on unreclaimable nodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Weiner commit c73322d098e4b6f5f0f0fa1330bf57e218775539 upstream. Patch series "mm: kswapd spinning on unreclaimable nodes - fixes and cleanups". Jia reported a scenario in which the

[PATCH 4.9 02/66] orangefs: use list_for_each_entry_safe in purge_waiting_ops

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 0afc0decf247f65b7aba666a76a0a68adf4bc435 upstream. set_op_state_purged can delete the op. Signed-off-by: Martin Brandenburg

[PATCH 4.9 02/66] orangefs: use list_for_each_entry_safe in purge_waiting_ops

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 0afc0decf247f65b7aba666a76a0a68adf4bc435 upstream. set_op_state_purged can delete the op. Signed-off-by: Martin Brandenburg Signed-off-by: Linus Torvalds

[PATCH 4.14 13/71] orangefs: fix deadlock; do not write i_size in read_iter

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 6793f1c450b1533a5e9c2493490de771d38b24f9 upstream. After do_readv_writev, the inode cache is invalidated anyway, so i_size will never be read.

[PATCH 4.4 24/74] mm, page_alloc: fix potential false positive in __zone_watermark_ok

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit b050e3769c6b4013bb937e879fc43bf1847ee819 upstream. Since commit 97a16fc82a7c ("mm, page_alloc: only enforce watermarks for order-0 allocations"),

[PATCH 4.14 13/71] orangefs: fix deadlock; do not write i_size in read_iter

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 6793f1c450b1533a5e9c2493490de771d38b24f9 upstream. After do_readv_writev, the inode cache is invalidated anyway, so i_size will never be read. It will be fetched

[PATCH 4.4 24/74] mm, page_alloc: fix potential false positive in __zone_watermark_ok

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit b050e3769c6b4013bb937e879fc43bf1847ee819 upstream. Since commit 97a16fc82a7c ("mm, page_alloc: only enforce watermarks for order-0 allocations"), __zone_watermark_ok()

[PATCH 4.14 30/71] net: igmp: fix source address check for IGMPv3 reports

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit ad23b750933ea7bf962678972a286c78a8fa36aa ] Commit "net: igmp: Use correct source address on IGMPv3 reports" introduced a check to validate the

[PATCH 4.9 55/66] flow_dissector: properly cap thoff field

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit d0c081b49137cd3200f2023c0875723be66e7ce5 ] syzbot reported yet another crash [1] that is caused by insufficient validation of DODGY

[PATCH 4.14 30/71] net: igmp: fix source address check for IGMPv3 reports

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit ad23b750933ea7bf962678972a286c78a8fa36aa ] Commit "net: igmp: Use correct source address on IGMPv3 reports" introduced a check to validate the source address

[PATCH 4.9 55/66] flow_dissector: properly cap thoff field

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit d0c081b49137cd3200f2023c0875723be66e7ce5 ] syzbot reported yet another crash [1] that is caused by insufficient validation of DODGY packets. Two bugs are

[PATCH 3.18 05/52] ALSA: hda - Apply the existing quirk to iMac 14,1

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 031f335cda879450095873003abb03ae8ed3b74a upstream. iMac 14,1 requires the same quirk as iMac 12,2, using GPIO 2 and 3 for headphone and speaker output amps.

[PATCH 3.18 05/52] ALSA: hda - Apply the existing quirk to iMac 14,1

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 031f335cda879450095873003abb03ae8ed3b74a upstream. iMac 14,1 requires the same quirk as iMac 12,2, using GPIO 2 and 3 for headphone and speaker output amps. Add the codec

[PATCH 4.4 18/74] PCI: layerscape: Fix MSG TLP drop setting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Minghuan Lian commit 1195c103f6c98d9ff381cac3a8760d4f8a133627 upstream. Some kinds of Layerscape PCIe controllers will forward the received message TLPs to system

[PATCH 4.4 18/74] PCI: layerscape: Fix MSG TLP drop setting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Minghuan Lian commit 1195c103f6c98d9ff381cac3a8760d4f8a133627 upstream. Some kinds of Layerscape PCIe controllers will forward the received message TLPs to system application address space,

[PATCH 4.4 28/74] ACPI / scan: Prefer devices without _HID/_CID for _ADR matching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit c2a6bbaf0c5f90463a7011a295bbdb7e33c80b51 upstream. The way acpi_find_child_device() works currently is that, if there are two (or more)

[PATCH 4.4 28/74] ACPI / scan: Prefer devices without _HID/_CID for _ADR matching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit c2a6bbaf0c5f90463a7011a295bbdb7e33c80b51 upstream. The way acpi_find_child_device() works currently is that, if there are two (or more) devices with the same _ADR

[PATCH 3.18 25/52] hwpoison, memcg: forcibly uncharge LRU pages

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michal Hocko commit 18365225f0440d09708ad9daade2ec11275c3df9 upstream. Laurent Dufour has noticed that hwpoinsoned pages are kept charged. In his particular case he has hit

[PATCH 3.18 25/52] hwpoison, memcg: forcibly uncharge LRU pages

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michal Hocko commit 18365225f0440d09708ad9daade2ec11275c3df9 upstream. Laurent Dufour has noticed that hwpoinsoned pages are kept charged. In his particular case he has hit a bad_page("page

[PATCH 4.14 10/71] Input: trackpoint - only expose supported controls for Elan, ALPS and NXP

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 2a924d71794c530e55e73d0ce2cc77233307eaa9 upstream. The newer trackpoints from ALPS, Elan and NXP implement a very limited subset of extended

[PATCH 4.14 10/71] Input: trackpoint - only expose supported controls for Elan, ALPS and NXP

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 2a924d71794c530e55e73d0ce2cc77233307eaa9 upstream. The newer trackpoints from ALPS, Elan and NXP implement a very limited subset of extended commands and controls that

[PATCH 3.18 16/52] dm btree: fix serious bug in btree_split_beneath()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit bc68d0a43560e950850fc69b58f0f8254b28f6d6 upstream. When inserting a new key/value pair into a btree we walk down the spine of btree nodes performing

[PATCH 3.18 16/52] dm btree: fix serious bug in btree_split_beneath()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit bc68d0a43560e950850fc69b58f0f8254b28f6d6 upstream. When inserting a new key/value pair into a btree we walk down the spine of btree nodes performing the following 2

[PATCH 4.4 15/74] drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit fac51482577d5e05bbb0efa8d602a3c2111098bf upstream. With CONFIG_OF enabled on x86, we get the following error on boot: " Failed to find cpu0

[PATCH 4.4 15/74] drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit fac51482577d5e05bbb0efa8d602a3c2111098bf upstream. With CONFIG_OF enabled on x86, we get the following error on boot: " Failed to find cpu0 device node

Re: [RFC,05/10] x86/speculation: Add basic IBRS support infrastructure

On Mon, 2018-01-29 at 18:14 -0200, Eduardo Habkost wrote: > > Sorry for being confused here, as probably the answer is buried > on a LKML thread somewhere.  The comment explains what the code > does, but not why.  Why exactly IBRS is preferred on Skylake? > > I'm asking this because I would like

Re: [RFC,05/10] x86/speculation: Add basic IBRS support infrastructure

On Mon, 2018-01-29 at 18:14 -0200, Eduardo Habkost wrote: > > Sorry for being confused here, as probably the answer is buried > on a LKML thread somewhere.  The comment explains what the code > does, but not why.  Why exactly IBRS is preferred on Skylake? > > I'm asking this because I would like

[PATCH 4.14 18/71] ARM: net: bpf: correct stack layout documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 0005e55a79cfda88199e41a406a829c88d708c67 upstream. The stack layout documentation incorrectly suggests that the BPF JIT scratch space starts

[PATCH 4.14 18/71] ARM: net: bpf: correct stack layout documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 0005e55a79cfda88199e41a406a829c88d708c67 upstream. The stack layout documentation incorrectly suggests that the BPF JIT scratch space starts immediately below BPF_FP. This

[PATCH 4.14 01/71] orangefs: use list_for_each_entry_safe in purge_waiting_ops

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 0afc0decf247f65b7aba666a76a0a68adf4bc435 upstream. set_op_state_purged can delete the op. Signed-off-by: Martin Brandenburg

[PATCH 4.14 01/71] orangefs: use list_for_each_entry_safe in purge_waiting_ops

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 0afc0decf247f65b7aba666a76a0a68adf4bc435 upstream. set_op_state_purged can delete the op. Signed-off-by: Martin Brandenburg Signed-off-by: Linus Torvalds

[PATCH 3.18 35/52] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit eef9ffdf9cd39b2986367bc8395e2772bc1284ba upstream. The SCSI host byte should be shifted left by 16 in order to have scsi_decide_disposition() do

[PATCH 3.18 35/52] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit eef9ffdf9cd39b2986367bc8395e2772bc1284ba upstream. The SCSI host byte should be shifted left by 16 in order to have scsi_decide_disposition() do the right thing

[PATCH 4.14 15/71] ARM: net: bpf: fix tail call jumps

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit f4483f2cc1fdc03488c8a1452e545545ae5bda93 upstream. When a tail call fails, it is documented that the tail call should continue execution at the

[PATCH 4.14 15/71] ARM: net: bpf: fix tail call jumps

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit f4483f2cc1fdc03488c8a1452e545545ae5bda93 upstream. When a tail call fails, it is documented that the tail call should continue execution at the following instruction. An

[PATCH 4.9 28/66] Input: trackpoint - force 3 buttons if 0 button is reported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Ma commit f5d07b9e98022d50720e38aa936fc11c67868ece upstream. Lenovo introduced trackpoint compatible sticks with minimum PS/2 commands. They supposed to reply

[PATCH 4.9 28/66] Input: trackpoint - force 3 buttons if 0 button is reported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Ma commit f5d07b9e98022d50720e38aa936fc11c67868ece upstream. Lenovo introduced trackpoint compatible sticks with minimum PS/2 commands. They supposed to reply with 0x02, 0x03, or 0x04 in

[PATCH 4.14 36/71] r8169: fix memory corruption on retrieval of hardware statistics.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Francois Romieu [ Upstream commit a78e93661c5fd30b9e1dee464b2f62f966883ef7 ] Hardware statistics retrieval hurts in tight invocation loops. Avoid extraneous write and

[PATCH 4.14 36/71] r8169: fix memory corruption on retrieval of hardware statistics.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Francois Romieu [ Upstream commit a78e93661c5fd30b9e1dee464b2f62f966883ef7 ] Hardware statistics retrieval hurts in tight invocation loops. Avoid extraneous write and enforce strict

[PATCH 4.4 74/74] net: tcp: close sock if net namespace is exiting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Streetman [ Upstream commit 4ee806d51176ba7b8ff1efd81f271d7252e03a1d ] When a tcp socket is closed, if it detects that its net namespace is exiting, close immediately

[PATCH 4.4 74/74] net: tcp: close sock if net namespace is exiting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Streetman [ Upstream commit 4ee806d51176ba7b8ff1efd81f271d7252e03a1d ] When a tcp socket is closed, if it detects that its net namespace is exiting, close immediately and do not wait for

[PATCH 4.4 07/74] x86/retpoline: Fill RSB on context switch for affected CPUs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit c995efd5a740d9cbafbf58bde4973e8b50b4d761 upstream. On context switch from a shallow call stack to a deeper one, as the CPU does 'ret' up the deeper

[PATCH 3.18 06/52] af_key: fix buffer overread in verify_address_len()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 06b335cb51af018d5feeff5dd4fd53847ddb675a upstream. If a message sent to a PF_KEY socket ended with one of the extensions that takes a 'struct

[PATCH 4.4 07/74] x86/retpoline: Fill RSB on context switch for affected CPUs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit c995efd5a740d9cbafbf58bde4973e8b50b4d761 upstream. On context switch from a shallow call stack to a deeper one, as the CPU does 'ret' up the deeper side it may encounter

[PATCH 3.18 06/52] af_key: fix buffer overread in verify_address_len()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 06b335cb51af018d5feeff5dd4fd53847ddb675a upstream. If a message sent to a PF_KEY socket ended with one of the extensions that takes a 'struct sadb_address' but there were

[PATCH 4.4 33/74] netfilter: nf_ct_expect: remove the redundant slash when policy name is empty

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liping Zhang commit b173a28f62cf929324a8a6adcc45adadce311d16 upstream. The 'name' filed in struct nf_conntrack_expect_policy{} is not a pointer, so check it is

[PATCH 4.9 21/66] netfilter: xt_osf: Add missing permission checks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Cernekee commit 916a27901de01446bcf57ecca4783f6cff493309 upstream. The capability check in nfnetlink_rcv() verifies that the caller has CAP_NET_ADMIN in the

[PATCH 4.4 33/74] netfilter: nf_ct_expect: remove the redundant slash when policy name is empty

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liping Zhang commit b173a28f62cf929324a8a6adcc45adadce311d16 upstream. The 'name' filed in struct nf_conntrack_expect_policy{} is not a pointer, so check it is NULL or not will always return

[PATCH 4.9 21/66] netfilter: xt_osf: Add missing permission checks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Cernekee commit 916a27901de01446bcf57ecca4783f6cff493309 upstream. The capability check in nfnetlink_rcv() verifies that the caller has CAP_NET_ADMIN in the namespace that "owns" the

Re: [PATCH 4.9] usbip: vhci_hcd: clear just the USB_PORT_STAT_POWER bit

On 01/28/2018 05:14 AM, Greg KH wrote: > On Fri, Jan 26, 2018 at 11:54:35AM -0700, Shuah Khan wrote: >> Upstream commit 1c9de5bf4286 ("usbip: vhci-hcd: Add USB3 SuperSpeed >> support") > > Hm, I think you have the wrong commit id here. > > I don't see any commit upstream with the Subject you

[PATCH 4.14 68/71] bpf: fix 32-bit divide by zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov [ upstream commit 68fda450a7df51cff9e5a4d4a4d9d0d5f2589153 ] due to some JITs doing if (src_reg == 0) check in 64-bit mode for div/mod operations mask

[PATCH 4.14 68/71] bpf: fix 32-bit divide by zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov [ upstream commit 68fda450a7df51cff9e5a4d4a4d9d0d5f2589153 ] due to some JITs doing if (src_reg == 0) check in 64-bit mode for div/mod operations mask upper 32-bits of src

Re: [PATCH 4.9] usbip: vhci_hcd: clear just the USB_PORT_STAT_POWER bit

On 01/28/2018 05:14 AM, Greg KH wrote: > On Fri, Jan 26, 2018 at 11:54:35AM -0700, Shuah Khan wrote: >> Upstream commit 1c9de5bf4286 ("usbip: vhci-hcd: Add USB3 SuperSpeed >> support") > > Hm, I think you have the wrong commit id here. > > I don't see any commit upstream with the Subject you

[PATCH 4.9 51/66] ip6_gre: init dev->mtu and dev->hard_header_len correctly

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 128bb975dc3c25d00de04e503e2fe0a780d04459 ] Commit b05229f44228 ("gre6: Cleanup GREv6 transmit path, call common GRE functions")

[PATCH 4.9 30/66] um: link vmlinux with -no-pie

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Meyer commit 883354afbc109c57f925ccc19840055193da0cc0 upstream. Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic

[PATCH 4.9 51/66] ip6_gre: init dev->mtu and dev->hard_header_len correctly

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 128bb975dc3c25d00de04e503e2fe0a780d04459 ] Commit b05229f44228 ("gre6: Cleanup GREv6 transmit path, call common GRE functions") moved dev->mtu initialization

[PATCH 4.9 30/66] um: link vmlinux with -no-pie

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Meyer commit 883354afbc109c57f925ccc19840055193da0cc0 upstream. Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic kernel image

Re: [RFC,05/10] x86/speculation: Add basic IBRS support infrastructure

On Sat, Jan 20, 2018 at 08:22:56PM +0100, KarimAllah Ahmed wrote: > From: David Woodhouse > > Not functional yet; just add the handling for it in the Spectre v2 > mitigation selection, and the X86_FEATURE_IBRS flag which will control > the code to be added in later patches. >

Re: [RFC,05/10] x86/speculation: Add basic IBRS support infrastructure

On Sat, Jan 20, 2018 at 08:22:56PM +0100, KarimAllah Ahmed wrote: > From: David Woodhouse > > Not functional yet; just add the handling for it in the Spectre v2 > mitigation selection, and the X86_FEATURE_IBRS flag which will control > the code to be added in later patches. > > Also take the

[PATCH 3.18 52/52] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jim Westfall [ Upstream commit cd9ff4de0107c65d69d02253bb25d6db93c3dbc1 ] Map all lookup neigh keys to INADDR_ANY for loopback/point-to-point devices to avoid

[PATCH 3.18 52/52] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jim Westfall [ Upstream commit cd9ff4de0107c65d69d02253bb25d6db93c3dbc1 ] Map all lookup neigh keys to INADDR_ANY for loopback/point-to-point devices to avoid making an entry for every

[PATCH 4.9 63/66] bpf: avoid false sharing of map refcount with max_entries

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit be95a845cc4402272994ce290e3ad928aff06cb9 ] In addition to commit b2157399cc98 ("bpf: prevent out-of-bounds speculation") also change the

[PATCH 4.9 63/66] bpf: avoid false sharing of map refcount with max_entries

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit be95a845cc4402272994ce290e3ad928aff06cb9 ] In addition to commit b2157399cc98 ("bpf: prevent out-of-bounds speculation") also change the layout of struct

Re: [PATCH] nvme-pci: use NOWAIT flag for nvme_set_host_mem

On Mon, Jan 29, 2018 at 09:55:41PM +0200, Sagi Grimberg wrote: > > Thanks for the fix. It looks like we still have a problem, though. > > Commands submitted with the "shutdown_lock" held need to be able to make > > forward progress without relying on a completion, but this one could > > block

Re: [PATCH] nvme-pci: use NOWAIT flag for nvme_set_host_mem

On Mon, Jan 29, 2018 at 09:55:41PM +0200, Sagi Grimberg wrote: > > Thanks for the fix. It looks like we still have a problem, though. > > Commands submitted with the "shutdown_lock" held need to be able to make > > forward progress without relying on a completion, but this one could > > block

Re: Avoiding information leaks between users and between processes by default? [Was: : [PATCH 1/5] prctl: add PR_ISOLATE_BP process control]

On Mon, 29 Jan 2018 14:14:46 +0100 Pavel Machek wrote: > On Wed 2018-01-24 20:46:22, Alan Cox wrote: > > > Anyway, no need to add prctl(), if A can ptrace B and B can ptrace A, > > > leaking info between them should not be a big deal. You can probably > > > find existing macros

Re: Avoiding information leaks between users and between processes by default? [Was: : [PATCH 1/5] prctl: add PR_ISOLATE_BP process control]

On Mon, 29 Jan 2018 14:14:46 +0100 Pavel Machek wrote: > On Wed 2018-01-24 20:46:22, Alan Cox wrote: > > > Anyway, no need to add prctl(), if A can ptrace B and B can ptrace A, > > > leaking info between them should not be a big deal. You can probably > > > find existing macros doing neccessary

[PATCH 4.4 23/74] cma: fix calculation of aligned offset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Doug Berger commit e048cb32f69038aa1c8f11e5c1b331be4181659d upstream. The align_offset parameter is used by bitmap_find_next_zero_area_off() to represent the offset of map's

[PATCH 4.4 23/74] cma: fix calculation of aligned offset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Doug Berger commit e048cb32f69038aa1c8f11e5c1b331be4181659d upstream. The align_offset parameter is used by bitmap_find_next_zero_area_off() to represent the offset of map's base from the

[PATCH 4.14 51/71] net/mlx5e: Fix fixpoint divide exception in mlx5e_am_stats_compare

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Talat Batheesh [ Upstream commit e58edaa4863583b54409444f11b4f80dff0af1cd ] Helmut reported a bug about division by zero while running traffic and doing physical cable

[PATCH 4.14 51/71] net/mlx5e: Fix fixpoint divide exception in mlx5e_am_stats_compare

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Talat Batheesh [ Upstream commit e58edaa4863583b54409444f11b4f80dff0af1cd ] Helmut reported a bug about division by zero while running traffic and doing physical cable pull test. When the

[PATCH 4.4 04/74] usbip: Fix potential format overflow in userspace tools

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Dieter commit e5dfa3f902b9a642ae8c6997d57d7c41e384a90b upstream. The usbip userspace tools call sprintf()/snprintf() and don't check for the return value which can

[PATCH 4.4 04/74] usbip: Fix potential format overflow in userspace tools

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Dieter commit e5dfa3f902b9a642ae8c6997d57d7c41e384a90b upstream. The usbip userspace tools call sprintf()/snprintf() and don't check for the return value which can lead the paths to

[PATCH 4.9 43/66] sctp: do not allow the v4 socket to bind a v4mapped v6 address

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit c5006b8aa74599ce19104b31d322d2ea9ff887cc ] The check in sctp_sockaddr_af is not robust enough to forbid binding a v4mapped v6 addr on a v4

[PATCH 3.18 30/52] netfilter: nfnetlink_cthelper: Add missing permission checks

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Cernekee commit 4b380c42f7d00a395feede754f0bc2292eebe6e5 upstream. The capability check in nfnetlink_rcv() verifies that the caller has CAP_NET_ADMIN in the

[PATCH 4.9 43/66] sctp: do not allow the v4 socket to bind a v4mapped v6 address

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit c5006b8aa74599ce19104b31d322d2ea9ff887cc ] The check in sctp_sockaddr_af is not robust enough to forbid binding a v4mapped v6 addr on a v4 socket. The worse thing

[PATCH 3.18 30/52] netfilter: nfnetlink_cthelper: Add missing permission checks

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Cernekee commit 4b380c42f7d00a395feede754f0bc2292eebe6e5 upstream. The capability check in nfnetlink_rcv() verifies that the caller has CAP_NET_ADMIN in the namespace that "owns" the

[PATCH 4.4 11/74] PM / sleep: declare __tracedata symbols as char[] rather than char

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit f97238373b8662a6d580e204df2e7bcbfa43e27a upstream. Accessing more than one byte from a symbol declared simply 'char' is undefined behavior, as reported

[PATCH 4.4 11/74] PM / sleep: declare __tracedata symbols as char[] rather than char

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit f97238373b8662a6d580e204df2e7bcbfa43e27a upstream. Accessing more than one byte from a symbol declared simply 'char' is undefined behavior, as reported by UBSAN:

[PATCH 4.4 53/74] um: link vmlinux with -no-pie

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Meyer commit 883354afbc109c57f925ccc19840055193da0cc0 upstream. Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic

[PATCH 4.4 53/74] um: link vmlinux with -no-pie

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Meyer commit 883354afbc109c57f925ccc19840055193da0cc0 upstream. Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic kernel image

[PATCH 4.9 29/66] orangefs: fix deadlock; do not write i_size in read_iter

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 6793f1c450b1533a5e9c2493490de771d38b24f9 upstream. After do_readv_writev, the inode cache is invalidated anyway, so i_size will never be read.

[PATCH 4.9 29/66] orangefs: fix deadlock; do not write i_size in read_iter

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit 6793f1c450b1533a5e9c2493490de771d38b24f9 upstream. After do_readv_writev, the inode cache is invalidated anyway, so i_size will never be read. It will be fetched

[PATCH 4.9 03/66] orangefs: initialize op on loop restart in orangefs_devreq_read

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit a0ec1ded22e6a6bc41981fae22406835b006a66e upstream. In orangefs_devreq_read, there is a loop which picks an op off the list of pending ops. If

[PATCH 4.14 06/71] xfrm: Fix a race in the xdst pcpu cache.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit 76a4201191814a0061cb5c861fafb9ecaa764846 upstream. We need to run xfrm_resolve_and_create_bundle() with bottom halves off. Otherwise we

[PATCH 3.18 00/52] 3.18.93-stable review

This is the start of the stable review cycle for the 3.18.93 release. There are 52 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 Jan 31 12:36:07 UTC 2018. Anything

[PATCH 4.9 03/66] orangefs: initialize op on loop restart in orangefs_devreq_read

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Brandenburg commit a0ec1ded22e6a6bc41981fae22406835b006a66e upstream. In orangefs_devreq_read, there is a loop which picks an op off the list of pending ops. If the loop fails to find

[PATCH 4.14 06/71] xfrm: Fix a race in the xdst pcpu cache.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit 76a4201191814a0061cb5c861fafb9ecaa764846 upstream. We need to run xfrm_resolve_and_create_bundle() with bottom halves off. Otherwise we may reuse an already released

[PATCH 3.18 00/52] 3.18.93-stable review

This is the start of the stable review cycle for the 3.18.93 release. There are 52 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 Jan 31 12:36:07 UTC 2018. Anything

[PATCH 4.4 38/74] netfilter: fix IS_ERR_VALUE usage

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Pablo Neira Ayuso commit 92b4423e3a0bc5d43ecde4bcad871f8b5ba04efd upstream. This is a forward-port of the original patch from Andrzej Hajda, he said: "IS_ERR_VALUE should

[PATCH 4.4 38/74] netfilter: fix IS_ERR_VALUE usage

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Pablo Neira Ayuso commit 92b4423e3a0bc5d43ecde4bcad871f8b5ba04efd upstream. This is a forward-port of the original patch from Andrzej Hajda, he said: "IS_ERR_VALUE should be used only with

[PATCH 4.14 70/71] bpf, arm64: fix stack_depth tracking in combination with tail calls

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a2284d912bfc865cdca4c00488e08a3550f9a405 ] Using dynamic stack_depth tracking in arm64 JIT is currently broken in combination with tail

[PATCH 4.14 70/71] bpf, arm64: fix stack_depth tracking in combination with tail calls

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit a2284d912bfc865cdca4c00488e08a3550f9a405 ] Using dynamic stack_depth tracking in arm64 JIT is currently broken in combination with tail calls. In prologue,

[PATCH 4.14 07/71] Revert "module: Add retpoline tag to VERMAGIC"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 5132ede0fe8092b043dae09a7cc32b8ae7272baa upstream. This reverts commit 6cfb521ac0d5b97470883ff9b7facae264b7ab12. Turns out distros do

[PATCH 4.4 30/74] netfilter: x_tables: speed up jump target validation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit f4dc77713f8016d2e8a3295e1c9c53a21f296def upstream. The dummy ruleset I used to test the original validation change was broken, most rules were

[PATCH 4.9 16/66] mm, page_alloc: fix potential false positive in __zone_watermark_ok

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit b050e3769c6b4013bb937e879fc43bf1847ee819 upstream. Since commit 97a16fc82a7c ("mm, page_alloc: only enforce watermarks for order-0 allocations"),

[PATCH 4.14 07/71] Revert "module: Add retpoline tag to VERMAGIC"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 5132ede0fe8092b043dae09a7cc32b8ae7272baa upstream. This reverts commit 6cfb521ac0d5b97470883ff9b7facae264b7ab12. Turns out distros do not want to make retpoline as

[PATCH 4.4 30/74] netfilter: x_tables: speed up jump target validation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit f4dc77713f8016d2e8a3295e1c9c53a21f296def upstream. The dummy ruleset I used to test the original validation change was broken, most rules were unreachable and were not

[PATCH 4.9 16/66] mm, page_alloc: fix potential false positive in __zone_watermark_ok

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit b050e3769c6b4013bb937e879fc43bf1847ee819 upstream. Since commit 97a16fc82a7c ("mm, page_alloc: only enforce watermarks for order-0 allocations"), __zone_watermark_ok()

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