[PATCH 4.4 51/92] signals: avoid unnecessary taking of sighand->siglock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Waiman Long commit c7be96af89d4b53211862d8599b2430e8900ed92 upstream. When running certain database workload on a high-end system with many CPUs, it was found that spinlock contention in the si

[PATCH 4.4 50/92] mm: filemap: avoid unnecessary calls to lock_page when waiting for IO to complete during a read

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit ebded02788b5d7c7600f8cff26ae07896d568649 upstream. In the generic read paths the kernel looks up a page in the page cache and if it's up to date, it is used. If not, the page

Re: [PATCH 1/3] i2c: mux: pca954x: merge calls to of_match_device and of_device_get_match_data

On 2018-05-21 11:49, Julia Lawall wrote: > Drop call to of_match_device, which is subsumed by the subsequent > call to of_device_get_match_data. The code becomes simpler, and a > temporary variable can be dropped. Thanks for your patch! Applied to i2c-mux/for-next Cheers, Peter

Re: [RESEND PATCH 2/5] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

Hi Benjamin, On Thu, 24 May 2018 13:30:14 +0200 Benjamin Lindqvist wrote: > Hi Stefan, > > It seems to me that a probe similar to what the BootROM does shouldn't > be awfully complicated to implement - just cycle through the switch > cases in case of an ECC error. But I guess that's more of an

[PATCH 4.4 49/92] mm: filemap: remove redundant code in do_read_cache_page

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit 32b635298ff4e991d8d8f64dc23782b02eec29c3 upstream. do_read_cache_page and __read_cache_page duplicate page filler code when filling the page for the first time. This patch si

[PATCH 4.4 77/92] s390: move expoline assembler macros to a header

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky [ Upstream commit 6dd85fbb87d1d6b87a3b1f02ca28d7b2abd2e7ba ] To be able to use the expoline branches in different assembler files move the associated macros from entry.S to a

[PATCH 4.4 46/92] powerpc: Dont preempt_disable() in show_cpuinfo()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit 349524bc0da698ec77f2057cf4a4948eb6349265 upstream. This causes warnings from cpufreq mutex code. This is also rather unnecessary and ineffective. If we really want

[PATCH 4.4 72/92] packet: in packet_snd start writing at link layer allocation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba ] Packet sockets allow construction of packets shorter than dev->hard_header_len to accommodate protocols with variab

Re: [PATCH 08/14] arm64: ssbd: Disable mitigation on CPU resume if required by user

On Tue, May 22, 2018 at 04:06:42PM +0100, Marc Zyngier wrote: > On a system where firmware can dynamically change the state of the > mitigation, the CPU will always come up with the mitigation enabled, > including when coming back from suspend. > > If the user has requested "no mitigation" via a c

[PATCH 4.4 73/92] sock_diag: fix use-after-free read in __sk_free

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 9709020c86f6bf8439ca3effc58cfca49a5de192 ] We must not call sock_diag_has_destroy_listeners(sk) on a socket that has no reference on net structure. BUG: KASAN: u

[PATCH 4.4 71/92] net: test tailroom before appending to linear skb

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 113f99c3358564a0647d444c2ae34e8b1abfd5b9 ] Device features may change during transmission. In particular with corking, a device may toggle scatter-gather in b

Re: [PATCH] userfaultfd: prevent non-cooperative events vs mcopy_atomic races

On Thu, May 24, 2018 at 02:24:37PM +0300, Pavel Emelyanov wrote: > On 05/23/2018 10:42 AM, Mike Rapoport wrote: > > If a process monitored with userfaultfd changes it's memory mappings or > > forks() at the same time as uffd monitor fills the process memory with > > UFFDIO_COPY, the actual creation

[PATCH 4.4 69/92] btrfs: fix crash when trying to resume balance without the resume flag

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Anand Jain commit 02ee654d3a04563c67bfe658a05384548b9bb105 upstream. We set the BTRFS_BALANCE_RESUME flag in the btrfs_recover_balance() only, which isn't called during the remount. So when res

[PATCH 4.4 67/92] ARM: 8772/1: kprobes: Prohibit kprobes on get_user functions

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 0d73c3f8e7f6ee2aab1bb350f60c180f5ae21a2c upstream. Since do_undefinstr() uses get_user to get the undefined instruction, it can be called before kprobes processes recurs

[PATCH 4.4 66/92] ARM: 8770/1: kprobes: Prohibit probing on optimized_callback

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 70948c05fdde0aac32f9667856a88725c192fa40 upstream. Prohibit probing on optimized_callback() because it is called from kprobes itself. If we put a kprobes on it, that wil

[PATCH 4.4 62/92] efi: Avoid potential crashes, fix the struct efi_pci_io_protocol_32 definition for mixed mode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 0b3225ab9407f557a8e20f23f37aa7236c10a9b1 upstream. Mixed mode allows a kernel built for x86_64 to interact with 32-bit EFI firmware, but requires us to define all struct d

[PATCH 4.4 59/92] s390/cpum_sf: ensure sample frequency of perf event attributes is non-zero

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hendrik Brueckner commit 4bbaf2584b86b0772413edeac22ff448f36351b1 upstream. Correct a trinity finding for the perf_event_open() system call with a perf event attribute structure that uses a fre

[PATCH 4.4 60/92] s390/qdio: dont release memory in qdio_setup_irq()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit 2e68adcd2fb21b7188ba449f0fab3bee2910e500 upstream. Calling qdio_release_memory() on error is just plain wrong. It frees the main qdio_irq struct, when following code stil

[PATCH 4.4 44/92] powerpc/powernv: remove FW_FEATURE_OPALv3 and just use FW_FEATURE_OPAL

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stewart Smith commit e4d54f71d29997344b4c4c8d47708240f9f23a5c upstream. Long ago, only in the lab, there was OPALv1 and OPALv2. Now there is just OPALv3, with nobody ever expecting anything on

[PATCH 4.4 64/92] tick/broadcast: Use for_each_cpu() specially on UP kernels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit 5596fe34495cf0f645f417eb928ef224df3e3cb4 upstream. for_each_cpu() unintuitively reports CPU0 as set independent of the actual cpumask content on UP kernels. This causes an une

Re: [PATCH] leds: class: ensure workqueue is initialized before setting brightness

On Wed 2018-05-23 23:22:21, Luis Henriques wrote: > An application can try to set brightness before all the initialization is > done, in particular before the workqueue is initialized with the call to > led_init_core(). Here's a WARNING easy to trigger: Acked-by: Pavel Machek -- (english) http

Re: [PATCH V4] mlx4_core: allocate ICM memory in page size chunks

On 24/05/2018 2:22 AM, Qing Huang wrote: When a system is under memory presure (high usage with fragments), the original 256KB ICM chunk allocations will likely trigger kernel memory management to enter slow path doing memory compact/migration ops in order to complete high order memory allocati

[PATCH 4.4 61/92] s390: remove indirect branch from do_softirq_own_stack

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 9f18fff63cfd6f559daa1eaae60640372c65f84b upstream. The inline assembly to call __do_softirq on the irq stack uses an indirect branch. This can be replaced with a norma

[PATCH 4.4 58/92] s390/qdio: fix access to uninitialized qdio_q fields

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit e521813468f786271a87e78e8644243bead48fad upstream. Ever since CQ/QAOB support was added, calling qdio_free() straight after qdio_alloc() results in qdio_release_memory()

[PATCH 4.4 52/92] cpufreq: intel_pstate: Enable HWP by default

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada commit 7791e4aa59ad724e0b4c8b4dea547a5735108972 upstream. If the processor supports HWP, enable it by default without checking for the cpu model. This will allow to enable H

[PATCH 4.4 54/92] proc read mms {arg,env}_{start,end} with mmap semaphore taken.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mateusz Guzik commit a3b609ef9f8b1dbfe97034ccad6cd3fe71fbe7ab upstream. Only functions doing more than one read are modified. Consumeres happened to deal with possibly changing data, but it do

[PATCH 4.4 55/92] procfs: fix pthread cross-thread naming if !PR_DUMPABLE

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Janis Danisevskis commit 1b3044e39a89cb1d4d5313da477e8dfea2b5232d upstream. The PR_DUMPABLE flag causes the pid related paths of the proc file system to be owned by ROOT. The implementation of

[PATCH 4.4 56/92] powerpc/powernv: Fix NVRAM sleep in invalid context when crashing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit c1d2a31397ec51f0370f6bd17b19b39152c263cb upstream. Similarly to opal_event_shutdown, opal_nvram_write can be called in the crash path with irqs disabled. Special case the

Re: [PATCH] i2c-mux-reg: Delete an error message for a failed memory allocation in i2c_mux_reg_probe_dt()

On 2018-02-01 17:24, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 1 Feb 2018 17:17:19 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring Applied to i2

[PATCH 4.4 43/92] powerpc/powernv: Remove OPALv2 firmware define and references

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stewart Smith commit 7261aafc095763b119136a562540dea7b1ccf657 upstream. OPALv2 only ever existed in the lab and didn't escape to the world. All OPAL systems in the wild are OPALv3. The probabi

Re: [PATCH 09/14] arm64: ssbd: Introduce thread flag to control userspace mitigation

On Tue, May 22, 2018 at 04:06:43PM +0100, Marc Zyngier wrote: > In order to allow userspace to be mitigated on demand, let's > introduce a new thread flag that prevents the mitigation from > being turned off when exiting to userspace, and doesn't turn > it on on entry into the kernel (with the assu

[PATCH 4.4 53/92] tracing/x86/xen: Remove zero data size trace events trace_xen_mmu_flush_tlb{_all}

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 45dd9b0666a162f8e4be76096716670cf1741f0e upstream. Doing an audit of trace events, I discovered two trace events in the xen subsystem that use a hack to create ze

Re: [PATCH 4.4 50/92] mm: filemap: avoid unnecessary calls to lock_page when waiting for IO to complete during a read

On Thu 24-05-18 13:28:41, Greg KH wrote: > On Thu, May 24, 2018 at 04:17:12AM -0700, Hugh Dickins wrote: > > Thu, May 24, 2018 at 4:06 AM Greg Kroah-Hartman > > > > wrote: > > > > > On Thu, May 24, 2018 at 12:50:11PM +0200, Jan Kara wrote: > > > > On Thu 24-05-18 11:38:27, Greg Kroah-Hartman wr

[PATCH 4.4 05/92] llc: better deal with too small mtu

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 2c5d5b13c6eb79f5677e206b8aad59b3a2097f60 ] syzbot loves to set very small mtu on devices, since it brings joy. We must make llc_ui_sendmsg() fool proof. usercopy

[PATCH 4.4 13/92] sctp: handle two v4 addrs comparison in sctp_inet6_cmp_addr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit d625329b06e46bd20baf9ee40847d11982569204 ] Since sctp ipv6 socket also supports v4 addrs, it's possible to compare two v4 addrs in pf v6 .cmp_addr, sctp_inet6_cmp_add

RE: [PATCH 1/6] mfd: da9063: Rename PMIC_DA9063 to PMIC_CHIP_ID_DA9063

Hi Marek, On 23 May 2018 12:42 Marek Vasut wrote: > To: linux-kernel@vger.kernel.org > Cc: Marek Vasut ; Geert Uytterhoeven > ; Lee Jones ; Mark Brown > ; Steve Twiss ; Wolfram > Sang ; linux-renesas-...@vger.kernel.org > Subject: [PATCH 1/6] mfd: da9063: Rename PMIC_DA9063 to PMIC_CHIP_ID_DA9

Re: [PATCH v1 00/10] mm: online/offline 4MB chunks controlled by device driver

On Thu 24-05-18 12:45:50, David Hildenbrand wrote: > On 24.05.2018 11:31, Michal Hocko wrote: > > On Thu 24-05-18 10:31:30, David Hildenbrand wrote: [...] > >> Allowing to unplug such small chunks is actually the interesting thing. > > > > Not really. The vmemmap will stay behind and so you are st

[PATCH 4.4 12/92] r8169: fix powering up RTL8168h

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 3148dedfe79e422f448a10250d3e2cdf8b7ee617 ] Since commit a92a08499b1f "r8169: improve runtime pm in general and suspend unused ports" interfaces w/o link are ru

[PATCH 4.4 41/92] spi: pxa2xx: Allow 64-bit DMA

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit efc4a13724b852ddaa3358402a8dec024ffbcb17 upstream. Currently the 32-bit device address only is supported for DMA. However, starting from Intel Sunrisepoint PCH the DMA ad

[PATCH 4.4 39/92] ALSA: hda: Add Lenovo C50 All in one to the power_save blacklist

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit c8beccc19b92f5172994c0732db689c08f4f98e5 upstream. Power-saving is causing loud plops on the Lenovo C50 All in one, add it to the blacklist. BugLink: https://bugzilla.redh

[PATCH 4.4 38/92] ALSA: usb: mixer: volume quirk for CM102-A+/102S+

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Federico Cuello commit 21493316a3c4598f308d5a9fa31cc74639c4caff upstream. Currently it's not possible to set volume lower than 26% (it just mutes). Also fixes this warning: Warning! Unlikel

[PATCH 4.4 33/92] usbip: usbip_host: refine probe and disconnect debug msgs to be useful

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit 28b68acc4a88dcf91fd1dcf2577371dc9bf574cc upstream. Refine probe and disconnect debug msgs to be useful and say what is in progress. Signed-off-by: Shuah Khan Cc: stable Sig

[PATCH 4.4 35/92] usbip: usbip_host: run rebind from exit when module is removed

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 7510df3f29d44685bab7b1918b61a8ccd57126a9 upstream. After removing usbip_host module, devices it releases are left without a driver. For example, when a keyboard

[PATCH 4.4 25/92] futex: Remove duplicated code and fix undefined behaviour

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit 30d6e0a4190d37740e9447e4e4815f06992dd8c3 upstream. There is code duplicated over all architecture's headers for futex_atomic_op_inuser. Namely op decoding, access_ok check for

[PATCH 4.4 32/92] kernel/exit.c: avoid undefined behaviour when calling wait4()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: zhongjiang commit dd83c161fbcc5d8be637ab159c0de015cbff5ba4 upstream. wait4(-2147483648, 0x20, 0, 0xdd) triggers: UBSAN: Undefined behaviour in kernel/exit.c:1651:9 The related calltrace is

[PATCH 4.4 34/92] usbip: usbip_host: delete device from busid_table after rebind

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 1e180f167d4e413afccbbb4a421b48b2de832549 upstream. Device is left in the busid_table after unbind and rebind. Rebind initiates usb bus scan and the original driv

[PATCH 4.4 26/92] xfrm: fix xfrm_do_migrate() with AEAD e.g(AES-GCM)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Antony Antony commit 75bf50f4aaa1c78d769d854ab3d975884909e4fb upstream. copy geniv when cloning the xfrm state. x->geniv was not copied to the new state and migration would fail. xfrm_do_migr

[PATCH 4.4 31/92] futex: futex_wake_op, fix sign_extend32 sign bits

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit d70ef22892ed6c066e51e118b225923c9b74af34 upstream. sign_extend32 counts the sign bit parameter from 0, not from 1. So we have to use "11" for 12th bit, not "12". This mistak

Re: [PATCH] MIPS: lantiq: gphy: Drop reboot/remove reset asserts

On Mon, May 21, 2018 at 05:39:32PM +0100, James Hogan wrote: > On Sun, Apr 08, 2018 at 10:30:03AM +0200, Mathias Kresin wrote: > > While doing a global software reset, these bits are not cleared and let > > some bootloader fail to initialise the GPHYs. The bootloader don't > > expect the GPHYs in r

[PATCH 4.4 30/92] pipe: cap initial pipe capacity according to pipe-max-size limit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Kerrisk (man-pages) commit 086e774a57fba4695f14383c0818994c0b31da7c upstream. This is a patch that provides behavior that is more consistent, and probably less surprising to users. I co

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

Hi Rob, Am Mittwoch, 23. Mai 2018, 21:53:53 CEST schrieb Rob Herring: > On Wed, May 23, 2018 at 10:12 AM, Heiko Stübner wrote: > > Am Mittwoch, 23. Mai 2018, 16:43:07 CEST schrieb Rob Herring: > >> On Tue, May 22, 2018 at 9:02 PM, Levin Du wrote: > >> > On 2018-05-23 2:02 AM, Rob Herring wrote:

[PATCH 4.4 27/92] lockd: lost rollback of set_grace_period() in lockd_down_net()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit 3a2b19d1ee5633f76ae8a88da7bc039a5d1732aa upstream. Commit efda760fe95ea ("lockd: fix lockd shutdown race") is incorrect, it removes lockd_manager and disarm grace_period_en

[PATCH 4.4 28/92] Revert "ARM: dts: imx6qdl-wandboard: Fix audio channel swap"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 9de3a3bfed892608dc30a6bc3fd8bdbeae5b51a5 which was commit 79935915300c5eb88a0e94fa9148a7505c14a02a upstream. As Ben points out: This depends on:

[PATCH 4.4 24/92] futex: Remove unnecessary warning from get_futex_key

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit 48fb6f4db940e92cfb16cd878cddd59ea6120d06 upstream. Commit 65d8fc777f6d ("futex: Remove requirement for lock_page() in get_futex_key()") removed an unnecessary lock_page() with

[PATCH 4.4 07/92] net/mlx4_en: Verify coalescing parameters are in range

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Moshe Shemesh [ Upstream commit 6ad4e91c6d796b38a7f0e724db1de28eeb122bad ] Add check of coalescing parameters received through ethtool are within range of values supported by the HW. Driver get

[PATCH 4.4 22/92] arm64: introduce mov_q macro to move a constant into a 64-bit register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 30b5ba5cf333cc650e474eaf2cc1ae91bc7cf89f upstream. Implement a macro mov_q that can be used to move an immediate constant into a 64-bit register, using between 2 and 4 mov

[PATCH 4.4 20/92] ALSA: timer: Call notifier in the same spinlock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit f65e0d299807d8a11812845c972493c3f9a18e10 upstream. snd_timer_notify1() is called outside the spinlock and it retakes the lock after the unlock. This is rather racy, and it'

[PATCH 4.4 06/92] net: ethernet: sun: niu set correct packet size in skb

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Rob Taglang [ Upstream commit 14224923c3600bae2ac4dcae3bf0c3d4dc2812be ] Currently, skb->len and skb->data_len are set to the page size, not the packet size. This causes the frame check sequenc

Re: [PATCH 10/14] arm64: ssbd: Add prctl interface for per-thread mitigation

On Tue, May 22, 2018 at 04:06:44PM +0100, Marc Zyngier wrote: > If running on a system that performs dynamic SSBD mitigation, allow > userspace to request the mitigation for itself. This is implemented > as a prctl call, allowing the mitigation to be enabled or disabled at > will for this particula

[PATCH 4.4 18/92] sctp: fix the issue that the cookie-ack with auth cant get processed

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit ce402f044e4e432c296f90eaabb8dbe8f3624391 ] When auth is enabled for cookie-ack chunk, in sctp_inq_pop, sctp processes auth chunk first, then continues to the next chu

[PATCH 4.4 17/92] tcp: ignore Fast Open on repair mode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yuchung Cheng [ Upstream commit 16ae6aa1705299789f71fdea59bfb119c1fbd9c0 ] The TCP repair sequence of operation is to first set the socket in repair mode, then inject the TCP stats into the soc

[PATCH 4.4 15/92] tg3: Fix vunmap() BUG_ON() triggered from tg3_free_consistent().

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Chan [ Upstream commit d89a2adb8bfe6f8949ff389acdb9fa298b6e8e12 ] tg3_free_consistent() calls dma_free_coherent() to free tp->hw_stats under spinlock and can trigger BUG_ON() in vunmap(

Re: [PATCH 02/14] arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1

On 24/05/18 11:52, Mark Rutland wrote: On Wed, May 23, 2018 at 10:23:20AM +0100, Julien Grall wrote: Hi Marc, On 05/22/2018 04:06 PM, Marc Zyngier wrote: diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S index ec2ee720e33e..f33e6aed3037 100644 --- a/arch/arm64/kernel/entry.S +

[PATCH 4.4 00/92] 4.4.133-stable review

This is the start of the stable review cycle for the 4.4.133 release. There are 92 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 May 26 09:31:28 UTC 2018. Anything receiv

[PATCH 4.4 16/92] bonding: do not allow rlb updates to invalid mac

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Debabrata Banerjee [ Upstream commit 4fa8667ca3989ce14cf66301fa251544fbddbdd0 ] Make sure multicast, broadcast, and zero mac's cannot be the output of rlb updates, which should all be directed

Re: [PATCH 11/14] arm64: KVM: Add HYP per-cpu accessors

On Tue, May 22, 2018 at 04:06:45PM +0100, Marc Zyngier wrote: > As we're going to require to access per-cpu variables at EL2, > let's craft the minimum set of accessors required to implement > reading a per-cpu variable, relying on tpidr_el2 to contain the > per-cpu offset. > > Reviewed-by: Christ

[PATCH 4.4 03/92] dccp: fix tasklet usage

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit a8d7aa17bbc970971ccdf71988ea19230ab368b1 ] syzbot reported a crash in tasklet_action_common() caused by dccp. dccp needs to make sure socket wont disappear befor

[PATCH 3.18 22/45] kernel/exit.c: avoid undefined behaviour when calling wait4()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: zhongjiang commit dd83c161fbcc5d8be637ab159c0de015cbff5ba4 upstream. wait4(-2147483648, 0x20, 0, 0xdd) triggers: UBSAN: Undefined behaviour in kernel/exit.c:1651:9 The related calltrace i

[PATCH 3.18 25/45] usbip: usbip_host: run rebind from exit when module is removed

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 7510df3f29d44685bab7b1918b61a8ccd57126a9 upstream. After removing usbip_host module, devices it releases are left without a driver. For example, when a keyboard

[PATCH 4.4 01/92] 8139too: Use disable_irq_nosync() in rtl8139_poll_controller()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ingo Molnar [ Upstream commit af3e0fcf78879f718c5f73df0814951bd7057d34 ] Use disable_irq_nosync() instead of disable_irq() as this might be called in atomic context with netpoll. Signed-off-by

[PATCH 3.18 26/45] usbip: fix error handling in stub_probe()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov commit 3ff67445750a84de67faaf52c6e1895cb09f2c56 upstream. If usb_hub_claim_port() fails, no resources are deallocated and if stub_add_files() fails, port is not released. T

[PATCH 3.18 24/45] usbip: usbip_host: delete device from busid_table after rebind

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 1e180f167d4e413afccbbb4a421b48b2de832549 upstream. Device is left in the busid_table after unbind and rebind. Rebind initiates usb bus scan and the original dri

[PATCH 3.18 21/45] pipe: cap initial pipe capacity according to pipe-max-size limit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Kerrisk (man-pages) commit 086e774a57fba4695f14383c0818994c0b31da7c upstream. This is a patch that provides behavior that is more consistent, and probably less surprising to users. I c

Re: [PATCH 1/1] mmc: sdhci-pci-dwc-mshc: synopsys dwc mshc support

On 24/05/18 14:28, Prabu Thangamuthu wrote: > Hi Adrian, > > On 5/24/2018 2:06 PM, Adrian Hunter wrote: >> Hi >> >> This patch is mangled. > We will check it. >> >> On 22/05/18 09:42, Prabu Thangamuthu wrote: >>> To enable Synopsys DWC MSHC controller on HPAS-DX platform connected using >>> PCIe i

Re: [RFC PATCH 0/5] kmalloc-reclaimable caches

On Thu, May 24, 2018 at 01:00:06PM +0200, Vlastimil Babka wrote: > Hi, > > as discussed at LSF/MM [1] here's a RFC patchset that introduces > kmalloc-reclaimable caches (more details in the first patch) and uses them > for SLAB freelists and dcache external names. The latter allows us to > repurpo

[PATCH 3.18 45/45] x86/kexec: Avoid double free_page() upon do_kexec_load() failure

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit a466ef76b815b86748d9870ef2a430af7b39c710 upstream. >From ff82bedd3e12f0d3353282054ae48c3bd8c72012 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Wed, 9 May 2018 12:12:3

[PATCH 3.18 43/45] cfg80211: limit wiphy names to 128 bytes

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit a7cfebcb7594a24609268f91299ab85ba064bf82 upstream. There's currently no limit on wiphy names, other than netlink message size and memory limitations, but that causes issue

[PATCH 3.18 42/45] scsi: sg: allocate with __GFP_ZERO in sg_build_indirect()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko commit a45b599ad808c3c982fdcdc12b0b8611c2f92824 upstream. This shall help avoid copying uninitialized memory to the userspace when calling ioctl(fd, SG_IO) with an empty co

Re: [PATCH 12/14] arm64: KVM: Add ARCH_WORKAROUND_2 support for guests

On Tue, May 22, 2018 at 04:06:46PM +0100, Marc Zyngier wrote: > In order to offer ARCH_WORKAROUND_2 support to guests, we need > a bit of infrastructure. > > Let's add a flag indicating whether or not the guest uses > SSBD mitigation. Depending on the state of this flag, allow > KVM to disable ARC

[PATCH 3.18 19/45] Revert "ARM: dts: imx6qdl-wandboard: Fix audio channel swap"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 2ebf343cbed76773563223761586fd5edcd0dc61 which was commit 79935915300c5eb88a0e94fa9148a7505c14a02a upstream. As Ben points out: This depends on:

[PATCH 3.18 39/45] tcp: purge write queue in tcp_connect_init()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7f582b248d0a86bae5788c548d7bb5bca6f7691a ] syzkaller found a reliable way to crash the host, hitting a BUG() in __tcp_retransmit_skb() Malicous MSG_FASTOPEN is

Re: [PATCH 09/14] arm64: ssbd: Introduce thread flag to control userspace mitigation

On 24/05/18 13:01, Mark Rutland wrote: > On Tue, May 22, 2018 at 04:06:43PM +0100, Marc Zyngier wrote: >> In order to allow userspace to be mitigated on demand, let's >> introduce a new thread flag that prevents the mitigation from >> being turned off when exiting to userspace, and doesn't turn >>

[PATCH 3.18 38/45] net: test tailroom before appending to linear skb

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 113f99c3358564a0647d444c2ae34e8b1abfd5b9 ] Device features may change during transmission. In particular with corking, a device may toggle scatter-gather in

Re: [PATCH 07/24] arm64: ilp32: add documentation on the ILP32 ABI for ARM64

Hi Pavel, On Wed, May 23, 2018 at 04:06:20PM +0200, Pavel Machek wrote: > On Wed 2018-05-16 11:18:52, Yury Norov wrote: > > Based on Andrew Pinski's patch-series. > > > > Signed-off-by: Yury Norov > > So Andrew's signoff should be here? Yes it should, but it lost since v4. I'll restore it. >

[PATCH 3.18 36/45] tick/broadcast: Use for_each_cpu() specially on UP kernels

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit 5596fe34495cf0f645f417eb928ef224df3e3cb4 upstream. for_each_cpu() unintuitively reports CPU0 as set independent of the actual cpumask content on UP kernels. This causes an un

[PATCH 3.18 35/45] ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit eb0146daefdde65665b7f076fbff7b49dade95b9 upstream. Prohibit kprobes on do_undefinstr because kprobes on arm is implemented by undefined instruction. This means if we pr

[PATCH 3.18 32/45] tracing/x86/xen: Remove zero data size trace events trace_xen_mmu_flush_tlb{_all}

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 45dd9b0666a162f8e4be76096716670cf1741f0e upstream. Doing an audit of trace events, I discovered two trace events in the xen subsystem that use a hack to create z

[PATCH 3.18 31/45] powerpc: Dont preempt_disable() in show_cpuinfo()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit 349524bc0da698ec77f2057cf4a4948eb6349265 upstream. This causes warnings from cpufreq mutex code. This is also rather unnecessary and ineffective. If we really wan

Re: [PATCH 8/9] PM / Domains: Add support for multi PM domains per device to genpd

On 24 May 2018 at 11:36, Jon Hunter wrote: > > On 24/05/18 08:04, Ulf Hansson wrote: > > ... > >>> Any reason why we could not add a 'boolean' argument to the API to >>> indicate >>> whether the new device should be linked? I think that I prefer the API >>> handles it, but I can see there could be

[PATCH 3.18 34/45] efi: Avoid potential crashes, fix the struct efi_pci_io_protocol_32 definition for mixed mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 0b3225ab9407f557a8e20f23f37aa7236c10a9b1 upstream. Mixed mode allows a kernel built for x86_64 to interact with 32-bit EFI firmware, but requires us to define all struct

[PATCH 3.18 30/45] ALSA: control: fix a redundant-copy issue

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang commit 3f12888dfae2a48741c4caa9214885b3aaf350f9 upstream. In snd_ctl_elem_add_compat(), the fields of the struct 'data' need to be copied from the corresponding fields of the struc

Re: [PATCH v1] cpufreq: tegra20: Fix imbalanced clock enable count

On 24.05.2018 12:36, Rafael J. Wysocki wrote: > On Wednesday, May 23, 2018 11:30:39 AM CEST Dmitry Osipenko wrote: >> On 23.05.2018 08:58, Viresh Kumar wrote: >>> On 23-05-18, 00:14, Dmitry Osipenko wrote: Tegra20-cpufreq driver missed enabling the CPU clocks. This results in a clock-enab

Re: [External] Re: [RFC PATCH v2 00/12] get rid of GFP_ZONE_TABLE/BAD

On Wed 23-05-18 16:07:16, Huaisheng HS1 Ye wrote: > From: Michal Hocko [mailto:mho...@kernel.org] > Sent: Wednesday, May 23, 2018 2:37 AM > > > > On Mon 21-05-18 23:20:21, Huaisheng Ye wrote: > > > From: Huaisheng Ye > > > > > > Replace GFP_ZONE_TABLE and GFP_ZONE_BAD with encoded zone number. >

[PATCH 3.18 28/45] usbip: usbip_host: fix bad unlock balance during stub_probe()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit c171654caa875919be3c533d3518da8be5be966e upstream. stub_probe() calls put_busid_priv() in an error path when device isn't found in the busid_table. Fix it by ma

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

Hi Levin, Am Donnerstag, 24. Mai 2018, 03:59:36 CEST schrieb Levin Du: > Hi all, I'd like to quote reply of Robin Murphy at > http://lists.infradead.org/pipermail/linux-rockchip/2018-May/020619.html > > > > > I would suggest s/pin number/bit number in the associated GRF register/ > > here. At l

Re: [PATCH 09/14] arm64: ssbd: Introduce thread flag to control userspace mitigation

On Thu, May 24, 2018 at 01:16:38PM +0100, Marc Zyngier wrote: > On 24/05/18 13:01, Mark Rutland wrote: > > On Tue, May 22, 2018 at 04:06:43PM +0100, Marc Zyngier wrote: > >> In order to allow userspace to be mitigated on demand, let's > >> introduce a new thread flag that prevents the mitigation fr

Re: [RESEND PATCH 2/5] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

On 24.05.2018 13:53, Boris Brezillon wrote: > Hi Benjamin, > > On Thu, 24 May 2018 13:30:14 +0200 > Benjamin Lindqvist wrote: > >> Hi Stefan, >> >> It seems to me that a probe similar to what the BootROM does shouldn't >> be awfully complicated to implement - just cycle through the switch >> cas

[PATCH 3.18 00/45] 3.18.110-stable review

This is the start of the stable review cycle for the 3.18.110 release. There are 45 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 May 26 09:30:59 UTC 2018. Anything recei

[PATCH 3.18 27/45] usbip: usbip_host: fix NULL-ptr deref and use-after-free errors

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 22076557b07c12086eeb16b8ce2b0b735f7a27e7 upstream. usbip_host updates device status without holding lock from stub probe, disconnect and rebind code paths. When

[PATCH 3.18 06/45] net: ethernet: sun: niu set correct packet size in skb

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Rob Taglang [ Upstream commit 14224923c3600bae2ac4dcae3bf0c3d4dc2812be ] Currently, skb->len and skb->data_len are set to the page size, not the packet size. This causes the frame check sequen

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