[PATCH 4.14 125/165] udl-kms: change down_interruptible to down

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

[PATCH 4.14 097/165] kprobes/arm64: Fix %p uses in error messages

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

[PATCH 4.14 126/165] udl-kms: handle allocation failure

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

Re: [PATCH net v2] net: bcmgenet: use MAC link status for fixed phy

On 8/31/2018 10:59 PM, David Miller wrote: From: Doug Berger Date: Wed, 29 Aug 2018 11:27:49 -0700 When using the fixed PHY with GENET (e.g. MOCA) the PHY link status can be determined from the internal link status captured by the MAC. This allows the PHY state machine to use the correct

[PATCH 4.14 114/165] x86/vdso: Fix vDSO build if a retpoline is emitted

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

[PATCH 4.14 118/165] fuse: Dont access pipe->buffers without pipe_lock()

4.14-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 4.14 115/165] x86/process: Re-export start_thread()

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

[PATCH 4.14 125/165] udl-kms: change down_interruptible to down

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

[PATCH 4.14 097/165] kprobes/arm64: Fix %p uses in error messages

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

[PATCH 4.14 126/165] udl-kms: handle allocation failure

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

Re: [PATCH net v2] net: bcmgenet: use MAC link status for fixed phy

On 8/31/2018 10:59 PM, David Miller wrote: From: Doug Berger Date: Wed, 29 Aug 2018 11:27:49 -0700 When using the fixed PHY with GENET (e.g. MOCA) the PHY link status can be determined from the internal link status captured by the MAC. This allows the PHY state machine to use the correct

[PATCH 4.14 114/165] x86/vdso: Fix vDSO build if a retpoline is emitted

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

[PATCH 4.14 119/165] fuse: fix initial parallel dirops

4.14-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.14 120/165] fuse: fix double request_end()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 87114373ea507895a62afb10d2910bd9adac35a8 upstream. Refcounting of request is broken when fuse_abort_conn() is called and request is on the fpq->io list: - ref is taken

[PATCH 4.14 123/165] fuse: Fix oops at process_init_reply()

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

[PATCH 4.14 119/165] fuse: fix initial parallel dirops

4.14-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.14 120/165] fuse: fix double request_end()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 87114373ea507895a62afb10d2910bd9adac35a8 upstream. Refcounting of request is broken when fuse_abort_conn() is called and request is on the fpq->io list: - ref is taken

[PATCH 4.14 123/165] fuse: Fix oops at process_init_reply()

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

[PATCH 4.14 096/165] printk/nmi: Prevent deadlock when accessing the main log buffer in NMI

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

[PATCH 4.14 117/165] x86/kvm/vmx: Remove duplicate l1d flush definitions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 94d7a86c21a3d6046bf4616272313cb7d525075a upstream. These are already defined higher up in the file. Fixes: 7db92e165ac8 ("x86/kvm: Move l1tf setup function")

[PATCH 4.14 124/165] fuse: Add missed unlock_page() to fuse_readpages_fill()

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

[PATCH 4.14 121/165] fuse: fix unlocked access to processing queue

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

[PATCH 4.14 122/165] fuse: umount should wait for all requests

4.14-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()

[PATCH 4.14 121/165] fuse: fix unlocked access to processing queue

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

[PATCH 4.14 122/165] fuse: umount should wait for all requests

4.14-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()

[PATCH 4.14 117/165] x86/kvm/vmx: Remove duplicate l1d flush definitions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 94d7a86c21a3d6046bf4616272313cb7d525075a upstream. These are already defined higher up in the file. Fixes: 7db92e165ac8 ("x86/kvm: Move l1tf setup function")

[PATCH 4.14 124/165] fuse: Add missed unlock_page() to fuse_readpages_fill()

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

[PATCH 4.14 096/165] printk/nmi: Prevent deadlock when accessing the main log buffer in NMI

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

[PATCH 4.14 113/165] x86/speculation/l1tf: Suggest what to do on systems with too much RAM

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

[PATCH 4.14 110/165] mm/tlb, x86/mm: Support invalidating TLB caches for RCU_TABLE_FREE

4.14-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().

[PATCH 4.14 112/165] x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM

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

[PATCH 4.14 109/165] platform/x86: ideapad-laptop: Apply no_hw_rfkill to Y20-15IKBM, too

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

[PATCH 4.14 065/165] arc: [plat-eznps] fix data type errors in platform headers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit b1f32ce1c3d2c11959b7e6a2c58dc5197c581966 ] Add to fix build errors. Both ctop.h and use u32 types and cause many errors. Examples:

[PATCH 4.14 095/165] printk: Create helper function to queue deferred console handling

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

[PATCH 4.14 108/165] nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

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

[PATCH 4.14 109/165] platform/x86: ideapad-laptop: Apply no_hw_rfkill to Y20-15IKBM, too

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

[PATCH 4.14 065/165] arc: [plat-eznps] fix data type errors in platform headers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit b1f32ce1c3d2c11959b7e6a2c58dc5197c581966 ] Add to fix build errors. Both ctop.h and use u32 types and cause many errors. Examples:

[PATCH 4.14 095/165] printk: Create helper function to queue deferred console handling

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

[PATCH 4.14 108/165] nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

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

[PATCH 4.14 113/165] x86/speculation/l1tf: Suggest what to do on systems with too much RAM

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

[PATCH 4.14 110/165] mm/tlb, x86/mm: Support invalidating TLB caches for RCU_TABLE_FREE

4.14-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().

[PATCH 4.14 112/165] x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM

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

[PATCH 4.14 104/165] stop_machine: Atomically queue and wake stopper threads

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

[PATCH 4.14 107/165] ext4: reset error code in ext4_find_entry in fallback

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

[PATCH 4.14 105/165] ext4: check for NUL characters in extended attributes name

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

[PATCH 4.14 111/165] x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit

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

[PATCH 4.14 107/165] ext4: reset error code in ext4_find_entry in fallback

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

[PATCH 4.14 105/165] ext4: check for NUL characters in extended attributes name

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

[PATCH 4.14 111/165] x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit

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

[PATCH 4.14 104/165] stop_machine: Atomically queue and wake stopper threads

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

[PATCH 4.14 056/165] ipc/sem.c: prevent queue.status tearing in semop

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Davidlohr Bueso [ Upstream commit f075faa300acc4f6301e348acde0a4580ed5f77c ] In order for load/store tearing prevention to work, _all_ accesses to the variable in question need to be done

[PATCH 4.14 106/165] ext4: sysfs: print ext4_super_block fields as little-endian

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

[PATCH 4.14 106/165] ext4: sysfs: print ext4_super_block fields as little-endian

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

[PATCH 4.14 056/165] ipc/sem.c: prevent queue.status tearing in semop

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Davidlohr Bueso [ Upstream commit f075faa300acc4f6301e348acde0a4580ed5f77c ] In order for load/store tearing prevention to work, _all_ accesses to the variable in question need to be done

[PATCH 4.14 063/165] enic: handle mtu change for vf properly

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Govindarajulu Varadarajan [ Upstream commit ab123fe071c9aa9680ecd62eb080eb26cff4892c ] When driver gets notification for mtu change, driver does not handle it for all RQs. It handles only

[PATCH 4.14 063/165] enic: handle mtu change for vf properly

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Govindarajulu Varadarajan [ Upstream commit ab123fe071c9aa9680ecd62eb080eb26cff4892c ] When driver gets notification for mtu change, driver does not handle it for all RQs. It handles only

[PATCH 4.14 064/165] ARC: [plat-eznps] Add missing struct nps_host_reg_aux_dpc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ofer Levi [ Upstream commit 05b466bf846d2e8d2f0baf8dfd81a42cc933e237 ] Fixing compilation issue caused by missing struct nps_host_reg_aux_dpc definition. Fixes: 3f9cd874dcc87 ("ARC:

[PATCH 4.14 064/165] ARC: [plat-eznps] Add missing struct nps_host_reg_aux_dpc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ofer Levi [ Upstream commit 05b466bf846d2e8d2f0baf8dfd81a42cc933e237 ] Fixing compilation issue caused by missing struct nps_host_reg_aux_dpc definition. Fixes: 3f9cd874dcc87 ("ARC:

[PATCH 4.14 093/165] iommu/arm-smmu: Error out only if not enough context interrupts

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

[PATCH 4.14 061/165] bpf: use GFP_ATOMIC instead of GFP_KERNEL in bpf_parse_prog()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Taehee Yoo [ Upstream commit 71eb5255f55bdb484d35ff7c9a1803f453dfbf82 ] bpf_parse_prog() is protected by rcu_read_lock(). so that GFP_KERNEL is not allowed in the bpf_parse_prog().

[PATCH 4.14 060/165] ARC: dma [non-IOC] setup SMP_CACHE_BYTES and cache_line_size

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eugeniy Paltsev [ Upstream commit eb2777397fd83a4a7eaa26984d09d3babb845d2a ] As for today we don't setup SMP_CACHE_BYTES and cache_line_size for ARC, so they are set to L1_CACHE_BYTES by

[PATCH 4.14 092/165] Btrfs: fix btrfs_write_inode vs delayed iput deadlock

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

IRQ number question.

Hi, I'm writing a kernel driver. It is not going to be widely used, so I'm not motivated to make things nice enough for inclusion in the standard kernel. But lspci shows my device: 03:01.0 Serial bus controller [0c80]: Phoenix Contact GmbH & Co. Device 0002 (rev b7) Flags: bus

[PATCH 4.14 062/165] nfp: flower: fix port metadata conversion bug

4.14-stable review patch. If anyone has any objections, please let me know. -- From: John Hurley [ Upstream commit ee614c871014045b45fae149b7245fc22a0bbdd8 ] Function nfp_flower_repr_get_type_and_port expects an enum nfp_repr_type return value but, if the repr type is

[PATCH 4.14 093/165] iommu/arm-smmu: Error out only if not enough context interrupts

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

[PATCH 4.14 061/165] bpf: use GFP_ATOMIC instead of GFP_KERNEL in bpf_parse_prog()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Taehee Yoo [ Upstream commit 71eb5255f55bdb484d35ff7c9a1803f453dfbf82 ] bpf_parse_prog() is protected by rcu_read_lock(). so that GFP_KERNEL is not allowed in the bpf_parse_prog().

[PATCH 4.14 060/165] ARC: dma [non-IOC] setup SMP_CACHE_BYTES and cache_line_size

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eugeniy Paltsev [ Upstream commit eb2777397fd83a4a7eaa26984d09d3babb845d2a ] As for today we don't setup SMP_CACHE_BYTES and cache_line_size for ARC, so they are set to L1_CACHE_BYTES by

[PATCH 4.14 092/165] Btrfs: fix btrfs_write_inode vs delayed iput deadlock

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

IRQ number question.

Hi, I'm writing a kernel driver. It is not going to be widely used, so I'm not motivated to make things nice enough for inclusion in the standard kernel. But lspci shows my device: 03:01.0 Serial bus controller [0c80]: Phoenix Contact GmbH & Co. Device 0002 (rev b7) Flags: bus

[PATCH 4.14 062/165] nfp: flower: fix port metadata conversion bug

4.14-stable review patch. If anyone has any objections, please let me know. -- From: John Hurley [ Upstream commit ee614c871014045b45fae149b7245fc22a0bbdd8 ] Function nfp_flower_repr_get_type_and_port expects an enum nfp_repr_type return value but, if the repr type is

[PATCH 4.14 091/165] btrfs: dont leak ret from do_chunk_alloc

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

[PATCH 4.14 089/165] smb3: fill in statfs fsid and correct namelen

4.14-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.14 091/165] btrfs: dont leak ret from do_chunk_alloc

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

[PATCH 4.14 089/165] smb3: fill in statfs fsid and correct namelen

4.14-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.14 088/165] smb3: dont request leases in symlink creation and query

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

[STABLE 4.4] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+

From: Andi Kleen [upstream cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4 for 4.4. Note there might be still a trivial conflict with the backport for b0a182f875689647b014bc01d36b340217792852, but should be easy to resolve] On Nehalem and newer core CPUs the CPU cache internally uses 44 bits physical

[PATCH 4.14 090/165] btrfs: use correct compare function of dirty_metadata_bytes

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

[PATCH 4.14 087/165] smb3: Do not send SMB3 SET_INFO if nothing changed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit fd09b7d3b352105f08b8e02f7afecf7e816380ef upstream. An earlier commit had a typo which prevented the optimization from working: commit 18dd8e1a65dd ("Do not send SMB3

[PATCH 4.14 085/165] cifs: check kmalloc before use

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire commit 126c97f4d0d1b5b956e8b0740c81a2b2a2ae548c upstream. The kmalloc was not being checked - if it fails issue a warning and return -ENOMEM to the caller. Signed-off-by:

[PATCH 4.14 088/165] smb3: dont request leases in symlink creation and query

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

[STABLE 4.4] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+

From: Andi Kleen [upstream cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4 for 4.4. Note there might be still a trivial conflict with the backport for b0a182f875689647b014bc01d36b340217792852, but should be easy to resolve] On Nehalem and newer core CPUs the CPU cache internally uses 44 bits physical

[PATCH 4.14 090/165] btrfs: use correct compare function of dirty_metadata_bytes

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

[PATCH 4.14 087/165] smb3: Do not send SMB3 SET_INFO if nothing changed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit fd09b7d3b352105f08b8e02f7afecf7e816380ef upstream. An earlier commit had a typo which prevented the optimization from working: commit 18dd8e1a65dd ("Do not send SMB3

[PATCH 4.14 085/165] cifs: check kmalloc before use

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire commit 126c97f4d0d1b5b956e8b0740c81a2b2a2ae548c upstream. The kmalloc was not being checked - if it fails issue a warning and return -ENOMEM to the caller. Signed-off-by:

[PATCH 4.14 086/165] smb3: enumerating snapshots was leaving part of the data off end

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit e02789a53d71334b067ad72eee5d4e88a0158083 upstream. When enumerating snapshots, the last few bytes of the final snapshot could be left off since we were miscalculating the

[PATCH 4.14 086/165] smb3: enumerating snapshots was leaving part of the data off end

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit e02789a53d71334b067ad72eee5d4e88a0158083 upstream. When enumerating snapshots, the last few bytes of the final snapshot could be left off since we were miscalculating the

[PATCH 4.14 084/165] cifs: add missing debug entries for kconfig options

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

[PATCH 4.14 084/165] cifs: add missing debug entries for kconfig options

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

[PATCH 4.14 083/165] mei: dont update offset in write

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

[PATCH 4.14 083/165] mei: dont update offset in write

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

[PATCH 4.14 080/165] scsi: fcoe: clear FC_RP_STARTED flags when receiving a LOGO

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn [ Upstream commit 1550ec458e0cf1a40a170ab1f4c46e3f52860f65 ] When receiving a LOGO request we forget to clear the FC_RP_STARTED flag before starting the rport delete

[PATCH 4.14 081/165] scsi: vmw_pvscsi: Return DID_RESET for status SAM_STAT_COMMAND_TERMINATED

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jim Gill [ Upstream commit e95153b64d03c2b6e8d62e51bdcc33fcad6e0856 ] Commands that are reset are returned with status SAM_STAT_COMMAND_TERMINATED. PVSCSI currently returns DID_OK |

[PATCH 4.14 082/165] mm/memory.c: check return value of ioremap_prot

4.14-stable review patch. If anyone has any objections, please let me know. -- From: "jie@chenj...@huwei.com" [ Upstream commit 24eee1e4c47977bdfb71d6f15f6011e7b6188d04 ] ioremap_prot() can return NULL which could lead to an oops. Link:

[PATCH 4.14 081/165] scsi: vmw_pvscsi: Return DID_RESET for status SAM_STAT_COMMAND_TERMINATED

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jim Gill [ Upstream commit e95153b64d03c2b6e8d62e51bdcc33fcad6e0856 ] Commands that are reset are returned with status SAM_STAT_COMMAND_TERMINATED. PVSCSI currently returns DID_OK |

[PATCH 4.14 082/165] mm/memory.c: check return value of ioremap_prot

4.14-stable review patch. If anyone has any objections, please let me know. -- From: "jie@chenj...@huwei.com" [ Upstream commit 24eee1e4c47977bdfb71d6f15f6011e7b6188d04 ] ioremap_prot() can return NULL which could lead to an oops. Link:

[PATCH 4.14 080/165] scsi: fcoe: clear FC_RP_STARTED flags when receiving a LOGO

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn [ Upstream commit 1550ec458e0cf1a40a170ab1f4c46e3f52860f65 ] When receiving a LOGO request we forget to clear the FC_RP_STARTED flag before starting the rport delete

[PATCH 4.14 073/165] mm: delete historical BUG from zap_pmd_range()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hugh Dickins [ Upstream commit 53406ed1bcfdabe4b5bc35e6d17946c6f9f563e2 ] Delete the old VM_BUG_ON_VMA() from zap_pmd_range(), which asserted that mmap_sem must be held when splitting an

[PATCH 4.14 073/165] mm: delete historical BUG from zap_pmd_range()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hugh Dickins [ Upstream commit 53406ed1bcfdabe4b5bc35e6d17946c6f9f563e2 ] Delete the old VM_BUG_ON_VMA() from zap_pmd_range(), which asserted that mmap_sem must be held when splitting an

[PATCH 4.14 072/165] squashfs metadata 2: electric boogaloo

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds [ Upstream commit cdbb65c4c7ead680ebe54f4f0d486e2847a500ea ] Anatoly continues to find issues with fuzzed squashfs images. This time, corrupt, missing, or undersized data for

[PATCH 4.14 072/165] squashfs metadata 2: electric boogaloo

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds [ Upstream commit cdbb65c4c7ead680ebe54f4f0d486e2847a500ea ] Anatoly continues to find issues with fuzzed squashfs images. This time, corrupt, missing, or undersized data for

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