[PATCH 4.9 125/171] perf tests: Fix indexing when invoking subtests

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aa90f9f9554616d5738f7bedb4a8f0e5e14d1bc6 ] Recently, the subtest numbering was changed to start from 1. While it is fine for displaying results, this should not be the case when the

[PATCH 4.9 124/171] xhci: Fix USB3 NULL pointer dereference at logical disconnect.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2278446e2b7cd33ad894b32e7eb63afc7db6c86e ] Hub driver will try to disable a USB3 device twice at logical disconnect, racing with xhci_free_dev() callback from the first port disable.

[PATCH 4.9 103/171] Btrfs: incremental send, fix invalid memory access

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24e52b11e0ca788513b945a87b57cc0522a92933 ] When doing an incremental send, while processing an extent that changed between the parent and send snapshots and that extent was an inline

[PATCH 4.9 123/171] libertas: call into generic suspend code before turning off power

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f75cdff0b986195413215eb062b7da6586f ] When powering down a SDIO connected card during suspend, make sure to call into the generic lbs_suspend() function before pulling the plug.

[PATCH 4.9 105/171] module: fix DEBUG_SET_MODULE_RONX typo

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4d217a5adccf5e806790c37c61cc374a08bd7381 ] The newly added 'rodata_enabled' global variable is protected by the wrong #ifdef, leading to a link error when

[PATCH 4.9 101/171] i40e: avoid NVM acquire deadlock during NVM update

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 09f79fd49d94cda5837e9bfd0cb32b3b6d9f ] X722 devices use the AdminQ to access the NVM, and this requires taking the AdminQ lock. Because of this, we lock the AdminQ during

[PATCH 4.9 110/171] cifs: Use ULL suffix for 64-bit constant

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3995bbf53bd2047f2720c6fdd4bf38f6d942a0c0 ] On 32-bit (e.g. with m68k-linux-gnu-gcc-4.1): fs/cifs/inode.c: In function ‘simple_hashstr’: fs/cifs/inode.c:713: warning: integer

[PATCH 4.9 109/171] perf/core: Fix locking for children siblings group read

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2aeb1883547626d82c597cce2c99f0b9c62e2425 ] We're missing ctx lock when iterating children siblings within the perf_read path for group reading. Following race and crash can happen:

[PATCH 4.9 142/171] net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel [ Upstream commit 30549aab146ccb1275230c3b4b4bc6b4181fd54e ] When building stmmac, it is only possible to select CONFIG_DWMAC_GENERIC, or any of the glue drivers, when

[PATCH 4.9 107/171] l2tp: remove configurable payload offset

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 900631ee6a2651dc4fbaecb8ef9fa5f1e3378853 ] If L2TP_ATTR_OFFSET is set to a non-zero value in L2TPv3 tunnels, it results in L2TPv3 packets being transmitted which might not be

[PATCH 4.4 083/114] MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68fe55680d0f3342969f49412fceabb90bdfadba ] Fix a commit 3021773c7c3e ("MIPS: DEC: Avoid la pseudo-instruction in delay slots") regression and remove assembly errors:

[PATCH 4.4 088/114] bridge: do not add port to router list when receives query with source 0.0.0.0

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu commit 5a2de63fd1a59c30c02526d427bc014b98adf508 upstream. Based on RFC 4541, 2.1.1. IGMP Forwarding Rules The switch supporting IGMP snooping must maintain a list of

[PATCH 4.4 093/114] net: sched: gred: pass the right attribute to gred_change_table_def()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit 38b4f18d56372e1e21771ab7b0357b853330186c ] gred_change_table_def() takes a pointer to TCA_GRED_DPS attribute, and expects it will be able to interpret its

[PATCH 4.4 092/114] net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 4ba4c566ba8448a05e6257e0b98a21f1a0d55315 ] The loop wants to skip previously dumped addresses, so loops until current index >= saved index. If the message fills

[PATCH 4.4 089/114] net: bridge: remove ipv6 zero address check in mcast queries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov commit 0fe5119e267f3e3d8ac206895f5922195ec55a8a upstream. Recently a check was added which prevents marking of routers with zero source address, but for IPv6 that cannot

[PATCH 4.4 087/114] perf tools: Disable parallelism for make clean

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit da15fc2fa9c07b23db8f5e479bd8a9f0d741ca07 ] The Yocto build system does a 'make clean' when rebuilding due to changed dependencies, and that consistently fails for me (causing the

[PATCH 4.4 100/114] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit da71577545a52be3e0e9225a946e5fd79cfab015 ] When an FDB entry is configured, the address is validated to have the length of an Ethernet address, but the device

[PATCH 4.4 099/114] vhost: Fix Spectre V1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit ff002269a4ee9c769dbf9365acef633ebcbd6cbe ] The idx in vhost_vring_ioctl() was controlled by userspace, hence a potential exploitation of the Spectre variant 1

[PATCH 4.4 098/114] net: drop skb on failure in ip_check_defrag()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 7de414a9dd91426318df7b63da024b2b07e53df5 ] Most callers of pskb_trim_rcsum() simply drop the skb when it fails, however, ip_check_defrag() still continues to pass

[PATCH 4.4 097/114] sctp: fix race on sctp_id2asoc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit b336decab22158937975293aea79396525f92bb3 ] syzbot reported an use-after-free involving sctp_id2asoc. Dmitry Vyukov helped to root cause it and it is

[PATCH 4.4 094/114] net: socket: fix a missing-check bug

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit b6168562c8ce2bd5a30e213021650422e08764dc ] In ethtool_ioctl(), the ioctl command 'ethcmd' is checked through a switch statement to see whether it is necessary to

[PATCH 4.4 091/114] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit ee1abcf689353f36d9322231b4320926096bdee0 ] Commit a61bbcf28a8c ("[NET]: Store skb->timestamp as offset to a base timestamp") introduces a neighbour control

[PATCH 4.4 053/114] fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 61c12b49e1c9c77d7a1bcc161de540d0fd21cf0c ] Commit 8fba54aebbdf ("fuse: direct-io: don't dirty ITER_BVEC pages") fixes the ITER_BVEC page deadlock for direct io in fuse by checking in

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, Nov 08, 2018 at 05:19:47PM -0500, Theodore Y. Ts'o wrote: > On Thu, Nov 08, 2018 at 01:04:49PM -0800, Greg KH wrote: > > > (Also note that even with fast SSD's and/or everything in page cache, > > > runnning "tag --contains " will take a good 3-4 seconds, and > > > if the git packs are not

[PATCH 4.4 038/114] aacraid: Start adapter after updating number of MSIX vectors

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 116d77fea02e2a5aded7d29ba4c692774cb339f1 ] The adapter has to be started after updating the number of MSIX Vectors Fixes: ecc479e00db8 (aacraid: Set correct MSIX count for EEH

[PATCH 4.4 057/114] ixgbe: fix RSS limit for X550

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e9ee3238f8a480bbca58e51d02a93628d7c1f265 ] X550 allows for up to 64 RSS queues, but the driver can have max of 63 (-1 MSIX vector for link). On systems with >= 64 CPUs the driver

[PATCH 4.4 056/114] net/mlx5e: Correctly handle RSS indirection table when changing number of channels

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 85082dba0a5059c538cfa786d07f5ec5370d22fe ] Upon changing num_channels, reset the RSS indirection table to match the new value. Fixes: 2d75b2bc8a8c ('net/mlx5e: Add ethtool RSS

[PATCH 4.4 055/114] net/mlx5e: Fix LRO modify

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ab0394fe2c258fdb5086c51a251b28f8ee7ab35c ] Ethtool LRO enable/disable is broken, as of today we only modify TCP TIRs in order to apply the requested configuration. Hardware requires

[PATCH 4.4 017/114] perf/ring_buffer: Prevent concurent ring buffer access

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cd6fb677ce7e460c25bdd66f689734102ec7d642 ] Some of the scheduling tracepoints allow the perf_tp_event code to write to ring buffer under different cpu than the code is running on.

[PATCH 4.4 049/114] sch_red: update backlog as well

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7f4f332f082c4d4ba53582f902ed6b44fd6f45e ] Fixes: 2f5fb43f ("net_sched: update hierarchical backlog too") Cc: Jamal Hadi Salim Signed-off-by: Cong Wang Signed-off-by: David S.

[PATCH 4.4 061/114] gro: Allow tunnel stacking in the case of FOU/GUE

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c3483384ee511ee2af40b4076366cd82a6a47b86 ] This patch should fix the issues seen with a recent fix to prevent tunnel-in-tunnel frames from being generated with GRO. The fix itself

[PATCH 4.4 060/114] vti6: flush x-netns xfrm cache when vti interface is removed

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7f92083eb58f85ea114d97f65fcbe22be5b0468d ] This is the same fix than commit a5d0dc810abf ("vti: flush x-netns xfrm cache when vti interface is removed") This patch fixes a refcnt

[PATCH 4.4 062/114] brcmfmac: Fix glom_skb leak in brcmf_sdiod_recv_chain

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5ea59db8a375216e6c915c5586f556766673b5a7 ] An earlier change to this function (3bdae810721b) fixed a leak in the case of an unsuccessful call to brcmf_sdiod_buffrw(). However, the

[PATCH 4.4 054/114] ixgbevf: Fix handling of NAPI budget when multiple queues are enabled per vector

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d0f71afffa1c3d5a36a4a278f1dbbd2643176dc3 ] This is the same patch as for ixgbe but applied differently according to busy polling. See commit 5d6002b7b822c74 ("ixgbe: Fix handling of

[PATCH 3.18 132/144] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit ee1abcf689353f36d9322231b4320926096bdee0 ] Commit a61bbcf28a8c ("[NET]: Store skb->timestamp as offset to a base timestamp") introduces a neighbour control

[PATCH 3.18 112/144] perf: Fix PERF_EVENT_IOC_PERIOD deadlock

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 642c2d671ceff40e9453203ea0c66e991e11e249 ] Dmitry reported a fairly silly recursive lock deadlock for PERF_EVENT_IOC_PERIOD, fix this by explicitly doing the inactive part of

[PATCH 3.18 111/144] libata: blacklist Micron 500IT SSD with MU01 firmware

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 136d769e0b3475d71350aa3648a116a6ee7a8f6c ] While whitelisting Micron M500DC drives, the tweaked blacklist entry enabled queued TRIM from M500IT variants also. But these do not

[PATCH 3.18 110/144] igb: Unpair the queues when changing the number of queues

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 37a5d163fb447b39f7960d0534de30e88ad395bb ] By the commit 72ddef0506da ("igb: Fix oops caused by missing queue pairing"), the IGB_FLAG_QUEUE_PAIRS flag can now be set when changing

[GIT PULL] xfs: fixes for v4.20-rc2

Hi Linus, Here's the start of the stabilization fixes for 4.20. Let me know if there are any problems merging; I just did it against current master and saw no issues. --D The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a: Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

[PATCH 3.18 108/144] tty: audit: Fix audit source

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6b2a3d628aa752f0ab825fc6d4d07b09e274d1c1 ] The data to audit/record is in the 'from' buffer (ie., the input read buffer). Fixes: 72586c6061ab ("n_tty: Fix auditing support for

[PATCH 3.18 085/144] x86/irq: Check for valid irq descriptor in check_irq_vectors_for_cpu_disable()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d97eb8966c91f2c9d05f0a22eb89ed5b76d966d1 ] When an interrupt is migrated away from a cpu it will stay in its vector_irq array until smp_irq_move_cleanup_interrupt succeeded. The

[PATCH 3.18 076/144] perf tools: Avoid build splat for syscall numbers with uclibc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ea1fe3a88763d4dfef7e2529ba606f96e8e6b271 ] This is due to duplicated unistd inclusion (via uClibc headers + kernel headers) Also seen on ARM uClibc based tools --- ARC build

[PATCH 3.18 099/144] dm9000: Fix irq trigger type setup on non-dt platforms

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a96d3b7593a3eefab62dd930e5c99201c3678ee4 ] Commit b5a099c67a1c36b "net: ethernet: davicom: fix devicetree irq resource" causes an interrupt storm after the ethernet interface is

[PATCH 3.18 024/144] xfrm: validate template mode

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32bf94fb5c2ec4ec842152d0e5937cd4bb6738fa ] XFRM mode parameters passed as part of the user templates in the IP_XFRM_POLICY are never properly validated. Passing values other than

[PATCH 3.18 000/144] 3.18.125-stable review

This is the start of the stable review cycle for the 3.18.125 release. There are 144 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 Sat Nov 10 21:50:17 UTC 2018. Anything

[PATCH 3.18 023/144] ARM: 8799/1: mm: fix pci_ioremap_io() offset check

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a58ac65e2d7969bcdf1b6acb70fa4d12a88e53e ] IO_SPACE_LIMIT is the ending address of the PCI IO space, i.e something like 0xf (and not 0x10). Therefore, when offset = 0xf

[PATCH 3.18 012/144] team: Forbid enslaving team device to itself

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 471b83bd8bbe4e89743683ef8ecb78f7029d8288 ] team's ndo_add_slave() acquires 'team->lock' and later tries to open the newly enslaved device via dev_open(). This

[PATCH 3.18 007/144] ip_tunnel: be careful when accessing the inner header

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit ccfec9e5cb2d48df5a955b7bf47f7782157d3bc2] Cong noted that we need the same checks introduced by commit 76c0ddd8c3a6 ("ip6_tunnel: be careful when accessing the

[PATCH 3.18 004/144] mach64: detect the dot clock divider correctly on sparc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 76ebebd2464c5c8a4453c98b6dbf9c95a599e810 upstream. On Sun Ultra 5, it happens that the dot clock is not set up properly for some videomodes. For example, if we set the

[PATCH 3.18 003/144] stmmac: fix valid numbers of unicast filter entries

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jongsung Kim [ Upstream commit edf2ef7242805e53ec2e0841db26e06d8bc7da70 ] Synopsys DWC Ethernet MAC can be configured to have 1..32, 64, or 128 unicast filter entries. (Table 7-8 MAC Address

RE: [PATCH 21/23] dt-bindings: pci: Add NXP LX SoCs PCIe controller

> -Original Message- > From: Z.q. Hou > Sent: Tuesday, November 6, 2018 7:21 AM > To: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; > bhelg...@google.com; robh...@kernel.org; mark.rutl...@arm.com; >

Re: [PATCH 00/12] Series short description

On Mon, Nov 05, 2018 at 12:30:47PM +1100, NeilBrown wrote: > Here is the respin on this series with the file_lock properly > initlized for unlock requests. > I found one that I had missed before - in locks_remove_flock() > The change makes this code smaller! > > Original series description: > >

[PATCH 3.18 123/144] USB: hub: fix up early-exit pathway in hub_activate

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ca5cbc8b02f9b21cc8cd1ab36668763ec34f9ee8 ] The early-exit pathway in hub_activate, added by commit e50293ef9775 ("USB: fix invalid memory access in hub_activate()") needs

[PATCH 4.4 023/114] tracing: Skip more functions when doing stack tracing of events

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit be54f69c26193de31053190761e521903b89d098 ] # echo 1 > options/stacktrace # echo 1 > events/sched/sched_switch/enable # cat trace -0 [002] d..2 1982.525169: =>

[PATCH 4.4 026/114] btrfs: cleaner_kthread() doesnt need explicit freeze

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 838fe1887765f4cc679febea60d87d2a06bd300e ] cleaner_kthread() is not marked freezable, and therefore calling try_to_freeze() in its context is a pointless no-op. In addition to that,

[PATCH 4.4 025/114] x86/mm/pat: Prevent hang during boot when mapping pages

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e535ec0899d1fe52ec3a84c9bc03457ac67ad6f7 ] There's a mixture of signed 32-bit and unsigned 32-bit and 64-bit data types used for keeping track of how many pages have been mapped.

[PATCH 4.4 008/114] Bluetooth: SMP: fix crash in unpairing

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cb28c306b93b71f2741ce1a5a66289db26715f4d ] In case unpair_device() was called through mgmt interface at the same time when pairing was in progress, Bluetooth kernel module crash was

[PATCH 4.4 006/114] xfrm: validate template mode

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32bf94fb5c2ec4ec842152d0e5937cd4bb6738fa ] XFRM mode parameters passed as part of the user templates in the IP_XFRM_POLICY are never properly validated. Passing values other than

[PATCH 4.4 005/114] ARM: 8799/1: mm: fix pci_ioremap_io() offset check

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a58ac65e2d7969bcdf1b6acb70fa4d12a88e53e ] IO_SPACE_LIMIT is the ending address of the PCI IO space, i.e something like 0xf (and not 0x10). Therefore, when offset = 0xf

[PATCH 4.4 010/114] asix: Check for supported Wake-on-LAN modes

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c4ce446e33d7a0e978256ac6fea4c80e59d9de5f ] The driver currently silently accepts unsupported Wake-on-LAN modes (other than WAKE_PHY or WAKE_MAGIC) without reporting that to the user,

[PATCH 4.4 007/114] mac80211_hwsim: do not omit multicast announce of first added radio

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 28ef8b49a338dc1844e86b7954cfffc7dfa2660a ] The allocation of hwsim radio identifiers uses a post-increment from 0, so the first radio has idx 0. This idx is explicitly excluded from

[PATCH 4.4 003/114] mac80211: Always report TX status

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8682250b3c1b75a45feb7452bc413d004cfe3778 ] If a frame is dropped for any reason, mac80211 wouldn't report the TX status back to user space. As the user space may rely on the

[PATCH 3.18 129/144] /proc/iomem: only expose physical resource addresses to privileged users

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 51d7b120418e99d6b3bf8df9eb3cc31e8171dee4 upstream. In commit c4004b02f8e5b ("x86: remove the kernel code/data/bss resources from /proc/iomem") I was hoping to remove the

[PATCH 3.18 143/144] USB: fix the usbfs flag sanitization for control transfers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 665c365a77fbfeabe52694aedf3446d5f2f1ce42 upstream. Commit 7a68d9fb8510 ("USB: usbdevfs: sanitize flags more") checks the transfer flags for URBs submitted from userspace via

[PATCH 3.18 128/144] perf tools: Disable parallelism for make clean

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit da15fc2fa9c07b23db8f5e479bd8a9f0d741ca07 ] The Yocto build system does a 'make clean' when rebuilding due to changed dependencies, and that consistently fails for me (causing the

[PATCH 4.18 25/34] tracing: Fix synthetic event to allow semicolon at end

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit a360d9e4016c1fcf41553b37ad496870dc5723d0 upstream. Fix synthetic event to allow independent semicolon at end. The synthetic_events interface accepts a semicolon after

[PATCH 4.18 00/34] 4.18.18-stable review

This is the start of the stable review cycle for the 4.18.18 release. There are 34 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 Sat Nov 10 21:51:21 UTC 2018. Anything

[PATCH 4.18 31/34] x86/percpu: Fix this_cpu_read()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b59167ac7bafd804c91e49ad53c6d33a7394d4c8 upstream. Eric reported that a sequence count loop using this_cpu_read() got optimized out. This is wrong, this_cpu_read() must

[PATCH 4.18 09/34] ptp: fix Spectre v1 vulnerability

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit efa61c8cf2950ab5c0e66cff3cabe2a2b24e81ba upstream. pin_index can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.18 26/34] Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15IGM

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikhail Nikiforov commit 13c1c5e4d7f887cba36c5e3df3faa22071c1469f upstream. Add ELAN061C to the ACPI table to support Elan touchpad found in Lenovo IdeaPad 330-15IGM. Signed-off-by: Mikhail

[PATCH 4.18 33/34] x86/swiotlb: Enable swiotlb for > 4GiG RAM on 32-bit kernels

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 485734f3fc77c1eb77ffe138c027b9a4bf0178f3 upstream. We already build the swiotlb code for 32-bit kernels with PAE support, but the code to actually use swiotlb has

[PATCH 4.18 29/34] x86/tsc: Force inlining of cyc2ns bits

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 4907c68abd3f60f650f98d5a69d4ec77c0bde44f upstream. Looking at the asm for native_sched_clock() I noticed we don't inline enough. Mostly caused by sharing code with

[PATCH 4.18 30/34] x86, hibernate: Fix nosave_regions setup for hibernation

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhimin Gu commit cc55f7537db6af371e9c1c6a71161ee40f918824 upstream. On 32bit systems, nosave_regions(non RAM areas) located between max_low_pfn and max_pfn are not excluded from hibernation

[PATCH 4.18 32/34] x86/time: Correct the attribute on jiffies definition

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nathan Chancellor commit 53c13ba8ed39e89f21a0b98f4c8a241bb44e483d upstream. Clang warns that the declaration of jiffies in include/linux/jiffies.h doesn't match the definition in

[PATCH 4.18 07/34] cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 169b803397499be85bdd1e3d07d6f5e3d4bd669e upstream. the victim might've been rmdir'ed just before the lock_rename(); unlike the normal callers, we do not look the source up

[PATCH 4.18 06/34] fscache: Fix incomplete initialisation of inline key space

4.18-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit 1ff22883b0b2f7a73eb2609ffe879c9fd96f6328 upstream. The inline key in struct rxrpc_cookie is insufficiently initialized, zeroing only 3 of the 4 slots, therefore an

[PATCH 4.18 28/34] sched/fair: Fix throttle_list starvation with low CFS quota

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Phil Auld commit baa9be4ffb55876923dc9716abc0a448e510ba30 upstream. With a very low cpu.cfs_quota_us setting, such as the minimum of 1000, distribute_cfs_runtime may not empty the

[PATCH 4.9 054/171] bnxt_en: Dont use rtnl lock to protect link change logic in workqueue.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e2dc9b6e38fa3919e63d6d7905da70ca41cbf908 ] As a further improvement to the PF/VF link change logic, use a private mutex instead of the rtnl lock to protect link change logic. With

[PATCH 4.9 051/171] net/mlx5: Fix command completion after timeout access invalid structure

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 061870800efb4e3d1ad4082a2569363629bdfcfc ] Completion on timeout should not free the driver command entry structure as it will need to access it again once real completion event from

x86_64 INIT/SIPI Bug

I apologize upfront if this is the wrong place to post this, pretty new to this. We are working on the Bareflank Hypervisor (www.bareflank.org), and we are passing through the INIT/SIPI process (similar to how a VMX rootkit from EFI might boot the OS) and we noticed that on Arch Linux, the

[PATCH 4.9 067/171] ARM: 8677/1: boot/compressed: fix decompressor header layout for v7-M

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 06a4b6d009a1b74a6ec46c5418b46cc53a79fcb8 ] As reported by Patrice, the header layout of the decompressor is incorrect when building for v7-M. In this case, the __nop macro resolves

[PATCH 4.9 052/171] tipc: Fix tipc_sk_reinit handling of -EAGAIN

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6c7e983b220f89e03286dc70a41c7ef3a8b409df ] In 9dbbfb0ab6680c6a85609041011484e6658e7d3c function tipc_sk_reinit had additional logic added to loop in the event that function

[PATCH 4.9 048/171] rxe: Fix a sleep-in-atomic bug in post_one_send

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07d432bb97f19dd5e784175152f9fce3b2646133 ] The driver may sleep under a spin lock, and the function call path is: post_one_send (acquire the lock by spin_lock_irqsave)

[PATCH 4.9 069/171] elevator: fix truncation of icq_cache_name

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9bd2bbc01d17ddd567cc0f81f77fe1163e497462 ] gcc 7.1 reports the following warning: block/elevator.c: In function ‘elv_register’: block/elevator.c:898:5: warning: ‘snprintf’

Re: [PATCH] z3fold: fix wrong handling of headless pages

On Thu, 8 Nov 2018 22:45:40 +0900 Jongseok Kim wrote: > Yes, you are right. > I think that's the best way to deal it. > Thank you. I did this: Link: http://lkml.kernel.org/r/20181105162225.74e8837d03583a9b707cf...@gmail.com Signed-off-by: Vitaly Wool Signed-off-by: Jongseok Kim

[PATCH 4.9 091/171] ALSA: hda - No loopback on ALC299 codec

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fa16b69f1299004b60b625f181143500a246e5cb ] ALC299 has no loopback mixer, but the driver still tries to add a beep control over the mixer NID which leads to the error at accessing it.

[PATCH 4.9 053/171] tipc: fix a race condition of releasing subscriber object

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fd849b7c41f0fabfe783d0691a63c5518e8ebc99 ] No matter whether a request is inserted into workqueue as a work item to cancel a subscription or to delete a subscription's subscriber

[PATCH 4.9 045/171] IB/ipoib: Do not warn if IPoIB debugfs doesnt exist

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 14fa91e0fef8e4d6feb8b1fa2a807828e0abe815 ] netdev_wait_allrefs() could rebroadcast NETDEV_UNREGISTER event multiple times until all refs are gone, which will result in calling

[PATCH 4.9 088/171] ocfs2: fix deadlock caused by recursive locking in xattr

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8818efaaacb78c60a9d90c5705b6c99b75d7d442 ] Another deadlock path caused by recursive locking is reported. This kind of issue was introduced since commit 743b5f1434f5 ("ocfs2: take

[PATCH 4.9 080/171] usb: renesas_usbhs: gadget: fix unused-but-set-variable warning

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b7d44c36a6f6d956e1539e0dd42f98b26e5a4684 ] The commit b8b9c974afee ("usb: renesas_usbhs: gadget: disable all eps when the driver stops") causes the unused-but-set-variable warning.

[PATCH 4.9 050/171] net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c505873eaece2b4aefd07d339dc7e1400e0235ac ] 88E1145 also need this autoneg errata. Fixes: f2899788353c ("net: phy: marvell: Limit errata to 88m1101") Signed-off-by: Zhao Qiang

[PATCH 3.18 074/144] perf machine: Fix __machine__findnew_thread() error path

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 260d819e3abdbdaa2b88fb983d1314f1b263f9e2 ] When thread__init_map_groups() fails, a new thread should be removed from the rbtree since it's gonna be freed. Also update last match

[PATCH 3.18 073/144] perf/x86/intel: Fix bug for "cycles:p" and "cycles:pp" on SLM

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 33636732dcd7cc738a5913bb730d663c6b03c8fb ] cycles:p and cycles:pp do not work on SLM since commit: 86a04461a99f ("perf/x86: Revamp PEBS event selection") UOPS_RETIRED.ALL is

Re: [driver-core PATCH v6 3/9] device core: Consolidate locking and unlocking of parent and device

Hi, Alex, On 11/08/2018 10:06 AM, Alexander Duyck wrote: +/* + * __device_driver_lock - release locks needed to manipulate dev->drv You meant to say __device_driver_unlock, right? + * @dev: Device we will update driver info for + * @parent: Parent device. Needed if the bus requires parent

[PATCH 3.18 075/144] perf tools: Fix statfs.f_type data type mismatch build error with uclibc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit db1806edcfef007d9594435a331dcf7e7f1b8fac ] ARC Linux uses the no legacy syscalls abi and corresponding uClibc headers statfs defines f_type to be U32 which causes perf build

[PATCH 3.18 058/144] arm: dts: Use pmu_system_controller phandle for dp phy

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e93e54544adf3aa6908b821e896cb17a562cb683 ] DP PHY now require pmu-system-controller to handle PMU register to control PHY's power isolation. Adding the same to dp-phy node.

[PATCH 3.18 087/144] Btrfs: avoid syncing log in the fast fsync path when not necessary

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b659ef027792219b590d67a2baf1643a93727d29 ] Commit 3a8b36f37806 ("Btrfs: fix data loss in the fast fsync path") added a performance regression for that causes an unnecessary sync of

[PATCH 3.18 059/144] scsi: ->queue_rq cant sleep

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 70a0f2c1898c6abf53670e55642b6e840b003892 ] The blk-mq ->queue_rq method is always called from process context, but might have preemption disabled. This means we still always have

[PATCH 3.18 054/144] NFSv4: Cache the NFSv4/v4.1 client owner_id in the struct nfs_client

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ceb3a16c070c403f5f9ca46b46cf2bb79ea11750 ] Ensure that we cache the NFSv4/v4.1 client owner_id so that we can verify it when we're doing trunking detection. Signed-off-by: Trond

[PATCH 3.18 070/144] fbdev/broadsheetfb: fix memory leak

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ef6899cdc8608e2f018e590683f04bb04a069704 ] static code analysis from cppcheck reports: [drivers/video/fbdev/broadsheetfb.c:673]: (error) Memory leak: sector_buffer sector_buffer

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