[PATCH 4.14 67/71] bpf: fix divides by zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit c366287ebd698ef5e3de300d90cd62ee9ee7373e ] Divides by zero are not nice, lets avoid them if possible. Also do_div() seems not needed when dealing with 32bit ope

[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. Sin

[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

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 CKSEG

[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 tfi

[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 t

[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 3.

[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 ha

[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 BDF

[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 (.i.e.

[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.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 present

[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 pa

[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 st

[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 (.i.e.

[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 th

[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 patc

[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 cus

[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 re

[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 s

[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. t

[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 i

[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 k

[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 of

[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 value

[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. tc

[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 ze

[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 o

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: > O

[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 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 sk

[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 stop

[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 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 3.

[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 patc

[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 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 INVITE,NOTIFY,OPTIONS,REFER,REGISTER

[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 BDF

[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 in

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 nod

[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 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. U

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 matches

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 us

[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 check

[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 h

[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.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. - fi

[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 in

[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 ("M

[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.14 25/71] dccp: dont restart ccid2_hc_tx_rto_expire() if sk in closed state

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

[PATCH 4.14 63/71] x86/mm/64: Fix vmapped stack syncing on very-large-memory 4-level systems

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 5beda7d54eafece4c974cfa9fbb9f60fb18fd20a upstream. Neil Berrington reported a double-fault on a VM with 768GB of RAM that uses large amounts of vmalloc space with PTI en

[PATCH 4.4 40/74] netfilter: xt_osf: Add missing permission checks

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

[PATCH 4.9 10/66] Prevent timer value 0 for MWAITX

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Janakarajan Natarajan commit 88d879d29f9cc0de2d930b584285638cdada6625 upstream. Newer hardware has uncovered a bug in the software implementation of using MWAITX for the delay function. A value

[PATCH 4.9 49/66] ppp: unlock all_ppp_mutex before registering device

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault [ Upstream commit 0171c41835591e9aa2e384b703ef9a6ae367c610 ] ppp_dev_uninit(), which is the .ndo_uninit() handler of PPP devices, needs to lock pn->all_ppp_mutex. Therefore we

[PATCH 3.18 14/52] phy: work around phys references to usb-nop-xceiv devices

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit b7563e2796f8b23c98afcfea7363194227fa089d upstream. Stefan Wahren reports a problem with a warning fix that was merged for v4.15: we had lots of device nodes with a 'phys'

[PATCH 3.18 15/52] ARM: dts: kirkwood: fix pin-muxing of MPP7 on OpenBlocks A7

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 56aeb07c914a616ab84357d34f8414a69b140cdf upstream. MPP7 is currently muxed as "gpio", but this function doesn't exist for MPP7, only "gpo" is available. This causes the

[PATCH] arm64: dts: Add DPAA QBMan portal 9

ARM DPAA1 (LS1043 and LS1046) have 10 QBMan portals (indexed 0-9) Enable the one that is missing in the device trees. Signed-off-by: Roy Pledge --- arch/arm64/boot/dts/freescale/qoriq-bman-portals.dtsi | 6 ++ arch/arm64/boot/dts/freescale/qoriq-qman-portals.dtsi | 7 +++ 2 files changed

[PATCH 3.18 37/52] eventpoll.h: add missing epoll event masks

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg KH commit 7e040726850a106587485c21bdacc0bfc8a0cbed upstream. [resend due to me forgetting to cc: linux-api the first time around I posted these back on Feb 23] From: Greg Kroah-Hartman

[PATCH 4.4 42/74] reiserfs: fix race in prealloc discard

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 08db141b5313ac2f64b844fb5725b8d81744b417 upstream. The main loop in __discard_prealloc is protected by the reiserfs write lock which is dropped across schedules like the BKL

[PATCH 4.14 17/71] ARM: net: bpf: move stack documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 70ec3a6c2c11e4b0e107a65de943a082f9aff351 upstream. Move the stack documentation towards the top of the file, where it's relevant for things like the register layout. Signe

[PATCH 4.14 42/71] ppp: unlock all_ppp_mutex before registering device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault [ Upstream commit 0171c41835591e9aa2e384b703ef9a6ae367c610 ] ppp_dev_uninit(), which is the .ndo_uninit() handler of PPP devices, needs to lock pn->all_ppp_mutex. Therefore we

[PATCH 4.4 72/74] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY

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

[PATCH 4.14 64/71] hrtimer: Reset hrtimer cpu base proper on CPU hotplug

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit d5421ea43d30701e03cadc56a38854c36a8b4433 upstream. The hrtimer interrupt code contains a hang detection and mitigation mechanism, which prevents that a long delayed hrti

[PATCH 4.4 10/74] can: af_can: canfd_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 d4689846881d160a4d12a514e991a740bcb5d65a upstream. If an invalid CANFD frame is received, from a driver or from a tun interface, a Kernel warning is generated. This pa

[PATCH 4.9 54/66] tun: fix a memory leak for tfile->tx_array

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

[PATCH 3.18 17/52] dm thin metadata: THIN_MAX_CONCURRENT_LOCKS should be 6

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dennis Yang commit 490ae017f54e55bde382d45ea24bddfb6d1a0aaf upstream. For btree removal, there is a corner case that a single thread could takes 6 locks which is more than THIN_MAX_CONCURRENT_

[PATCH 3.18 08/52] pipe: avoid round_pipe_size() nr_pages overflow on 32-bit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joe Lawrence commit d3f14c485867cfb2e0c48aa88c41d0ef4bf5209c upstream. round_pipe_size() contains a right-bit-shift expression which may overflow, which would cause undefined results in a subs

[PATCH 4.9 32/66] eventpoll.h: add missing epoll event masks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Greg KH commit 7e040726850a106587485c21bdacc0bfc8a0cbed upstream. [resend due to me forgetting to cc: linux-api the first time around I posted these back on Feb 23] From: Greg Kroah-Hartman

Re: [PATCH v6 3/3] platform/chrome: Register cros_ec_accel_legacy driver

On Fri, Jan 19, 2018 at 3:00 AM, Thierry Escande wrote: > > With this patch, the cros_ec_ctl driver will register the legacy > accelerometer driver (named cros_ec_accel_legacy) if it fails to > register sensors through the usual path cros_ec_sensors_register(). > This legacy device is present on C

[PATCH 4.9 50/66] be2net: restore properly promisc mode after queues reconfiguration

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Vecera [ Upstream commit 52acf06451930eb4cefabd5ecea56e2d46c32f76 ] The commit 622190669403 ("be2net: Request RSS capability of Rx interface depending on number of Rx rings") modified be_

[PATCH 3.18 19/52] MIPS: AR7: ensure the port types FCR value is used

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jonas Gorski commit 0a5191efe06b5103909206e4fbcff81d30283f8e upstream. Since commit aef9a7bd9b67 ("serial/uart/8250: Add tunable RX interrupt trigger I/F of FIFO buffers"), the port's default

[PATCH 3.18 21/52] usbip: Fix implicit fallthrough warning

3.18-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 t

[PATCH 3.18 28/52] netfilter: restart search if moved to other chain

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 95a8d19f28e6b29377a880c6264391a62e07fccc upstream. In case nf_conntrack_tuple_taken did not find a conflicting entry check that all entries in this hash slot were teste

[PATCH 4.4 17/74] PCI: layerscape: Add "fsl,ls2085a-pcie" compatible ID

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi commit dbae40b76abef2f8a7e7bf1701f77df9e73def48 upstream. The Layerscape PCI host driver must recognize ls2085a compatible when using firmware with ls2085a compatible property, otherwi

[PATCH 4.9 48/66] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY

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

[PATCH 4.14 34/71] net: vrf: Add support for sends to local broadcast address

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 1e19c4d689dc1e95bafd23ef68fbc0c6b9e05180 ] Sukumar reported that sends to the local broadcast address (255.255.255.255) are broken. Check for the address in vrf

[PATCH 4.14 24/71] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY

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

[PATCH 4.4 14/74] Prevent timer value 0 for MWAITX

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Janakarajan Natarajan commit 88d879d29f9cc0de2d930b584285638cdada6625 upstream. Newer hardware has uncovered a bug in the software implementation of using MWAITX for the delay function. A value

[PATCH 3.18 13/52] Input: twl4030-vibra - fix sibling-node lookup

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 5b189201993ab03001a398de731045bfea90c689 upstream. A helper purported to look up a child node based on its name was using the wrong of-helper and ended up prematurely freei

[PATCH 4.14 41/71] net/mlx5: Fix get vector affinity helper function

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Saeed Mahameed [ Upstream commit 05e0cc84e00c54fb152d1f4b86bc211823a83d0c ] mlx5_get_vector_affinity used to call pci_irq_get_affinity and after reverting the patch that sets the device affin

[PATCH 4.14 23/71] net: Allow neigh contructor functions ability to modify the primary_key

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jim Westfall [ Upstream commit 096b9854c04df86f03b38a97d40b6506e5730919 ] Use n->primary_key instead of pkey to account for the possibility that a neigh constructor function may have modified

Re: [PATCH v2 22/43] drm/bridge: analogix_dp: Check dpcd write/read status

On Fri, Jan 26, 2018 at 02:16:49PM +0100, Thierry Escande wrote: > From: Lin Huang > > We need to check the dpcd write/read return value to see whether the > write/read was successful > > Cc: Kristian H. Kristensen > Signed-off-by: Lin Huang > Signed-off-by: zain wang > Signed-off-by: Douglas

Re: [PATCH v6 01/41] dt-bindings: clock: Add new bindings for TI Davinci PLL clocks

On 01/29/2018 01:53 PM, Rob Herring wrote: On Sat, Jan 20, 2018 at 11:13:40AM -0600, David Lechner wrote: This adds a new binding for the PLL IP blocks in the mach-davinci family of processors. Currently, only da850 has device tree support but these bindings can also work for other SoCs in this

[PATCH 4.9 19/66] ACPICA: Namespace: fix operand cache leak

4.9-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 12/74] time: Avoid undefined behaviour in ktime_add_safe()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vegard Nossum commit 979515c5645830465739254abc1b1648ada41518 upstream. I ran into this: UBSAN: Undefi

[PATCH 4.9 11/66] drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled

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

[PATCH 4.14 48/71] flow_dissector: properly cap thoff field

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

[PATCH 3.18 38/52] um: Stop abusing __KERNEL__

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 298e20ba8c197e8d429a6c8671550c41c7919033 upstream. Currently UML is abusing __KERNEL__ to distinguish between kernel and host code (os-Linux). It is better to use a c

[PATCH 4.9 22/66] reiserfs: fix race in prealloc discard

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 08db141b5313ac2f64b844fb5725b8d81744b417 upstream. The main loop in __discard_prealloc is protected by the reiserfs write lock which is dropped across schedules like the BKL

[PATCH 4.14 62/71] x86/microcode: Fix again accessing initrd after having been freed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 1d080f096fe33f031d26e19b3ef0146f66b8b0f1 upstream. Commit 24c2503255d3 ("x86/microcode: Do not access the initrd after it has been freed") fixed attempts to access initr

[PATCH 4.14 46/71] mlxsw: spectrum_router: Dont log an error on missing neighbor

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yuval Mintz [ Upstream commit 1ecdaea02ca6bfacf2ecda500dc1af51e9780c42 ] Driver periodically samples all neighbors configured in device in order to update the kernel regarding their state. Wh

[PATCH 3.18 20/52] x86/asm/32: Make sync_core() handle missing CPUID on all 32-bit kernels

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 1c52d859cb2d417e7216d3e56bb7fea88444cec9 upstream. We support various non-Intel CPUs that don't have the CPUID instruction, so the M486 test was wrong. For now, fix it

[PATCH 4.4 39/74] netfilter: nfnetlink_cthelper: Add missing permission checks

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

[PATCH 4.14 38/71] sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf

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

[PATCH 4.14 33/71] net/tls: Fix inverted error codes to avoid endless loop

4.14-stable review patch. If anyone has any objections, please let me know. -- From: "r.her...@avm.de" [ Upstream commit 30be8f8dba1bd2aff73e8447d59228471233a3d4 ] sendfile() calls can hang endless with using Kernel TLS if a socket error occurs. Socket error codes must be in

[PATCH 4.4 55/74] eventpoll.h: add missing epoll event masks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg KH commit 7e040726850a106587485c21bdacc0bfc8a0cbed upstream. [resend due to me forgetting to cc: linux-api the first time around I posted these back on Feb 23] From: Greg Kroah-Hartman

[PATCH 3.18 03/52] futex: Prevent overflow by strengthen input validation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Li Jinyue commit fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a upstream. UBSAN reports signed integer overflow in kernel/futex.c: UBSAN: Undefined behaviour in kernel/futex.c:2041:18 signed inte

<    3   4   5   6   7   8   9   10   11   >