[PATCH 4.14 058/165] tools/power turbostat: Read extended processor family from CPUID

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Walton [ Upstream commit 5aa3d1a20a233d4a5f1ec3d62da3f19d9afea682 ] This fixes the reported family on modern AMD processors (e.g. Ryzen, which is family 0x17). Previously these processo

[PATCH 4.14 075/165] drivers: net: lmc: fix case value for target abort error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit afb41bb039656f0cecb54eeb8b2e2088201295f5 ] Current value for a target abort error is 0x010, however, this value should in fact be 0x002. As it stands, the ran

[PATCH 4.14 078/165] scsi: fcoe: fix use-after-free in fcoe_ctlr_els_send

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn [ Upstream commit 2d7d4fd35e6e15b47c13c70368da83add19f01e7 ] KASAN reports a use-after-free in fcoe_ctlr_els_send() when we're sending a LOGO and have FIP debugging enabled.

[PATCH 4.14 146/165] s390/pci: fix out of bounds access during irq setup

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 866f3576a72b2233a76dffb80290f8086dc49e17 upstream. During interrupt setup we allocate interrupt vectors, walk the list of msi descriptors, and fill in the message data. Re

[PATCH 4.14 076/165] memcg: remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Tkhai [ Upstream commit 7e97de0b033bcac4fa9a35cef72e0c06e6a22c67 ] In case of memcg_online_kmem() failure, memcg_cgroup::id remains hashed in mem_cgroup_idr even after memcg memory is f

[PATCH 4.18 018/123] Btrfs: fix btrfs_write_inode vs delayed iput deadlock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 3c4276936f6fbe52884b4ea4e6cc120b890a0f9f upstream. We recently ran into the following deadlock involving btrfs_write_inode(): [ +0.005066] __schedule+0x38e/0x8c0 [ +0.00

[PATCH 4.18 013/123] smb3: dont request leases in symlink creation and query

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit 22783155f4bf956c346a81624ec9258930a6fe06 upstream. Fixes problem pointed out by Pavel in discussions about commit 729c0c9dd55204f0c9a823ac8a7bfa83d36c7e78 Signed-off-by: P

[PATCH 4.18 015/123] btrfs: use correct compare function of dirty_metadata_bytes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ethan Lien commit d814a49198eafa6163698bdd93961302f3a877a4 upstream. We use customized, nodesize batch value to update dirty_metadata_bytes. We should also use batch version of compare functio

[PATCH 4.18 017/123] Btrfs: fix mount failure after fsync due to hard link recreation

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 0d836392cadd5535f4184d46d901a82eb276ed62 upstream. If we end up with logging an inode reference item which has the same name but different index from the one we have persi

[PATCH 4.18 016/123] btrfs: dont leak ret from do_chunk_alloc

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 4559b0a71749c442d34f7cfb9e72c9e58db83948 upstream. If we're trying to make a data reservation and we have to allocate a data chunk we could leak ret == 1, as do_chunk_alloc(

[PATCH 4.18 014/123] smb3: fill in statfs fsid and correct namelen

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit 21ba3845b59c733a79ed4fe1c4f3732e7ece9df7 upstream. Fil in the correct namelen (typically 255 not 4096) in the statfs response and also fill in a reasonably unique fsid (in

[PATCH 4.18 019/123] Btrfs: fix send failure when root has deleted files still open

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 46b2f4590aab71d31088a265c86026b1e96c9de4 upstream. The more common use case of send involves creating a RO snapshot and then use it for a send operation. In this case it's

[PATCH 4.18 002/123] scripts/kernel-doc: Escape all literal braces in regexes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 673bb2dfc36488abfdbbfc2ce2631204eaf682f2 upstream. Commit 701b3a3c0ac4 ("PATCH scripts/kernel-doc") fixed the two instances of literal braces that Perl 5.28 warns about, b

[PATCH 4.18 021/123] hwmon: (k10temp) 27C Offset needed for Threadripper2

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Larabel commit 484a84f25ca7817c3662001316ba7d1e06b74ae2 upstream. For at least the Threadripper 2950X and Threadripper 2990WX, it's confirmed a 27 degree offset is needed. Signed-off-

[PATCH 4.18 022/123] bpf, arm32: fix stack var offset in jit

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann Commit 38ca93060163 ("bpf, arm32: save 4 bytes of unneeded stack space") messed up STACK_VAR() by 4 bytes presuming it was related to skb scratch buffer space, but it clearly is

[PATCH 4.18 020/123] Btrfs: send, fix incorrect file layout after hole punching beyond eof

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 22d3151c2c4cb517a309154d1e828a28106508c7 upstream. When doing an incremental send, if we have a file in the parent snapshot that has prealloc extents beyond EOF and in the

[PATCH 4.18 025/123] printk: Split the code for storing a message into the log buffer

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Petr Mladek commit ba552399954dde1b388f7749fecad5c349216981 upstream. It is just a preparation step. The patch does not change the existing behavior. Link: http://lkml.kernel.org/r/2018062714

[PATCH 4.18 023/123] regulator: arizona-ldo1: Use correct device to get enable GPIO

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit a9191579ba1086d91842199263e6fe6bb5eec1ba upstream. Currently the enable GPIO is being looked up on the regulator device itself but that does not have its own DT node, thi

[PATCH 4.18 024/123] iommu/arm-smmu: Error out only if not enough context interrupts

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vivek Gautam commit d1e20222d5372e951bbb2fd3f6489ec4a6ea9b11 upstream. Currently we check if the number of context banks is not equal to num_context_interrupts. However, there are booloaders s

[PATCH 4.18 026/123] printk: Create helper function to queue deferred console handling

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Petr Mladek commit a338f84dc196f44b63ba0863d2f34fd9b1613572 upstream. It is just a preparation step. The patch does not change the existing behavior. Link: http://lkml.kernel.org/r/2018062714

[PATCH 4.18 027/123] printk/nmi: Prevent deadlock when accessing the main log buffer in NMI

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Petr Mladek commit 03fc7f9c99c1e7ae2925d459e8487f1a6f199f79 upstream. The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI when logbuf_lock is available") brought back the possib

[PATCH 4.18 028/123] kprobes/arm64: Fix %p uses in error messages

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 0722867dcbc28cc9b269b57acd847c7c1aa638d6 upstream. Fix %p uses in error messages by removing it because those are redundant or meaningless. Signed-off-by: Masami Hiram

[PATCH 4.18 029/123] arm64: Fix mismatched cache line size detection

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit 4c4a39dd5fe2d13e2d2fa5fceb8ef95d19fc389a upstream. If there is a mismatch in the I/D min line size, we must always use the system wide safe value both in applications a

[PATCH 4.18 031/123] arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Hackmann commit 5ad356eabc47d26a92140a0c4b20eba471c10de3 upstream. ARM64's pfn_valid() shifts away the upper PAGE_SHIFT bits of the input before seeing if the PFN is valid. This leads to

[PATCH 4.18 003/123] scsi: libsas: dynamically allocate and free ata host

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jason Yan commit 2fa4a32613c9182b00e46872755b0662374424a7 upstream. Commit 2623c7a5f2 ("libata: add refcounting to ata_host") v4.17+ introduced refcounting to ata_host and will increase or dec

[PATCH 4.18 004/123] xprtrdma: Fix disconnect regression

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever commit 8d4fb8ff427a23e573c9373b2bb3d1d6e8ea4399 upstream. I found that injecting disconnects with v4.18-rc resulted in random failures of the multi-threaded git regression test. T

[PATCH 4.18 030/123] arm64: Handle mismatched cache type

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit 314d53d297980676011e6fd83dac60db4a01dc70 upstream. Track mismatches in the cache type register (CTR_EL0), other than the D/I min line sizes and trap user accesses if th

[PATCH 4.18 006/123] cifs: add missing support for ACLs in SMB 3.11

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ronnie Sahlberg commit c1777df1a5d541cda918ff0450c8adcc8b69c2fd upstream. We were missing the methods for get_acl and friends for the 3.11 dialect. Signed-off-by: Ronnie Sahlberg Signed-off-

[PATCH 4.18 007/123] CIFS: fix uninitialized ptr deref in smb2 signing

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Aurelien Aptel commit a5c62f4833c2c8e6e0f35367b99b717b78f5c029 upstream. server->secmech.sdeschmacsha256 is not properly initialized before smb2_shash_allocate(), set shash after that call. a

[PATCH 4.18 009/123] cifs: use a refcount to protect open/closing the cached file handle

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ronnie Sahlberg commit 9da6ec7775d2cd76df53fbf4f1f35f6d490204f5 upstream. Signed-off-by: Ronnie Sahlberg Signed-off-by: Steve French Reviewed-by: Pavel Shilovsky Cc: Signed-off-by: Greg Kr

[PATCH 4.18 005/123] mei: dont update offset in write

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Usyskin commit a103af1b64d74853a5e08ca6c86aeb0e5c6ca4f1 upstream. MEI enables writes of complete messages only while read can be performed in parts, hence write should not update the

[PATCH 4.18 008/123] cifs: add missing debug entries for kconfig options

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit 950132afd59385caf6e2b84e5235d069fa10681d upstream. /proc/fs/cifs/DebugData displays the features (Kconfig options) used to build cifs.ko but it was missing some, and needed

[PATCH 4.18 033/123] KVM: arm/arm64: Fix potential loss of ptimer interrupts

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall commit 7afc4ddbf299a13aaf28406783d141a34c6b4f5a upstream. kvm_timer_update_state() is called when changing the phys timer configuration registers, either via vcpu reset, as a

[PATCH 4.18 000/123] 4.18.6-stable review

This is the start of the stable review cycle for the 4.18.6 release. There are 123 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 Wed Sep 5 16:56:53 UTC 2018. Anything receiv

[PATCH 4.18 042/123] ext4: use ext4_warning() for sb_getblk failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Wang Shilong commit 5ef2a69993676a0dfd49bf60ae1323eb8a288366 upstream. Out of memory should not be considered as critical errors; so replace ext4_error() with ext4_warnig(). Signed-off-by: Wa

[PATCH 4.18 044/123] ext4: reset error code in ext4_find_entry in fallback

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit f39b3f45dbcb0343822cce31ea7636ad66e60bc2 upstream. When ext4_find_entry() falls back to "searching the old fashioned way" due to a corrupt dx dir, it needs to reset the err

[PATCH 4.18 043/123] ext4: sysfs: print ext4_super_block fields as little-endian

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit a4d2aadca184ece182418950d45ba4ffc7b652d2 upstream. While working on extended rand for last_error/first_error timestamps, I noticed that the endianess is wrong; we access t

[PATCH 4.18 050/123] mm/tlb, x86/mm: Support invalidating TLB caches for RCU_TABLE_FREE

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit d86564a2f085b79ec046a5cba90188e612352806 upstream. Jann reported that x86 was missing required TLB invalidates when he hit the !*batch slow path in tlb_remove_table(). T

[PATCH 4.18 054/123] x86/vdso: Fix vDSO build if a retpoline is emitted

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 2e549b2ee0e358bc758480e716b881f9cabedb6a upstream. Currently, if the vDSO ends up containing an indirect branch or call, GCC will emit the "external thunk" style of retp

[PATCH 4.18 045/123] ext4: fix race when setting the bitmap corrupted flag

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Wang Shilong commit 9af0b3d1257756394ebbd06b14937b557e3a756b upstream. Whenever we hit block or inode bitmap corruptions we set bit and then reduce this block group free inode/clusters counter

[PATCH 4.18 046/123] nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michal Wnukowski commit f1ed3df20d2d223e0852cc4ac1f19bba869a7e3c upstream. In many architectures loads may be reordered with older stores to different locations. In the nvme driver the follow

[PATCH 4.18 052/123] x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit b0a182f875689647b014bc01d36b340217792852 upstream. Two users have reported [1] that they have an "extremely unlikely" system with more than MAX_PA/2 memory and L1TF miti

[PATCH 4.18 051/123] x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit 9df9516940a61d29aedf4d91b483ca6597e7d480 upstream. On 32bit PAE kernels on 64bit hardware with enough physical bits, l1tf_pfn_limit() will overflow unsigned long. This i

[PATCH 4.18 047/123] x86/gpu: reserve ICLs graphics stolen memory

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Paulo Zanoni commit db0c8d8b031d2b5960f6407f7f2ca20e97e00605 upstream. ICL changes the registers and addresses to 64 bits. I also briefly looked at implementing an u64 version of the PCI conf

[PATCH 4.18 049/123] platform/x86: ideapad-laptop: Apply no_hw_rfkill to Y20-15IKBM, too

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 58e73aa177850babb947555257fd4f79e5275cf1 upstream. The commit 5d9f40b56630 ("platform/x86: ideapad-laptop: Add Y520-15IKBN to no_hw_rfkill") added the entry for Y20-15IKBN,

[PATCH 4.18 034/123] KVM: arm/arm64: Fix lost IRQs from emulated physcial timer when blocked

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall commit 245715cbe83ca934af5d20e078fd85175c62995e upstream. When the VCPU is blocked (for example from WFI) we don't inject the physical timer interrupt if it should fire while

[PATCH 4.18 056/123] KVM: x86: ensure all MSRs can always be KVM_GET/SET_MSRd

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 44883f01fe6ae436a8604c47d8435276fef369b0 upstream. Some of the MSRs returned by GET_MSR_INDEX_LIST currently cannot be sent back to KVM_GET_MSR and/or KVM_SET_MSR; either

[PATCH 4.18 055/123] x86/process: Re-export start_thread()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rian Hunter commit dc76803e57cc86589c4efcb5362918f9b0c0436f upstream. The consolidation of the start_thread() functions removed the export unintentionally. This breaks binfmt handlers built as

[PATCH 4.18 053/123] x86/speculation/l1tf: Suggest what to do on systems with too much RAM

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka commit 6a012288d6906fee1dbc244050ade1dafe4a9c8d upstream. Two users have reported [1] that they have an "extremely unlikely" system with more than MAX_PA/2 memory and L1TF miti

[PATCH 4.18 035/123] KVM: arm/arm64: Skip updating PMD entry if no change

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Punit Agrawal commit 86658b819cd0a9aa584cd84453ed268a6f013770 upstream. Contention on updating a PMD entry by a large number of vcpus can lead to duplicate work when handling stage 2 page faul

[PATCH 4.18 062/123] fuse: umount should wait for all requests

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit b8f95e5d13f5f0191dcb4b9113113d241636e7cb upstream. fuse_abort_conn() does not guarantee that all async requests have actually finished aborting (i.e. their ->end() functi

[PATCH 4.18 036/123] KVM: arm/arm64: Skip updating PTE entry if no change

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Punit Agrawal commit 976d34e2dab10ece5ea8fe7090b7692913f89084 upstream. When there is contention on faulting in a particular page table entry at stage 2, the break-before-make requirement of t

[PATCH 4.18 058/123] fuse: Dont access pipe->buffers without pipe_lock()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit a2477b0e67c52f4364a47c3ad70902bc2a61bd4c upstream. fuse_dev_splice_write() reads pipe->buffers to determine the size of 'bufs' array before taking the pipe_lock(). This

[PATCH trivial] scsi: arcmsr: Spelling s/rebulid/rebuild/

Signed-off-by: Geert Uytterhoeven --- drivers/scsi/arcmsr/arcmsr_hba.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c index 12316ef4c8931853..cc0be46511281050 100644 --- a/drivers/scsi/

[PATCH 4.18 064/123] fuse: Add missed unlock_page() to fuse_readpages_fill()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Tkhai commit 109728ccc5933151c68d1106e4065478a487a323 upstream. The above error path returns with page unlocked, so this place seems also to behave the same. Fixes: f8dbdf81821b ("fuse

[PATCH 4.18 066/123] udl-kms: change down_interruptible to down

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 8456b99c16d193c4c3b7df305cf431e027f0189c upstream. If we leave urbs around, it causes not only leak, but also memory corruption. This patch fixes the function udl_free_u

[PATCH 4.18 061/123] fuse: fix unlocked access to processing queue

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 45ff350bbd9d0f0977ff270a0d427c71520c0c37 upstream. fuse_dev_release() assumes that it's the only one referencing the fpq->processing list, but that's not true, since fuse

[PATCH 4.18 059/123] fuse: fix initial parallel dirops

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 63576c13bd17848376c8ba4a98f5d5151140c4ac upstream. If parallel dirops are enabled in FUSE_INIT reply, then first operation may leave fi->mutex held. Reported-by: syzbot

[PATCH 4.18 065/123] lib/vsprintf: Do not handle %pO[^F] as %px

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 554ec508653688c21d9b8024af73a1ffaa0164b9 upstream. This patch avoids that gcc reports the following when building with W=1: lib/vsprintf.c:1941:3: warning: this stateme

[PATCH 4.18 067/123] udl-kms: handle allocation failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 542bb9788a1f485eb1a2229178f665d8ea166156 upstream. Allocations larger than PAGE_ALLOC_COSTLY_ORDER are unreliable and they may fail anytime. This patch fixes the udl kms

[PATCH 4.18 063/123] fuse: Fix oops at process_init_reply()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit e8f3bd773d22f488724dffb886a1618da85c2966 upstream. syzbot is hitting NULL pointer dereference at process_init_reply(). This is because deactivate_locked_super() is called

[PATCH 4.18 037/123] s390/kvm: fix deadlock when killed by oom

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Claudio Imbrenda commit 306d6c49ac9ded4cb53b0925da52f2c2ada1 upstream. When the oom killer kills a userspace process in the page fault handler while in guest context, the fault handler fai

[PATCH 4.18 038/123] perf kvm: Fix subcommands on s390

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Richter commit 8a95c8994509c55abf1e38c0cc037b1205725e21 upstream. With commit eca0fa28cd0d ("perf record: Provide detailed information on s390 CPU") s390 platform provides detailed type

[PATCH 4.18 041/123] ext4: check for NUL characters in extended attributes name

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 7d95178c77014dbd8dce36ee40bbbc5e6c121ff5 upstream. Extended attribute names are defined to be NUL-terminated, so the name must not contain a NUL character. This is import

[PATCH 4.18 040/123] stop_machine: Atomically queue and wake stopper threads

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Prasad Sodagudi commit cfd355145c32bb7ccb65fccbe2d67280dc2119e1 upstream. When cpu_stop_queue_work() releases the lock for the stopper thread that was queued into its wake queue, preemption is

[PATCH 4.18 081/123] x86/irqflags: Mark native_restore_fl extern inline

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nick Desaulniers commit 1f59a4581b5ecfe9b4f049a7a2cf904d8352842d upstream. This should have been marked extern inline in order to pick up the out of line definition in arch/x86/kernel/irqflags

[PATCH 4.18 079/123] x86/vdso: Fix lsl operand order

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Samuel Neves commit e78e5a91456fcecaa2efbb3706572fe043766f4d upstream. In the __getcpu function, lsl is using the wrong target and destination registers. Luckily, the compiler tends to choose

[PATCH 4.18 039/123] stop_machine: Reflow cpu_stop_queue_two_works()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b80a2bfce85e1051056d98d04ecb2d0b55cbbc1c upstream. The code flow in cpu_stop_queue_two_works() is a little arcane; fix this by lifting the preempt_disable() to the top to

[PATCH 4.18 084/123] hwmon: (nct6775) Fix potential Spectre v1

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

[PATCH 4.18 082/123] x86/spectre: Add missing family 6 check to microcode check

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit 1ab534e85c93945f7862378d8c8adcf408205b19 upstream. The check for Spectre microcodes does not check for family 6, only the model numbers. Add a family 6 check to avoid ambigu

[PATCH 4.18 078/123] scsi: qla2xxx: Fix stalled relogin

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Himanshu Madhani commit 15b6c3c9568765f0717b2dd3aa67a5f7eadd9734 upstream. This patch sets and clears FCF_ASYNC_{SENT|ACTIVE} flags to prevent stalling of relogin attempt. Once flag are correc

[PATCH 4.18 032/123] arm64: dts: rockchip: corrected uart1 clock-names for rk3328

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Huibin Hong commit d0414fdd58eb51ffd6528280fd66705123663964 upstream. Corrected the uart clock-names or the uart driver might fail. Fixes: 52e02d377a72 ("arm64: dts: rockchip: add core dtsi f

[PATCH 4.18 080/123] x86/nmi: Fix NMI uaccess race against CR3 switching

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 4012e77a903d114f915fc607d6d2ed54a3d6c9b1 upstream. A NMI can hit in the middle of context switching or in the middle of switch_mm_irqs_off(). In either case, CR3 might

[PATCH 4.18 069/123] udl-kms: avoid division

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 91ba11fb7d7ca0a3bbe8a512e65e666e2ec1e889 upstream. Division is slow, so it shouldn't be done by the pixel generating code. The driver supports only 2 or 4 bytes per pixe

[PATCH 4.18 083/123] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4 upstream. On Nehalem and newer core CPUs the CPU cache internally uses 44 bits physical address space. The L1TF workaround is limited

[PATCH 4.18 085/123] x86/entry/64: Wipe KASAN stack shadow before rewind_stack_do_exit()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit f12d11c5c184626b4befdee3d573ec8237405a33 upstream. Reset the KASAN shadow state of the task stack before rewinding RSP. Without this, a kernel oops will leave parts of the sta

[PATCH 4.18 070/123] b43legacy/leds: Ensure NUL-termination of LED name string

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Buesch commit 4d77a89e3924b12f4a5628b21237e57ab4703866 upstream. strncpy might not NUL-terminate the string, if the name equals the buffer size. Use strlcpy instead. Signed-off-by: Mi

[PATCH 4.18 088/123] s390/lib: use expoline for all bcr instructions

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 5eda25b10297684c1f46a14199ec00210f3c346e upstream. The memove, memset, memcpy, __memset16, __memset32 and __memset64 function have an additional indirect return branc

[PATCH 4.18 089/123] s390: fix br_r1_trampoline for machines without exrl

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 26f843848bae973817b3587780ce6b7b0200d3e4 upstream. For machines without the exrl instruction the BFP jit generates code that uses an "br %r1" instruction located in t

[PATCH 4.18 087/123] s390/mm: fix addressing exception after suspend/resume

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gerald Schaefer commit 37a366face294facb9c9d9fdd9f5b64a27456cbd upstream. Commit c9b5ad546e7d "s390/mm: tag normal pages vs pages used in page tables" accidentally changed the logic in arch_se

[PATCH 4.18 086/123] x86: Allow generating user-space headers without a compiler

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 829fe4aa9ac16417a904ad1de1307de906854bcf upstream. When bootstrapping an architecture, it's usual to generate the kernel's user-space headers (make headers_install) before

[PATCH 4.18 092/123] s390/pci: fix out of bounds access during irq setup

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 866f3576a72b2233a76dffb80290f8086dc49e17 upstream. During interrupt setup we allocate interrupt vectors, walk the list of msi descriptors, and fill in the message data. Re

[PATCH 4.18 093/123] s390/purgatory: Fix crash with expoline enabled

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Philipp Rudo commit ad03b821fbc30395b72af438f5bb41676a5f891d upstream. When the kernel is built with CONFIG_EXPOLINE=y and a compiler with indirect branch mitigation enabled the purgatory cras

[PATCH 4.18 095/123] kprobes: Show blacklist addresses as same as kallsyms does

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit ffb9bd68ebdb3b8d00ef5a79bbe8167a3281cace upstream. Show kprobes blacklist addresses under same condition of showing kallsyms addresses. Since there are several name co

[PATCH 4.18 091/123] s390/numa: move initial setup of node_to_cpumask_map

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit fb7d7518b0d65955f91c7b875c36eae7694c69bd upstream. The numa_init_early initcall sets the node_to_cpumask_map[0] to the full cpu_possible_mask. Unfortunately this earl

[PATCH 4.18 096/123] kprobes: Replace %p with other pointer types

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 4458515b2c52831ee622411d2fe3e774d1f5c49a upstream. Replace %p with %pS or just remove it if unneeded. And use WARN_ONCE() if it is a single bug. Signed-off-by: Masami

[PATCH 4.18 094/123] s390/purgatory: Add missing FORCE to Makefile targets

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Philipp Rudo commit c315e69308c739a43c4ebc539bedbc1ac8d79854 upstream. Without FORCE make does not detect changes only made to the command line options. So object files might not be re-built e

[PATCH 4.18 090/123] s390/qdio: reset old sbal_state flags

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit 64e03ff72623b8c2ea89ca3cb660094e019ed4ae upstream. When allocating a new AOB fails, handle_outbound() is still capable of transmitting the selected buffer (just without

[PATCH 4.18 101/123] MIPS: Always use -march=, not - shortcuts

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton commit 344ebf09949c31bcb8818d8458b65add29f1d67b upstream. The VDSO Makefile filters CFLAGS to select a subset which it uses whilst building the VDSO ELF. One of the flags it allows

[PATCH 4.18 102/123] MIPS: Change definition of cpu_relax() for Loongson-3

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit a30718868915fbb991a9ae9e45594b059f28e9ae upstream. Linux expects that if a CPU modifies a memory location, then that modification will eventually become visible to other CPU

[PATCH 4.18 098/123] kprobes: Make list and blacklist root user read only

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit f2a3ab36077222437b4826fc76111caa14562b7c upstream. Since the blacklist and list files on debugfs indicates a sensitive address information to reader, it should be restr

[PATCH 4.18 072/123] ASoC: dpcm: dont merge format from invalid codec dai

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jerome Brunet commit 4febced15ac8ddb9cf3e603edb111842e4863d9a upstream. When merging codec formats, dpcm_runtime_base_format() should skip the codecs which are not supporting the current strea

[PATCH 4.18 097/123] kprobes/arm: Fix %p uses in error messages

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 75b2f5f5911fe7a2fc82969b2b24dde34e8f820d upstream. Fix %p uses in error messages by removing it and using general dumper. Signed-off-by: Masami Hiramatsu Cc: Ananth N

[PATCH 4.18 100/123] MIPS: memset.S: Fix byte_fixup for MIPSr6

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Matt Redfearn commit b1c03f1ef48d36ff28afb06e8f0c1233ef072f1d upstream. The __clear_user function is defined to return the number of bytes that could not be cleared. From the underlying memset

[PATCH 4.18 073/123] ASoC: zte: Fix incorrect PCM format bit usages

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit c889a45d229938a94b50aadb819def8bb11a6a54 upstream. zx-tdm driver sets the DAI driver definitions with the format bits wrongly set with SNDRV_PCM_FORMAT_*, instead of SNDRV_

[PATCH 4.18 071/123] b43/leds: Ensure NUL-termination of LED name string

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Buesch commit 2aa650d1950fce94f696ebd7db30b8830c2c946f upstream. strncpy might not NUL-terminate the string, if the name equals the buffer size. Use strlcpy instead. Signed-off-by: Mi

[PATCH 4.18 104/123] tpm: Return the actual size when receiving an unsupported command

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Schwarzmeier commit 36a11029b07ee30bdc4553274d0efea645ed9d91 upstream. The userpace expects to read the number of bytes stated in the header. Returning the size of the buffer instead w

[PATCH 4.18 099/123] MIPS: Correct the 64-bit DSP accumulator register size

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit f5958b4cf4fc38ed4583ab83fb7c4cd1ab05f47b upstream. Use the `unsigned long' rather than `__u32' type for DSP accumulator registers, like with the regular MIPS multiply/

[PATCH 4.18 103/123] MIPS: lib: Provide MIPS64r6 __multi3() for GCC < 7

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton commit 690d9163bf4b8563a2682e619f938e6a0443947f upstream. Some versions of GCC suboptimally generate calls to the __multi3() intrinsic for MIPS64r6 builds, resulting in link failur

[PATCH 4.18 076/123] soc: qcom: rmtfs-mem: fix memleak in probe error paths

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 78ee559d7fc65e37670a46cfbeaaa62cb014af67 upstream. Make sure to set the mem device release callback before calling put_device() in a couple of probe error paths so that the

<    3   4   5   6   7   8   9   10   11   >