[PATCH 4.4 62/74] lan78xx: Fix failure in USB Full Speed

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yuiko Oshino [ Upstream commit a5b1379afbfabf91e3a689e82ac619a7157336b3 ] Fix initialize the uninitialized tx_qlen to an appropriate value when USB Full Speed is used. Fixes: 55d7de9de6c3

[PATCH 3.18 46/52] pppoe: take ->needed_headroom of lower device into account on xmit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault [ Upstream commit 02612bb05e51df8489db5e94d0cf8d1c81f87b0c ] In pppoe_sendmsg(), reserving dev->hard_header_len bytes of headroom was probably fine before the introduction of

[PATCH 4.9 60/66] bpf: fix bpf_tail_call() x64 JIT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov [ upstream commit 90caccdd8cc0215705f18b92771b449b01e2474a ] - bpf prog_array just like all other types of bpf array accepts 32-bit index. Clarify that in the

[PATCH] iio/pressure: Delete an error message for a failed memory allocation in hid_press_probe()

From: Markus Elfring Date: Mon, 29 Jan 2018 21:55:08 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 4.9 60/66] bpf: fix bpf_tail_call() x64 JIT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov [ upstream commit 90caccdd8cc0215705f18b92771b449b01e2474a ] - bpf prog_array just like all other types of bpf array accepts 32-bit index. Clarify that in the comment. -

[PATCH] iio/pressure: Delete an error message for a failed memory allocation in hid_press_probe()

From: Markus Elfring Date: Mon, 29 Jan 2018 21:55:08 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/iio/pressure/hid-sensor-press.c | 4 +--- 1 file changed, 1

[PATCH 4.4 48/74] Input: trackpoint - force 3 buttons if 0 button is reported

4.4-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.4 48/74] Input: trackpoint - force 3 buttons if 0 button is reported

4.4-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 59/71] vmxnet3: repair memory leak

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Neil Horman [ Upstream commit 848b159835ddef99cc4193083f7e786c3992f580 ] with the introduction of commit b0eb57cb97e7837ebb746404c2c58c6f536f23fa, it appears that

[PATCH 4.14 59/71] vmxnet3: repair memory leak

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Neil Horman [ Upstream commit 848b159835ddef99cc4193083f7e786c3992f580 ] with the introduction of commit b0eb57cb97e7837ebb746404c2c58c6f536f23fa, it appears that rq->buf_info is improperly

[GIT PULL] Btrfs for 4.16

Hi, the btrfs updates for this cycle are mostly cleanups with a few raid56 bugfixes and some feature additions. Please pull, thanks. Features or user visible changes: - fallocate: implement zero range mode - avoid losing data raid profile when deleting a device - tree item checker: more

[GIT PULL] Btrfs for 4.16

Hi, the btrfs updates for this cycle are mostly cleanups with a few raid56 bugfixes and some feature additions. Please pull, thanks. Features or user visible changes: - fallocate: implement zero range mode - avoid losing data raid profile when deleting a device - tree item checker: more

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

On Mon, 2018-01-29 at 12:44 -0800, Arjan van de Ven wrote: > On 1/29/2018 12:42 PM, Eduardo Habkost wrote: > > > > The question is how the hypervisor could tell that to the guest. > > If Intel doesn't give us a CPUID bit that can be used to tell > > that retpolines are enough, maybe we should

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

On Mon, 2018-01-29 at 12:44 -0800, Arjan van de Ven wrote: > On 1/29/2018 12:42 PM, Eduardo Habkost wrote: > > > > The question is how the hypervisor could tell that to the guest. > > If Intel doesn't give us a CPUID bit that can be used to tell > > that retpolines are enough, maybe we should

Re: [PATCH v2 20/43] drm/bridge: analogix_dp: Extend hpd check time to 100ms

On Fri, Jan 26, 2018 at 02:16:47PM +0100, Thierry Escande wrote: > From: Lin Huang > > There was a 1ms delay to detect the hpd signal, which is too short to > detect a short pulse. This patch extends this delay to 100ms. The commit message doesn't align with the code here.

Re: [PATCH v2 20/43] drm/bridge: analogix_dp: Extend hpd check time to 100ms

On Fri, Jan 26, 2018 at 02:16:47PM +0100, Thierry Escande wrote: > From: Lin Huang > > There was a 1ms delay to detect the hpd signal, which is too short to > detect a short pulse. This patch extends this delay to 100ms. The commit message doesn't align with the code here. The code below

[PATCH 4.14 21/71] ARM: net: bpf: clarify tail_call index

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 091f02483df7b56615b524491f404e574c5e0668 upstream. As per 90caccdd8cc0 ("bpf: fix bpf_tail_call() x64 JIT"), the index used for array lookup is

[PATCH 4.14 21/71] ARM: net: bpf: clarify tail_call index

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 091f02483df7b56615b524491f404e574c5e0668 upstream. As per 90caccdd8cc0 ("bpf: fix bpf_tail_call() x64 JIT"), the index used for array lookup is defined to be 32-bit wide.

[PATCH 4.4 45/74] fs/fcntl: f_setown, avoid undefined behaviour

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit fc3dc67471461c0efcb1ed22fb7595121d65fad9 upstream. fcntl(0, F_SETOWN, 0x8000) triggers: UBSAN: Undefined behaviour in fs/fcntl.c:118:7 negation of

[PATCH 4.4 45/74] fs/fcntl: f_setown, avoid undefined behaviour

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit fc3dc67471461c0efcb1ed22fb7595121d65fad9 upstream. fcntl(0, F_SETOWN, 0x8000) triggers: UBSAN: Undefined behaviour in fs/fcntl.c:118:7 negation of -2147483648 cannot be

Re: [PATCH 1/2] media: adv7604: Add support for i2c_new_secondary_device

On Mon, Jan 22, 2018 at 12:49:56PM +, Kieran Bingham wrote: > From: Jean-Michel Hautbois > > The ADV7604 has thirteen 256-byte maps that can be accessed via the main > I²C ports. Each map has it own I²C address and acts as a standard slave > device on the

Re: [PATCH 1/2] media: adv7604: Add support for i2c_new_secondary_device

On Mon, Jan 22, 2018 at 12:49:56PM +, Kieran Bingham wrote: > From: Jean-Michel Hautbois > > The ADV7604 has thirteen 256-byte maps that can be accessed via the main > I²C ports. Each map has it own I²C address and acts as a standard slave > device on the I²C bus. > > Allow a device tree

[PATCH 4.14 09/71] Input: trackpoint - force 3 buttons if 0 button is reported

4.14-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.14 09/71] Input: trackpoint - force 3 buttons if 0 button is reported

4.14-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

[PATCH 4.14 61/71] x86/microcode/intel: Extend BDW late-loading further with LLC size check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit 7e702d17ed138cf4ae7c00e8c00681ed464587c7 upstream. Commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check")

[PATCH 4.14 61/71] x86/microcode/intel: Extend BDW late-loading further with LLC size check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit 7e702d17ed138cf4ae7c00e8c00681ed464587c7 upstream. Commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check") reduced the impact of erratum

[PATCH 3.18 29/52] netfilter: nf_conntrack_sip: extend request line validation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ulrich Weber commit 444f901742d054a4cd5ff045871eac5131646cfb upstream. on SIP requests, so a fragmented TCP SIP packet from an allow header starting with

[PATCH 3.18 29/52] netfilter: nf_conntrack_sip: extend request line validation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ulrich Weber commit 444f901742d054a4cd5ff045871eac5131646cfb upstream. on SIP requests, so a fragmented TCP SIP packet from an allow header starting with

[PATCH 4.9 07/66] can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marc Kleine-Budde commit 8cb68751c115d176ec851ca56ecfbb411568c9e8 upstream. If an invalid CAN frame is received, from a driver or from a tun interface, a Kernel warning is

[PATCH 4.4 29/74] ACPICA: Namespace: fix operand cache leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Seunghun Han commit 3b2d69114fefa474fca542e51119036dceb4aa6f upstream. ACPICA commit a23325b2e583556eae88ed3f764e457786bf4df6 I found some ACPI operand cache leaks in ACPI

[PATCH 4.9 07/66] can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marc Kleine-Budde commit 8cb68751c115d176ec851ca56ecfbb411568c9e8 upstream. If an invalid CAN frame is received, from a driver or from a tun interface, a Kernel warning is generated. This

[PATCH 4.4 29/74] ACPICA: Namespace: fix operand cache leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Seunghun Han commit 3b2d69114fefa474fca542e51119036dceb4aa6f upstream. ACPICA commit a23325b2e583556eae88ed3f764e457786bf4df6 I found some ACPI operand cache leaks in ACPI early abort cases.

[PATCH 4.4 54/74] vsyscall: Fix permissions for emulate mode with KAISER/PTI

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of KAISER to 4.4 turned vsyscall emulate mode into native mode. Add a vsyscall_pgprot variable to hold the correct page protections,

[PATCH 4.4 54/74] vsyscall: Fix permissions for emulate mode with KAISER/PTI

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of KAISER to 4.4 turned vsyscall emulate mode into native mode. Add a vsyscall_pgprot variable to hold the correct page protections, like Borislav and Hugh did for

[PATCH 3.18 47/52] sctp: do not allow the v4 socket to bind a v4mapped v6 address

3.18-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 47/52] sctp: do not allow the v4 socket to bind a v4mapped v6 address

3.18-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 42/52] dccp: dont restart ccid2_hc_tx_rto_expire() if sk in closed state

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit dd5684ecae3bd8e44b644f50e2c12c7e57fdfef5 ] ccid2_hc_tx_rto_expire() timer callback always restarts the timer again and can run

[PATCH 3.18 42/52] dccp: dont restart ccid2_hc_tx_rto_expire() if sk in closed state

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit dd5684ecae3bd8e44b644f50e2c12c7e57fdfef5 ] ccid2_hc_tx_rto_expire() timer callback always restarts the timer again and can run indefinitely (unless it is

[PATCH 4.4 69/74] sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit a0ff660058b88d12625a783ce9e5c1371c87951f ] After commit cea0cc80a677 ("sctp: use the right sk after waking up from wait_buf sleep"), it may

[PATCH 4.4 69/74] sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit a0ff660058b88d12625a783ce9e5c1371c87951f ] After commit cea0cc80a677 ("sctp: use the right sk after waking up from wait_buf sleep"), it may change to lock another

Re: [PATCH v3 bpf] bpf: introduce BPF_JIT_ALWAYS_ON config

On Mon, Jan 29, 2018 at 12:40:47AM +0100, Daniel Borkmann wrote: > On 01/28/2018 03:45 PM, Greg KH wrote: > > On Wed, Jan 24, 2018 at 11:10:50AM +0100, Daniel Borkmann wrote: > >> On 01/24/2018 11:07 AM, David Woodhouse wrote: > >>> On Tue, 2018-01-09 at 22:39 +0100, Daniel Borkmann wrote: >

[PATCH 4.14 16/71] ARM: net: bpf: fix stack alignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit d1220efd23484c72c82d5471f05daeb35b5d1916 upstream. As per 2dede2d8e925 ("ARM EABI: stack pointer must be 64-bit aligned after a CPU exception")

Re: [PATCH v3 bpf] bpf: introduce BPF_JIT_ALWAYS_ON config

On Mon, Jan 29, 2018 at 12:40:47AM +0100, Daniel Borkmann wrote: > On 01/28/2018 03:45 PM, Greg KH wrote: > > On Wed, Jan 24, 2018 at 11:10:50AM +0100, Daniel Borkmann wrote: > >> On 01/24/2018 11:07 AM, David Woodhouse wrote: > >>> On Tue, 2018-01-09 at 22:39 +0100, Daniel Borkmann wrote: >

[PATCH 4.14 16/71] ARM: net: bpf: fix stack alignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit d1220efd23484c72c82d5471f05daeb35b5d1916 upstream. As per 2dede2d8e925 ("ARM EABI: stack pointer must be 64-bit aligned after a CPU exception") the stack should be aligned

[PATCH 4.4 16/74] drivers: base: cacheinfo: fix boot error message when acpi is enabled

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit 55877ef45fbd7f975d078426866b7d1a2435dcc3 upstream. ARM64 enables both CONFIG_OF and CONFIG_ACPI and the firmware can pass both ACPI tables and the

[PATCH 4.4 52/74] usbip: prevent leaking socket pointer address in messages

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit 90120d15f4c397272aaf41077960a157fc4212bf upstream. usbip driver is leaking socket pointer address in messages. Remove the messages that aren't useful

[PATCH 4.4 16/74] drivers: base: cacheinfo: fix boot error message when acpi is enabled

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit 55877ef45fbd7f975d078426866b7d1a2435dcc3 upstream. ARM64 enables both CONFIG_OF and CONFIG_ACPI and the firmware can pass both ACPI tables and the device tree. Based on the

[PATCH 4.4 52/74] usbip: prevent leaking socket pointer address in messages

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit 90120d15f4c397272aaf41077960a157fc4212bf upstream. usbip driver is leaking socket pointer address in messages. Remove the messages that aren't useful and print sockfd in the

[PATCH 4.14 65/71] bpf: introduce BPF_JIT_ALWAYS_ON config

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov [ upstream commit 290af86629b25ffd1ed6232c4e9107da031705cb ] The BPF interpreter has been used as part of the spectre 2 attack CVE-2017-5715. A quote from

[PATCH 4.14 65/71] bpf: introduce BPF_JIT_ALWAYS_ON config

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov [ upstream commit 290af86629b25ffd1ed6232c4e9107da031705cb ] The BPF interpreter has been used as part of the spectre 2 attack CVE-2017-5715. A quote from goolge project

[PATCH 4.9 39/66] net: qdisc_pkt_len_init() should be more robust

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7c68d1a6b4db9012790af7ac0f0fdc0d2083422a ] Without proper validation of DODGY packets, we might very well feed qdisc_pkt_len_init() with

[PATCH 4.9 39/66] net: qdisc_pkt_len_init() should be more robust

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7c68d1a6b4db9012790af7ac0f0fdc0d2083422a ] Without proper validation of DODGY packets, we might very well feed qdisc_pkt_len_init() with invalid GSO packets.

[PATCH 4.9 18/66] ACPI / scan: Prefer devices without _HID/_CID for _ADR matching

4.9-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.9 18/66] ACPI / scan: Prefer devices without _HID/_CID for _ADR matching

4.9-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 4.9 38/66] net: igmp: fix source address check for IGMPv3 reports

4.9-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 38/66] net: igmp: fix source address check for IGMPv3 reports

4.9-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 56/66] perf/x86/amd/power: Do not load AMD power module on !AMD platforms

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xiao Liang commit 40d4071ce2d20840d224b4a77b5dc6f752c9ab15 upstream. The AMD power module can be loaded on non AMD platforms, but unload fails with the following Oops:

[PATCH 4.9 56/66] perf/x86/amd/power: Do not load AMD power module on !AMD platforms

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xiao Liang commit 40d4071ce2d20840d224b4a77b5dc6f752c9ab15 upstream. The AMD power module can be loaded on non AMD platforms, but unload fails with the following Oops: BUG: unable to handle

[PATCH 4.4 68/74] sctp: do not allow the v4 socket to bind a v4mapped v6 address

4.4-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 4.4 68/74] sctp: do not allow the v4 socket to bind a v4mapped v6 address

4.4-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 45/52] net: qdisc_pkt_len_init() should be more robust

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7c68d1a6b4db9012790af7ac0f0fdc0d2083422a ] Without proper validation of DODGY packets, we might very well feed qdisc_pkt_len_init() with

[PATCH 3.18 45/52] net: qdisc_pkt_len_init() should be more robust

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7c68d1a6b4db9012790af7ac0f0fdc0d2083422a ] Without proper validation of DODGY packets, we might very well feed qdisc_pkt_len_init() with invalid GSO packets.

[PATCH 3.18 48/52] sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit a0ff660058b88d12625a783ce9e5c1371c87951f ] After commit cea0cc80a677 ("sctp: use the right sk after waking up from wait_buf sleep"), it may

[PATCH 3.18 48/52] sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit a0ff660058b88d12625a783ce9e5c1371c87951f ] After commit cea0cc80a677 ("sctp: use the right sk after waking up from wait_buf sleep"), it may change to lock another

[PATCH 4.9 24/66] fs/fcntl: f_setown, avoid undefined behaviour

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit fc3dc67471461c0efcb1ed22fb7595121d65fad9 upstream. fcntl(0, F_SETOWN, 0x8000) triggers: UBSAN: Undefined behaviour in fs/fcntl.c:118:7 negation of

[PATCH 4.9 24/66] fs/fcntl: f_setown, avoid undefined behaviour

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit fc3dc67471461c0efcb1ed22fb7595121d65fad9 upstream. fcntl(0, F_SETOWN, 0x8000) triggers: UBSAN: Undefined behaviour in fs/fcntl.c:118:7 negation of -2147483648 cannot be

[PATCH 4.4 20/74] fs/select: add vmalloc fallback for select(2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit 2d19309cf86883f634a4f8ec55a54bda87db19bf upstream. The select(2) syscall performs a kmalloc(size, GFP_KERNEL) where size grows with the number of fds

[PATCH 4.4 20/74] fs/select: add vmalloc fallback for select(2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit 2d19309cf86883f634a4f8ec55a54bda87db19bf upstream. The select(2) syscall performs a kmalloc(size, GFP_KERNEL) where size grows with the number of fds passed. We had a

[PATCH 4.9 05/66] usbip: Fix implicit fallthrough warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Dieter commit cfd6ed4537a9e938fa76facecd4b9cd65b6d1563 upstream. GCC 7 now warns when switch statements fall through implicitly, and with -Werror enabled in

[PATCH 4.4 09/74] can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marc Kleine-Budde commit 8cb68751c115d176ec851ca56ecfbb411568c9e8 upstream. If an invalid CAN frame is received, from a driver or from a tun interface, a Kernel warning is

[PATCH 4.9 05/66] usbip: Fix implicit fallthrough warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Dieter commit cfd6ed4537a9e938fa76facecd4b9cd65b6d1563 upstream. GCC 7 now warns when switch statements fall through implicitly, and with -Werror enabled in configure.ac, that makes

[PATCH 4.4 09/74] can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marc Kleine-Budde commit 8cb68751c115d176ec851ca56ecfbb411568c9e8 upstream. If an invalid CAN frame is received, from a driver or from a tun interface, a Kernel warning is generated. This

[PATCH 4.4 46/74] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

4.4-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 4.4 46/74] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

4.4-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.4 47/74] Revert "module: Add retpoline tag to VERMAGIC"

4.4-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

[PATCH 4.9 14/66] hwpoison, memcg: forcibly uncharge LRU pages

4.9-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

[PATCH 4.4 47/74] Revert "module: Add retpoline tag to VERMAGIC"

4.4-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.9 14/66] hwpoison, memcg: forcibly uncharge LRU pages

4.9-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.4 05/74] x86/microcode/intel: Fix BDW late-loading revision check

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check") to 4.4-stable deleted a "return true"

[PATCH 4.4 05/74] x86/microcode/intel: Fix BDW late-loading revision check

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check") to 4.4-stable deleted a "return true" statement. This bug is not

[PATCH 3.18 09/52] Input: 88pm860x-ts - fix child-node lookup

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 906bf7daa0618d0ef39f4872ca42218c29a3631f upstream. Fix child node-lookup during probe, which ended up searching the whole device tree depth-first

[PATCH 3.18 09/52] Input: 88pm860x-ts - fix child-node lookup

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 906bf7daa0618d0ef39f4872ca42218c29a3631f upstream. Fix child node-lookup during probe, which ended up searching the whole device tree depth-first starting at parent rather

[PATCH 4.9 25/66] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

4.9-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 4.9 25/66] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

4.9-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 3.18 40/52] x86/microcode/intel: Extend BDW late-loading further with LLC size check

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit 7e702d17ed138cf4ae7c00e8c00681ed464587c7 upstream. Commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check")

[PATCH 3.18 40/52] x86/microcode/intel: Extend BDW late-loading further with LLC size check

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit 7e702d17ed138cf4ae7c00e8c00681ed464587c7 upstream. Commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check") reduced the impact of erratum

[PATCH 4.4 70/74] vmxnet3: repair memory leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Neil Horman [ Upstream commit 848b159835ddef99cc4193083f7e786c3992f580 ] with the introduction of commit b0eb57cb97e7837ebb746404c2c58c6f536f23fa, it appears that

[PATCH 4.4 70/74] vmxnet3: repair memory leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Neil Horman [ Upstream commit 848b159835ddef99cc4193083f7e786c3992f580 ] with the introduction of commit b0eb57cb97e7837ebb746404c2c58c6f536f23fa, it appears that rq->buf_info is improperly

[PATCH 4.9 31/66] vsyscall: Fix permissions for emulate mode with KAISER/PTI

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of KAISER to 4.4 turned vsyscall emulate mode into native mode. Add a vsyscall_pgprot variable to hold the correct page protections,

[PATCH 4.9 31/66] vsyscall: Fix permissions for emulate mode with KAISER/PTI

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of KAISER to 4.4 turned vsyscall emulate mode into native mode. Add a vsyscall_pgprot variable to hold the correct page protections, like Borislav and Hugh did for

[PATCH 4.14 12/71] KVM: s390: add proper locking for CMMA migration bitmap

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christian Borntraeger commit 1de1ea7efeb9e8543212210e34518b4049ccd285 upstream. Some parts of the cmma migration bitmap is already protected with the kvm->lock (e.g.

[PATCH 4.14 12/71] KVM: s390: add proper locking for CMMA migration bitmap

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christian Borntraeger commit 1de1ea7efeb9e8543212210e34518b4049ccd285 upstream. Some parts of the cmma migration bitmap is already protected with the kvm->lock (e.g. the migration start). On

[PATCH 4.14 47/71] tun: fix a memory leak for tfile->tx_array

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 4df0bfc79904b7169dc77dcce44598b1545721f9 ] tfile->tun could be detached before we close the tun fd, via tun_detach_all(), so it should

[PATCH 4.14 47/71] tun: fix a memory leak for tfile->tx_array

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 4df0bfc79904b7169dc77dcce44598b1545721f9 ] tfile->tun could be detached before we close the tun fd, via tun_detach_all(), so it should not be used to check for

Re: [PATCH RFC 0/6] MIPS: Broadcom eXtended KSEG0/1 support

On 01/26/2018 12:31 AM, Steven J. Hill wrote: > On 01/23/2018 07:47 PM, Florian Fainelli wrote: > > [...] > >> >> Florian Fainelli (6): >> MIPS: Allow board to override TLB initialization >> MIPS: Allow platforms to override mapping/unmapping coherent >> MIPS: BMIPS: Avoid referencing

Re: [PATCH RFC 0/6] MIPS: Broadcom eXtended KSEG0/1 support

On 01/26/2018 12:31 AM, Steven J. Hill wrote: > On 01/23/2018 07:47 PM, Florian Fainelli wrote: > > [...] > >> >> Florian Fainelli (6): >> MIPS: Allow board to override TLB initialization >> MIPS: Allow platforms to override mapping/unmapping coherent >> MIPS: BMIPS: Avoid referencing

[PATCH 3.18 18/52] arm64: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit acfb3b883f6d6a4b5d27ad7fdded11f6a09ae6dd upstream. KVM doesn't follow the SMCCC when it comes to unimplemented calls, and inject an UNDEF instead of

[PATCH 4.14 40/71] {net,ib}/mlx5: Dont disable local loopback multicast traffic when needed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eran Ben Elisha [ Upstream commit 8978cc921fc7fad3f4d6f91f1da01352aeeeff25 ] There are systems platform information management interfaces (such as HOST2BMC) for which we

[PATCH 3.18 18/52] arm64: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit acfb3b883f6d6a4b5d27ad7fdded11f6a09ae6dd upstream. KVM doesn't follow the SMCCC when it comes to unimplemented calls, and inject an UNDEF instead of returning an error.

[PATCH 4.14 40/71] {net,ib}/mlx5: Dont disable local loopback multicast traffic when needed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eran Ben Elisha [ Upstream commit 8978cc921fc7fad3f4d6f91f1da01352aeeeff25 ] There are systems platform information management interfaces (such as HOST2BMC) for which we cannot disable local

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