[PATCH 3.18 056/144] NFS: Ignore transport protocol when detecting server trunking

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a01edf0058df98d6cc734c5a4ecc51f929a86ec ] Detect server trunking across transport protocols. Otherwise, an RDMA mount and a TCP mount of the same server will end up with separate

[PATCH 3.18 068/144] ARM: at91/dt: sam9263: Add missing clocks to lcdc node

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 55eb9c343fdd3611ae3de6ab8a8512f303d3f581 ] atmel_lcdfb needs also uses hclk clock, but AT91SAM9263 doesn't have that specific clock, so use lcd_clk twice. The same was done in

[PATCH 3.18 071/144] tracing: Fix enabling of syscall events on the command line

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce1039bd3a89e99e4f624e75fb1777fc92d76eb3 ] Commit 5f893b2639b2 "tracing: Move enabling tracepoints to just after rcu_init()" broke the enabling of system call events from the

[PATCH 3.18 055/144] NFSv4/v4.1: Verify the client owner id during trunking detection

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 55b9df93ddd684cbc4c2dee9b8a99f6e48348212 ] While we normally expect the NFSv4 client to always send the same client owner to all servers, there are a couple of situations where that

Re: [PATCH v5 16/17] tpm: take TPM chip power gating out of tpm_transmit()

On Thu, Nov 08, 2018 at 06:38:59PM +, Winkler, Tomas wrote: > > Call tpm_chip_start() and tpm_chip_stop() in > > > > * tpm_try_get_ops() and tpm_put_ops() > > * tpm_chip_register() > > * tpm2_del_space() > > > > And remove these calls from tpm_transmit(). The core reason for this change > >

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 02:42:55PM -0800, Greg Kroah-Hartman wrote: > On Thu, Nov 08, 2018 at 03:32:58PM -0700, Keith Busch wrote: > > On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > > > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > > > I'm having second

Re: [PATCH v5 09/17] tpm: move tpm_validate_commmand() to tpm2-space.c

On Thu, Nov 08, 2018 at 05:03:29PM +, Winkler, Tomas wrote: > You initialized cc under if only > > + > > + i = tpm2_find_cc(chip, cc); > > + if (i < 0) { > > + dev_dbg(>dev, "0x%04X is an invalid > > command\n", > > + cc); > > +

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

On Thu, Nov 08, 2018 at 01:50:41PM -0800, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > [ Upstream commit 838fe1887765f4cc679febea60d87d2a06bd300e ] Please check the discussion under

[PATCH net-next v2 2/2] net: phy: remove flag PHY_HAS_INTERRUPT from driver configs

Now that flag PHY_HAS_INTERRUPT has been replaced with a check for callbacks config_intr and ack_interrupt, we can remove setting this flag from all driver configs. Last but not least remove flag PHY_HAS_INTERRUPT completely. Signed-off-by: Heiner Kallweit --- v2: - remove flag from all driver

Re: [PATCH v4 12/18] arm64: dts: qcom: pms405: add gpios

On Thu, Nov 8, 2018 at 12:41 PM Vinod Koul wrote: > > Add the GPIOs present on PMS405 chip. > > Signed-off-by: Vinod Koul > --- > arch/arm64/boot/dts/qcom/pms405.dtsi | 19 +++ > 1 file changed, 19 insertions(+) > > diff --git a/arch/arm64/boot/dts/qcom/pms405.dtsi >

[PATCH 3.18 034/144] s390/kvm: REPLACE barrier fixup with READ_ONCE

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5de72a2247ac05bde7c89039631b3d0c6186fafb ] ACCESS_ONCE does not work reliably on non-scalar types. For example gcc 4.6 and 4.7 might remove the volatile tag for such accesses during

[PATCH 3.18 038/144] mmc: sdhci: restore behavior when setting VDD via external regulator

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 918f4cbd4340ddd1eb389cd8efa3b07ac74ec4c0 ] After commit 52221610dd84 ("mmc: sdhci: Improve external VDD regulator support"), for the VDD is supplied via external regulators, we

[PATCH 3.18 049/144] phy-sun4i-usb: Change disconnect threshold value for sun6i

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 372400344afb60e275a271f3f5ccce17af0e45cb ] The allwinner SDK uses a value of 3 for the disconnect threshold setting on sun6i, do the same in the kernel. In my previous experience

[PATCH 3.18 048/144] usb: dwc2: gadget: kill requests with force in s3c_hsotg_udc_stop()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 62f4f0651ce8ef966a0e5b6db6a7a524c268fdd2 ] This makes us sure that all requests are completed before we unbind gadget. There are assumptions in gadget API that all requests have to

[PATCH 3.18 019/144] powerpc/tm: Avoid possible userspace r1 corruption on reclaim

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling [ Upstream commit 96dc89d526ef77604376f06220e3d2931a0bfd58 ] Current we store the userspace r1 to PACATMSCRATCH before finally saving it to the thread struct. In theory an

[PATCH 3.18 017/144] media: af9035: prevent buffer overflow on write

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jozef Balga [ Upstream commit 312f73b648626a0526a3aceebb0a3192aaba05ce ] When less than 3 bytes are written to the device, memcpy is called with negative array size which leads to buffer

[PATCH 3.18 047/144] usb: musb: Fix randconfig build issues for Kconfig options

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c0442479652b99b62dd1ffccb34231caff25751c ] Commit 82c02f58ba3a ("usb: musb: Allow multiple glue layers to be built in") enabled selecting multiple glue layers, which in turn exposed

[PATCH 3.18 039/144] usb: gadget: gadgetfs: fix an oops in ep_write()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 42d6cfa0caec4b68a7f17147fbf13a36e94a8bf2 ] We try to free an ERR_PTR on this error path. Fixes: b44be2462dbe ('usb: gadget: gadgetfs: Free memory allocated by memdup_user()')

[PATCH 3.18 032/144] dm thin: restore requested error_if_no_space setting on OODS to WRITE transition

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 172c238612ebf81cabccc86b788c9209af591f61 ] A thin-pool that is in out-of-data-space (OODS) mode may transition back to write mode -- without the admin adding more space to the

[PATCH 3.18 041/144] Revert "drm/i915: Fix mutex->owner inspection race under DEBUG_MUTEXES"

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a50940510e94f5fb65ffd79877a60592d85598a9 ] The core fix was applied in commit a63b03e2d2477586440741677ecac45bcf28d7b1 Author: Chris Wilson Date: Tue Jan 6 10:29:35 2015 +

[PATCH 3.18 018/144] powerpc/tm: Fix userspace r13 corruption

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling [ Upstream commit cf13435b730a502e814c63c84d93db131e563f5f ] When we treclaim we store the userspace checkpointed r13 to a scratch SPR and then later save the scratch SPR to

[PATCH 4.4 046/114] xfrm: Clear sk_dst_cache when applying per-socket policy.

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 ] If a socket has a valid dst cache, then xfrm_lookup_route will get skipped. However, the cache is not invalidated when applying policy to a

[PATCH 4.4 019/114] KEYS: put keyring if install_session_keyring_to_cred() fails

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d636bd9f12a66ea3775c9fabbf3f8e118253467a ] In join_session_keyring(), if install_session_keyring_to_cred() were to fail, we would leak the keyring reference, just like in the bug

[PATCH 4.4 035/114] thermal: allow u8500-thermal driver to be a module

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 26716ce124fce88f288f07738ef685d5dfe5c13f ] When the thermal subsystem is a loadable module, the u8500 driver fails to build: drivers/thermal/built-in.o: In function

[PATCH 4.4 016/114] smsc95xx: Check for Wake-on-LAN modes

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c530c471ba37bdd9fe1c7185b01455c00ae606fb ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.4 030/114] ipv6: orphan skbs in reassembly unit

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 48cac18ecf1de82f76259a54402c3adb7839ad01 ] Andrey reported a use-after-free in IPv6 stack. Issue here is that we free the socket while it still has skb in TX path and in some

[PATCH 4.4 037/114] x86/PCI: Mark Broadwell-EP Home Agent 1 as having non-compliant BARs

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit da77b67195de1c65bef4908fa29967c4d0af2da2 ] Commit b894157145e4 ("x86/PCI: Mark Broadwell-EP Home Agent & PCU as having non-compliant BARs") marked Home Agent 0 & PCU has having

[PATCH 4.4 066/114] sparc64 mm: Fix more TSB sizing issues

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1e953d846ac015fbfcf09c857e8f893924cb629c ] Commit af1b1a9b36b8 ("sparc64 mm: Fix base TSB sizing when hugetlb pages are used") addressed the difference between hugetlb and THP pages

[PATCH 4.4 042/114] ASoC: ak4613: Enable cache usage to fix crashes on resume

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dcd2d1f78664fdc75eadaaf65257834e24383d01 ] During system resume: kernel BUG at drivers/base/regmap/regcache.c:347! ... PC is at regcache_sync+0x1c/0x128 LR is at

Re: [PATCH 2/6] regulator: lochnagar: Move driver to binding from DT

On Thu, Nov 08, 2018 at 12:16:29PM +, Mark Brown wrote: > On Thu, Nov 08, 2018 at 10:14:01AM +, Charles Keepax wrote: > > > +static const struct of_device_id lochnagar_of_match[] = { > > + { .compatible = "cirrus,lochnagar-regulator" }, > > + {}, > > +}; > > This is obviously just

[PATCH 4.4 059/114] ALSA: timer: Fix zero-division by continue of uninitialized instance

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9f8a7658bcafb2a7853f7a2eae8a94e87e6e695b ] When a user timer instance is continued without the explicit start beforehand, the system gets eventually zero-division error like:

[PATCH 4.4 069/114] gpio: msic: fix error return code in platform_msic_gpio_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ca1f3ae3154ad6d08caa740c99be0d86644a4e44 ] platform_get_irq() returns an error code, but the gpio-msic driver ignores it and always returns -EINVAL. This is not correct, and prevents

[PATCH 4.4 058/114] ixgbe: Correct X550EM_x revision check

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3ca2b2506ec9a3b1615930a6810d30ec9aba10a1 ] The X550EM_x revision check needs to check a value, not just a bit. Use a mask and check the value. Also remove the redundant check inside

[PATCH 4.4 052/114] drm/nouveau/fbcon: fix oops without fbdev emulation

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4813766325374af6ed0b66879ba6a0bbb05c83b6 ] This is similar to an earlier commit 52dfcc5ccfbb ("drm/nouveau: fix for disabled fbdev emulation"), but protects all occurrences of

[PATCH 4.4 065/114] video: fbdev: pxa3xx_gcu: fix error return code in pxa3xx_gcu_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7588f1ecc5f0c914e669d8afb6525f47cd1c4355 ] platform_get_irq() returns an error code, but the pxa3xx_gcu driver ignores it and always returns -ENODEV. This is not correct and,

[PATCH 4.4 015/114] smsc75xx: Check for Wake-on-LAN modes

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9c734b2769a73eea2e9e9767c0e0bf839ff23679 ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.4 028/114] af_iucv: Move sockaddr length checks to before accessing sa_family in bind and connect handlers

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e3c42b61ff813921ba58cfc0019e3fd63f651190 ] Verify that the caller-provided sockaddr structure is large enough to contain the sa_family field, before accessing it in bind() and

[PATCH 4.9 143/171] net: udp: fix handling of CHECKSUM_COMPLETE packets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sean Tranchetti [ Upstream commit db4f1be3ca9b0ef7330763d07bf4ace83ad6f913 ] Current handling of CHECKSUM_COMPLETE packets by the UDP stack is incorrect for any packet that has an incorrect

[PATCH 4.9 148/171] bonding: fix length of actor system

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Jungel [ Upstream commit 414dd6fb9a1a1b59983aea7bf0f79f0085ecc5b8 ] The attribute IFLA_BOND_AD_ACTOR_SYSTEM is sent to user space having the length of

[PATCH 4.9 158/171] cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)

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

[PATCH 4.9 156/171] gpio: mxs: Get rid of external API call

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 833eacc7b5913da9896bacd30db7d490aa777868 ] The MXS driver was calling back into the GPIO API from its irqchip. This is not very elegant, as we are a driver, let's just shortcut back

[PATCH 4.9 151/171] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.9-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.9 135/171] net: bridge: remove ipv6 zero address check in mcast queries

4.9-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.9 153/171] Revert "x86/mm: Expand static page table for fixmap space"

4.9-stable review patch. If anyone has any objections, please let me know. -- This reverts commit 3a8304b7ad2e291777e8499e39390145d932a2fd, which was upstream commit 05ab1d8a4b36ee912b7087c6da127439ed0a903e. Ben Hutchings writes: This backport is incorrect. The part that

[PATCH 4.9 147/171] ethtool: fix a privilege escalation bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit 58f5bbe331c566f49c9559568f982202a278aa78 ] In dev_ethtool(), the eth command 'ethcmd' is firstly copied from the use-space buffer 'useraddr' and checked to see

[PATCH 4.9 149/171] net: drop skb on failure in ip_check_defrag()

4.9-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.9 133/171] perf tools: Disable parallelism for make clean

4.9-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.9 145/171] sctp: fix race on sctp_id2asoc

4.9-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.9 144/171] r8169: fix NAPI handling under high load

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high

[PATCH 4.9 146/171] vhost: Fix Spectre V1 vulnerability

4.9-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.9 150/171] net: fix pskb_trim_rcsum_slow() with odd trim offset

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dimitris Michailidis [ Upstream commit d55bef5059dd057bd077155375c581b49d25be7e ] We've been getting checksum errors involving small UDP packets, usually 59B packets with 1 extra non-zero

[PATCH 4.4 105/114] ptp: fix Spectre v1 vulnerability

4.4-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.4 101/114] mremap: properly flush TLB before releasing the page

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds Commit eb66ae030829605d61fbef1909ce310e29f78821 upstream. This is a backport to stable 4.4.y. Jann Horn points out that our TLB flushing was subtly wrong for the mremap()

[PATCH 4.4 103/114] ahci: dont ignore result code of ahci_reset_controller()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d312fefea8387503375f728855c9a62de20c9665 ] ahci_pci_reset_controller() calls ahci_reset_controller(), which may fail, but ignores the result code and always returns success. This may

[PATCH 4.4 076/114] spi: xlp: fix error return code in xlp_spi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9a6b94796ae6feaf275ec6200e9b2964db208182 ] platform_get_irq() returns an error code, but the spi-xlp driver ignores it and always returns -EINVAL. This is not correct and, prevents

[PATCH 4.4 107/114] IB/ucm: Fix Spectre v1 vulnerability

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

[PATCH 4.4 075/114] spi/bcm63xx: fix error return code in bcm63xx_spi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ba8afe94723e9ba665aee9cca649fb2c80f7304c ] platform_get_irq() returns an error code, but the spi-bcm63xx driver ignores it and always returns -ENXIO. This is not correct and,

[PATCH 4.4 104/114] cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)

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

[PATCH 4.4 102/114] crypto: shash - Fix a sleep-in-atomic bug in shash_setkey_unaligned

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9039f3ef446e9ffa200200c934f049add9e58426 ] The SCTP program may sleep under a spinlock, and the function call path is: sctp_generate_t3_rtx_event (acquire the spinlock) sctp_do_sm

[PATCH 4.4 077/114] ASoC: spear: fix error return code in spdif_in_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 27d30400c448264c1ac9434cb836de0c230af213 ] platform_get_irq() returns an error code, but the spdif_in driver ignores it and always returns -EINVAL. This is not correct, and prevents

[PATCH 4.4 113/114] x86/percpu: Fix this_cpu_read()

4.4-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.9 010/171] ARM: dts: BCM63xx: Fix incorrect interrupt specifiers

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3ab97942d0213b6583a5408630a8cbbfbf54730f ] A number of our interrupts were incorrectly specified, fix both the PPI and SPI interrupts to be correct. Fixes: b5762cacc411 ("ARM:

[PATCH 4.9 005/171] mac80211: fix pending queue hang due to TX_DROP

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6eae4a6c2be387fec41b0d2782c4fffb57159498 ] In our environment running lots of mesh nodes, we are seeing the pending queue hang periodically, with the debugfs queues file showing

[PATCH 4.9 004/171] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24f33e64fcd0d50a4b1a8e5b41bd0257aa66b0e8 ] Core regulatory hints didn't set wiphy_idx to WIPHY_IDX_INVALID. Since the regulatory request is zeroed, wiphy_idx was always implicitly

[PATCH 4.9 001/171] xfrm: Validate address prefix lengths in the xfrm selector.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 4.9 003/171] mac80211: Always report TX status

4.9-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 4.4 071/114] usb: ehci-omap: fix error return code in ehci_hcd_omap_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 99dbff202e28ad1dadf55b058bcae7908678e963 ] platform_get_irq() returns an error code, but the ehci-omap driver ignores it and always returns -ENODEV. This is not correct and, prevents

[PATCH 3.18 082/144] rtnl: dont account unused struct ifla_port_vsi in rtnl_port_size

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 025331df34f6722f86b467cb13a69326444ab1bc ] When allocating rtnl dump messages, struct ifla_port_vsi is never dumped, so we can save header plus payload in rtnl_port_size(). Infact,

[PATCH 3.18 093/144] tty: serial: fsl_lpuart: fix clearing of receive flag

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d68827c62a105eec547945daedf4d1d3e283717d ] Commit 8e4934c6d6c6 ("tty: serial: fsl_lpuart: clear receive flag on FIFO flush") implemented clearing of the receive flag by reading the

[PATCH 3.18 081/144] quota: Fix maximum quota limit settings

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7e08da50cf706151f324349f9235ebd311226997 ] Currently quota format that supports 64-bit usage sets maximum quota limit as 2^64-1. However quota core code uses signed numbers to track

[PATCH 3.18 083/144] nfs: fix high load average due to callback thread sleeping

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5d05e54af3cdbb13cf19c557ff2184781b91a22c ] Chuck pointed out a problem that crept in with commit 6ffa30d3f734 (nfs: don't call blocking operations while !TASK_RUNNING). Linux counts

[PATCH 3.18 079/144] ARM: dts: disable CCI on exynos5420 based arndale-octa

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 25217fef355174209eff68c0eb438a8af5d7b01c ] The arndale-octa board was giving "imprecise external aborts" during boot-up with MCPM enabled. CCI enablement of the boot cluster was

[PATCH 3.18 092/144] iommu/vt-d: Fix VM domain ID leak

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46ebb7af7b93792de65e124e1ab8b89a108a41f2 ] This continues the attempt to fix commit fb170fb4c548 ("iommu/vt-d: Introduce helper functions to make code symmetric for readability").

[PATCH 3.18 078/144] drivers: bus: check cci device tree node status

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 896ddd600ba4a3426aeb11710ae9c28dd7ce68ce ] The arm-cci driver completes the probe sequence even if the cci node is marked as disabled. Add a check in the driver to honour the cci

[PATCH 3.18 096/144] net: ethernet: davicom: fix devicetree irq resource

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b5a099c67a1c36b91356624ce86eb3f9f48a82c7 ] The dm9000 driver doesn't work in at least one device-tree configuration, spitting an error message on irq resource : [1.062495]

[PATCH 3.18 097/144] perf bench numa: Fix to show proper convergence stats

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b42b09b88c831ba4da2d669581dde371c38c2af ] With commit: e1e455f4f4d3 (perf tools: Work around lack of sched_getcpu in glibc < 2.6), perf_bench numa mem with -c or -m option is not

[PATCH 3.18 094/144] x86/idle: Restore trace_cpu_idle to mwait_idle() calls

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e43d0189ac02415fe4487f79fc35e8f147e9ea0d ] Commit b253149b843f ("sched/idle/x86: Restore mwait_idle() to fix boot hangs, to improve power savings and to improve performance")

[PATCH 3.18 089/144] dm: fix AB-BA deadlock in __dm_destroy()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a708cff93f1845b9239bc7d6310aef54e716c6a ] __dm_destroy() takes io_barrier SRCU lock (dm_get_live_table) and suspend_lock in reverse order. Doing so can cause AB-BA deadlock:

[PATCH 3.18 090/144] arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 90f6e150e44a0dc3883110eeb3ab35d1be42b6bb ] We don't hold the mmap_sem while searching for the VMAs when we try to unmap each memslot for a VM. Fix this properly to avoid unexpected

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

On Thu, Nov 8, 2018 at 12:14 PM Theodore Y. Ts'o wrote: > > On Thu, Nov 08, 2018 at 09:19:33AM -0800, Dan Williams wrote: > > > > I know at least StGit mail does not grok that "#"notation. I've > > stopped using it in favor of a "Fixes:" tag. I would think "Fixes:" is > > preferred over "# " if

Re: [PATCH RFC 0/3] Static calls

On Thu, Nov 08, 2018 at 03:15:50PM -0600, Josh Poimboeuf wrote: > - Does this feature have much value without retpolines? If not, should > we make it depend on retpolines somehow? I forgot Andy mentioned that we might be able to use this to clean up paravirt patching, in which case it would

Re: [PATCH 10/12] fs/locks: create a tree of dependent requests.

On Mon, Nov 05, 2018 at 12:30:48PM +1100, NeilBrown wrote: > When we find an existing lock which conflicts with a request, > and the request wants to wait, we currently add the request > to a list. When the lock is removed, the whole list is woken. > This can cause the thundering-herd problem. >

[PATCH 3.18 011/144] qlcnic: fix Tx descriptor corruption on 82xx devices

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shahed Shaikh [ Upstream commit c333fa0c4f220f8f7ea5acd6b0ebf3bf13fd684d ] In regular NIC transmission flow, driver always configures MAC using Tx queue zero descriptor as a part of MAC

[PATCH 3.18 001/144] selftests/efivarfs: add required kernel configs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lei Yang [ Upstream commit 53cf59d6c0ad3edc4f4449098706a8f8986258b6 ] add config file Signed-off-by: Lei Yang Signed-off-by: Shuah Khan (Samsung OSG) Signed-off-by: Sasha Levin

[PATCH 3.18 005/144] i2c: i2c-scmi: fix for i2c_smbus_write_block_data

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Edgar Cherkasov commit 08d9db00fe0e300d6df976e6c294f974988226dd upstream. The i2c-scmi driver crashes when the SMBus Write Block transaction is executed: WARNING: CPU: 9 PID: 2194 at

[PATCH 3.18 008/144] net/ipv6: Display all addresses in output of /proc/net/if_inet6

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Barnhill <0xeff...@gmail.com> [ Upstream commit 86f9bd1ff61c413a2a251fa736463295e4e24733 ] The backend handling for /proc/net/if_inet6 in addrconf.c doesn't properly handle

[PATCH 3.18 009/144] netlabel: check for IPV4MASK in addrinfo_get

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sean Tranchetti [ Upstream commit f88b4c01b97e09535505cf3c327fdbce55c27f00 ] netlbl_unlabel_addrinfo_get() assumes that if it finds the NLBL_UNLABEL_A_IPV4ADDR attribute, it must also have

[PATCH 3.18 010/144] net/usb: cancel pending work when unbinding smsc75xx

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yu Zhao [ Upstream commit f7b2a56e1f3dcbdb4cf09b2b63e859ffe0e09df8 ] Cancel pending work before freeing smsc75xx private data structure during binding. This fixes the following crash in the

[PATCH 3.18 002/144] mfd: omap-usb-host: Fix dts probe of children

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 10492ee8ed9188d6d420e1f79b2b9bdbc0624e65 ] It currently only works if the parent bus uses "simple-bus". We currently try to probe children with non-existing

[PATCH 3.18 006/144] xhci: Dont print a warning when setting link state for disabled ports

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 1208d8a84fdcae6b395c57911cdf907450d30e70 upstream. When disabling a USB3 port the hub driver will set the port link state to U3 to prevent "ejected" or "safely removed"

[PATCH 3.18 025/144] asix: Check for supported Wake-on-LAN modes

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

[PATCH 3.18 014/144] net: systemport: Fix wake-up interrupt race during resume

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit 45ec318578c0c22a11f5b9927d064418e1ab1905 ] The AON_PM_L2 is normally used to trigger and identify the source of a wake-up event. Since the RX_SYS clock is

[PATCH 3.18 028/144] smsc75xx: Check for Wake-on-LAN modes

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9c734b2769a73eea2e9e9767c0e0bf839ff23679 ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not

[PATCH 3.18 029/144] smsc95xx: Check for Wake-on-LAN modes

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c530c471ba37bdd9fe1c7185b01455c00ae606fb ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not

[PATCH 3.18 016/144] ip6_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 76c0ddd8c3a683f6e2c6e60e11dc1a1558caf4bc ] the ip6 tunnel xmit ndo assumes that the processed skb always contains an ip[v6] header, but syzbot has found a way to

[PATCH 3.18 027/144] sr9800: Check for supported Wake-on-LAN modes

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

[PATCH 4.4 090/114] ipv6: mcast: fix a use-after-free in inet6_mc_check

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit dc012f3628eaecfb5ba68404a5c30ef501daf63d ] syzbot found a use-after-free in inet6_mc_check [1] The problem here is that inet6_mc_check() uses rcu and

[PATCH 4.4 095/114] net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules

4.4-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.4 096/114] r8169: fix NAPI handling under high load

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high

[PATCH 4.4 073/114] spi/bcm63xx-hspi: fix error return code in bcm63xx_hsspi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 378da4a65f3a0390837b38145bb5d8c2d20c2cf7 ] platform_get_irq() returns an error code, but the spi-bcm63xx-hsspi driver ignores it and always returns -ENXIO. This is not correct and,

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