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

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

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

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

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

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

[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: => save

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

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

[PATCH 3.18 122/144] KEYS: put keyring if install_session_keyring_to_cred() fails

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

[PATCH 3.18 141/144] cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)

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

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

[PATCH 3.18 140/144] net: sched: gred: pass the right attribute to gred_change_table_def()

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

[PATCH 3.18 126/144] unix: correctly track in-flight fds in sending process user_struct

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 415e3d3e90ce9e18727e8843ae343eda5a58fad6 ] The commit referenced in the Fixes tag incorrectly accounted the number of in-flight fds over a unix domain socket to the original opener o

[PATCH 3.18 121/144] igb: fix NULL derefs due to skipped SR-IOV enabling

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit be06998f96ecb93938ad2cce46c4289bf7cf45bc ] The combined effect of commits 6423fc3416 ("igb: do not re-init SR-IOV during probe") and ceee3450b3 ("igb: make sure SR-IOV init uses the

[PATCH 3.18 125/144] x86/PCI: Mark Broadwell-EP Home Agent 1 as having non-compliant BARs

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

[PATCH 3.18 135/144] net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules

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

[PATCH 3.18 130/144] mremap: properly flush TLB before releasing the page

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds Commit eb66ae030829605d61fbef1909ce310e29f78821 upstream. This is a backport to stable 3.18.y, based on Will Deacon's 4.4.y backport. Jann Horn points out that our TLB flushing

[PATCH 3.18 138/144] net: drop skb on failure in ip_check_defrag()

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

[PATCH 3.18 137/144] sctp: fix race on sctp_id2asoc

3.18-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 3.18 139/144] rtnetlink: Disallow FDB configuration for non-Ethernet device

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

[PATCH 3.18 106/144] ALSA: hda - Add headset mic support for Acer Aspire V5-573G

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0420694dddeb9e269a1ab2129a0119a5cea294a4 ] Acer Aspire V5 with the ALC282 codec is given the wrong value for the 0x19 PIN by the laptop's BIOS. Overriding it with the correct value a

[PATCH 3.18 107/144] ALSA: usb-audio: Add a more accurate volume quirk for AudioQuest DragonFly

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 42e3121d90f42e57f6dbd6083dff2f57b3ec7daa ] AudioQuest DragonFly DAC reports a volume control range of 0..50 (0x..0x0032) which in USB Audio means a range of 0 .. 0.2dB, which is

[PATCH 3.18 105/144] rtlwifi: rtl8821ae: Fix lockups on boot

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eeec5d0ef7ee54a75e09e861c3cc44177b8752c7 ] In commit 54328e64047a5 ("rtlwifi: rtl8821ae: Fix system lockups on boot"), an attempt was made to fix a regression introduced in commit 12

[PATCH 3.18 101/144] ASoC: dapm: Dont add prefix to widget stream name

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a798c24a69b64f09e2d323ac8155a36373e5d5fd ] Commit fdb6eb0a1287 ("ASoC: dapm: Modify widget stream name according to prefix") fixed the case where a DAPM route between a DAI widget an

[PATCH 3.18 095/144] ext4: fix an ext3 collapse range regression in xfstests

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b9576fc3624eb9fc88bec0d0ae883fd78be86239 ] The xfstests test suite assumes that an attempt to collapse range on the range (0, 1) will return EOPNOTSUPP if the file system does not su

[PATCH 3.18 080/144] clk: rockchip: fix deadlock possibility in cpuclk

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a5e1baf7dca10f8cf945394034013260297bc416 ] Lockdep reported a possible deadlock between the cpuclk lock and for example the i2c driver. CPU0CPU1 --

[PATCH 3.18 115/144] x86/ldt: Fix small LDT allocation for Xen

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f454b478861325f067fd58ba7ee9f1b5c4a9d6a0 ] While the following commit: 37868fe113 ("x86/ldt: Make modify_ldt synchronous") added a nice comment explaining that Xen needs page-ali

[PATCH 3.18 109/144] Btrfs: do not ignore errors from btrfs_lookup_xattr in do_setxattr

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5cdf83edb8e41cad1ec8eab2d402b4f9d9eb7ee0 ] The return value from btrfs_lookup_xattr() can be a pointer encoding an error, therefore deal with it. This fixes commit 5f5bc6b1e2d5 ("Btr

[PATCH 3.18 118/144] sctp: translate network order to host order when users get a hmacid

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a84bd46647ff181eb2659fdc99590e6f16e501d ] Commit ed5a377d87dc ("sctp: translate host order to network order when setting a hmacid") corrected the hmacid byte-order when setting a hm

[PATCH 3.18 119/144] iwlwifi: pcie: correctly define 7265-D cfg

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b0e2b0f7bfe9a9098bda6109176adcf78f9b7ac ] The trans cfg was not replaced for 7265-D cards. This led to a check of the min-NVM version against a 7265-C card, causing very-old 7265-D

[PATCH 3.18 117/144] vfs: Make sendfile(2) killable even better

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c725bfce7968009756ed2836a8cd7ba4dc163011 ] Commit 296291cdd162 (mm: make sendfile(2) killable) fixed an issue where sendfile(2) was doing a lot of tiny writes into a filesystem and t

[PATCH 3.18 084/144] rcu: Clear need_qs flag to prevent splat

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c0135d07b013fa8f7ba9ec91b4369c372e6a28cb ] If the scheduling-clock interrupt sets the current tasks need_qs flag, but if the current CPU passes through a quiescent state in the meant

[PATCH 3.18 077/144] perf tools: Fix segfault for symbol annotation on TUI

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 813ccd15452ed34e97aa526ffc70d6d8e6c466c5 ] Currently the symbol structure is allocated with symbol_conf.priv_size to carry sideband information like annotation, map browser on TUI an

[PATCH 3.18 088/144] pinctrl: imx25: ensure that a pin with id i is at position i in the info array

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9911a2d5e9d14e39692b751929a92cb5a1d9d0e0 ] The code in pinctrl-imx.c only works correctly if in the imx_pinctrl_soc_info passed to imx_pinctrl_probe we have: info->pins[i].n

[PATCH 3.18 063/144] Revert "tty: Fix pty master poll() after slave closes v2"

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2ce3c10c0c3e0d418c1a7a4c838319ba42c75388 ] This reverts commit c4dc304677e8d566572c4738d95c48be150c6606. This fix is superseded by commit 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73, 'p

[PATCH 3.18 069/144] ARM: at91: board-dt-sama5: add phy_fixup to override NAND_Tree

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b8659752c37ec157ee254cff443b1c9d523aea22 ] Appearance: On some SAMA5D4EK boards, after power up, the Eth1 doesn't work. Reason: The PIOE2 pin is connected to the NAND_Tree# of KSZ80

[PATCH 3.18 067/144] ARM: at91: sama5d3: dt: correct the sound route

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 04582fd03fb263598e3b126c76cc42195aa0fd05 ] The MICBIAS is a supply, should route to MIC while not IN1L. Signed-off-by: Bo Shen Signed-off-by: Nicolas Ferre Signed-off-by: Sasha Le

[PATCH 3.18 062/144] usb: host: ehci-tegra: request deferred probe when failing to get phy

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f56e67f0a880a5b795cdb5f62614aafe264c5304 ] The commit 1290a958d48e ("usb: phy: propagate __of_usb_find_phy()'s error on failure") changed the condition to return -EPROBE_DEFER to hos

[PATCH 3.18 061/144] uas: disable UAS on Apricorn SATA dongles

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 36d1ffdb210ec2d0d6a69e9f6466ae8727d34119 ] The Apricorn SATA dongle will occasionally return "USBSUSBSUSB" in response to SCSI commands when running in UAS mode. Therefore, disable

[PATCH 3.18 060/144] USB: EHCI: adjust error return code

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c401e7b4a808d50ab53ef45cb8d0b99b238bf2c9 ] The USB stack uses error code -ENOSPC to indicate that the periodic schedule is too full, with insufficient bandwidth to accommodate a new

[PATCH 3.18 057/144] NFSv4: Remove incorrect check in can_open_delegated()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4e379d36c050b0117b5d10048be63a44f5036115 ] Remove an incorrect check for NFS_DELEGATION_NEED_RECLAIM in can_open_delegated(). We are allowed to cache opens even in a situation where

[PATCH 3.18 066/144] ARM: at91/dt: sama5d4: fix the timer reg length

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0068b2e1b7f925a818fdc0a5d10ef0ad40f746e7 ] The second property of reg is the length, so correct it for timer. Signed-off-by: Bo Shen Signed-off-by: Nicolas Ferre Signed-off-by: Sa

[PATCH 3.18 065/144] mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7b7c54914f73966976893747ee8e2ca58166a627 ] Currently it is not possible to have a kernel with built-in MCB attached devices. This results out of the fact that mcb-pci requests PCI BA

[PATCH 3.18 022/144] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

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

[PATCH 3.18 064/144] serial: samsung: Add the support for Exynos5433 SoC

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31ec77aca72ee5920ed3ec3d047734dc0bc43342 ] This patch adds new s3c24xx_serial_drv_data structure for Exynos5433 SoC because Exynos5433 has different fifo size from existing Exynos4 S

[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()') Signe

[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 thin-p

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

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

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

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

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

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

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

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

[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 user,

[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 user,

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

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

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

[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 starting/stoppi

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

[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" de

[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 mm/page_

[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 Signed-off-

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

Re: RFC: userspace exception fixups

On 11/8/18 1:16 PM, Sean Christopherson wrote: > On Thu, Nov 08, 2018 at 12:10:30PM -0800, Dave Hansen wrote: >> On 11/8/18 12:05 PM, Andy Lutomirski wrote: >>> Hmm. The idea being that the SDK preserves RBP but not RSP. That's >>> not the most terrible thing in the world. But could the SDK live

Re: [PATCH v4 01/18] arm64: dts: qcom: qcs404: add base dts files

On Thu, Nov 8, 2018 at 12:40 PM Vinod Koul wrote: > > Add base dts files for QCS404 chipset along with cpu, timer, > gcc and uart2 nodes. > > Signed-off-by: Vinod Koul > --- > arch/arm64/boot/dts/qcom/qcs404.dtsi | 175 > +++ > 1 file changed, 175 insertions(+) >

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 > b/arch/arm6

[PATCH] HID: hidraw: enforce minors_lock locking via lockdep

From: Jiri Kosina lockdep is much more powerful enforcing the locking rules than code comments, so let's switch to it. Signed-off-by: Jiri Kosina --- drivers/hid/hidraw.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/hid/hidraw.c b/drivers/hid/hidraw.c index

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

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. > T

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; > l.subrahma

Re: [PATCH] irq/irq_sim: add locking

Hello, On Thu, Nov 08, 2018 at 09:55:02PM +0100, Bartosz Golaszewski wrote: > czw., 8 lis 2018 o 20:41 Uwe Kleine-König > napisał(a): > > > @@ -142,10 +143,14 @@ EXPORT_SYMBOL_GPL(devm_irq_sim_init); > > > */ > > > void irq_sim_fire(struct irq_sim *sim, unsigned int offset) > > > { > > > +

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 hav

kmemleak: Early log buffer exceeded (525980) during boot

The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it disables kmemleak every time on this aarch64 server running the latest mainline (b00d209). # echo scan > /sys/kernel/debug/kmemleak  -bash: echo: write error: Device or resource busy Any idea on how to enable kmemleak there?

Re: [PATCH v2 3/4] of/property: Add of_fwnode_name()

On Thu, Nov 8, 2018 at 1:25 PM Andy Shevchenko wrote: > > On Thu, Nov 08, 2018 at 12:23:51PM -0600, Rob Herring wrote: > > On Thu, Nov 8, 2018 at 10:52 AM Heikki Krogerus > > wrote: > > > > > > This implements get_name fwnode op for DT. > > > > > > Signed-off-by: Heikki Krogerus > > > --- > > >

[PATCH RFC 0/3] Static calls

These patches are related to two similar patch sets from Ard and Steve: - https://lkml.kernel.org/r/20181005081333.15018-1-ard.biesheu...@linaro.org - https://lkml.kernel.org/r/20181006015110.653946...@goodmis.org The code is also heavily inspired by the jump label code, as some of the concepts a

[RFC PATCH 1/3] static_call: Add static call infrastructure

Add a static call infrastructure. Static calls use code patching to hard-code function pointers into direct branch instructions. They give the flexibility of function pointers, but with improved performance. This is especially important for cases where retpolines would otherwise be used, as retpo

[RFC PATCH 2/3] x86/static_call: Add x86 unoptimized static call implementation

Add the x86 unoptimized static call implementation. For each key, it creates a permanent trampoline which is the destination for all static calls for the given key. The trampoline has a direct jump which gets patched by static_call_update() when the destination changes. Signed-off-by: Josh Poimb

[RFC PATCH 3/3] x86/static_call: Add optimized static call implementation for 64-bit

Add the optimized static call implementation for x86-64. For each key, a temporary trampoline is created, named __static_call_tramp_. The trampoline has an indirect jump to the destination function. Objtool uses the trampoline naming convention to detect all the call sites. It then annotates th

Re: A different PD controller firmware problem?

On Thu, Nov 08, 2018 at 06:00:59PM +, mario.limoncie...@dell.com wrote: > > Sortly after 12:30am US/Eastern, I got a low power warning on my > > system, and the battery power had dropped below 10%. Apparently the > > laptop was not accepting any charge any more. I tried doing a suspend > > to

Re: RFC: userspace exception fixups

On Thu, Nov 08, 2018 at 12:10:30PM -0800, Dave Hansen wrote: > On 11/8/18 12:05 PM, Andy Lutomirski wrote: > > Hmm. The idea being that the SDK preserves RBP but not RSP. That's > > not the most terrible thing in the world. But could the SDK live with > > something more like my suggestion where

Re: [PATCH 2/3] gpio: mockup: add locking

On Thu, Nov 08, 2018 at 05:52:54PM +0100, Bartosz Golaszewski wrote: > While no user reported any race condition problems with gpio-mockup, > let's be on the safe side and use a mutex when performing any changes > on the dummy chip structures. > > Suggested-by: Uwe Kleine-König > Signed-off-by: B

Re: [PATCH 12/24] leds: lm3692x: Use led_compose_name()

Jacek On 11/08/2018 02:48 PM, Jacek Anaszewski wrote: > Dan, > > On 11/08/2018 07:14 PM, Dan Murphy wrote: >> On 11/06/2018 04:07 PM, Jacek Anaszewski wrote: >>> Switch to using generic LED support for composing LED class >>> device name. >>> >>> Signed-off-by: Jacek Anaszewski >>> Cc: Dan Murph

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

On Thu, Nov 08, 2018 at 01:06:15PM -0800, Greg KH wrote: > On Thu, Nov 08, 2018 at 08:58:32PM +0100, Thomas Gleixner wrote: > > On Thu, 8 Nov 2018, Paul E. McKenney wrote: > > > On Thu, Nov 08, 2018 at 09:19:33AM -0800, Dan Williams wrote: > > > > On Thu, Nov 8, 2018 at 1:13 AM Peter Zijlstra > >

Re: [PATCH 04/24] dt-bindings: leds: Add function and color properties

Jacek On 11/08/2018 02:47 PM, Jacek Anaszewski wrote: > Dan, > > On 11/08/2018 07:00 PM, Dan Murphy wrote: >> Jacek >> >> On 11/06/2018 04:07 PM, Jacek Anaszewski wrote: >>> Introduce dedicated properties for conveying information about >>> LED function and color. Mark old "label" property as dep

[PATCH v6 01/10] dt-bindings: fsi: Add P9 OCC device documentation

From: Eddie James Document the bindings for the FSI-attached POWER9 On-Chip Controller. Signed-off-by: Eddie James --- Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt | 16 1 file changed, 16 insertions(+) create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9-o

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

On Thu, Nov 08, 2018 at 08:58:32PM +0100, Thomas Gleixner wrote: > On Thu, 8 Nov 2018, Paul E. McKenney wrote: > > On Thu, Nov 08, 2018 at 09:19:33AM -0800, Dan Williams wrote: > > > On Thu, Nov 8, 2018 at 1:13 AM Peter Zijlstra > > > wrote: > > > > > > > > On Thu, Nov 08, 2018 at 08:40:12AM +010

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

On Thu, Nov 08, 2018 at 03:14:25PM -0500, 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 "#

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