[PATCH 4.18 095/158] wlcore: Set rx_status boottime_ns field on rx

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Loic Poulain [ Upstream commit 37a634f60fd6dfbda2c312657eec7ef0750546e7 ] When receiving a beacon or probe response, we should update the boottime_ns field which is the timestamp the frame

[PATCH 4.18 097/158] mtd: rawnand: make subop helpers return unsigned values

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miquel Raynal [ Upstream commit 760c435e0f85ed19e48a90d746ce1de2cd02def7 ] A report from Colin Ian King pointed a CoverityScan issue where error values on these helpers where not checked in

[PATCH 4.18 102/158] nfs: Referrals not inheriting proto setting from parent

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Calum Mackay [ Upstream commit 23a88ade7131aa259c532ab17685c76de562242b ] Commit 530ea4219231 ("nfs: Referrals should use the same proto setting as their parent") encloses the fix with #ifdef

[PATCH 4.18 101/158] ata: libahci: Correct setting of DEVSLP register

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada [ Upstream commit 2dbb3ec29a6c069035857a2fc4c24e80e5dfe3cc ] We have seen that on some platforms, SATA device never show any DEVSLP residency. This prevent power gating of

[PATCH 4.18 098/158] scsi: tcmu: do not set max_blocks if data_bitmap has been setup

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mike Christie [ Upstream commit c97840c84f5a4362a596a2751e9245a979377a16 ] This patch prevents a bug where data_bitmap is allocated in tcmu_configure_device, userspace changes the max_blocks

[PATCH 4.18 095/158] wlcore: Set rx_status boottime_ns field on rx

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Loic Poulain [ Upstream commit 37a634f60fd6dfbda2c312657eec7ef0750546e7 ] When receiving a beacon or probe response, we should update the boottime_ns field which is the timestamp the frame

[PATCH 4.18 097/158] mtd: rawnand: make subop helpers return unsigned values

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miquel Raynal [ Upstream commit 760c435e0f85ed19e48a90d746ce1de2cd02def7 ] A report from Colin Ian King pointed a CoverityScan issue where error values on these helpers where not checked in

[PATCH 4.18 102/158] nfs: Referrals not inheriting proto setting from parent

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Calum Mackay [ Upstream commit 23a88ade7131aa259c532ab17685c76de562242b ] Commit 530ea4219231 ("nfs: Referrals should use the same proto setting as their parent") encloses the fix with #ifdef

[PATCH 4.18 100/158] ata: libahci: Allow reconfigure of DEVSLP register

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada [ Upstream commit 11c291461b6ea8d1195a96d6bba6673a94aacebc ] There are two modes in which DEVSLP can be entered. The OS initiated or hardware autonomous. In hardware

[PATCH 4.18 099/158] MIPS: Fix ISA virt/bus conversion for non-zero PHYS_OFFSET

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton [ Upstream commit 0494d7ffdcebc6935410ea0719b24ab626675351 ] isa_virt_to_bus() & isa_bus_to_virt() claim to treat ISA bus addresses as being identical to physical addresses, but

[PATCH 4.18 075/158] iwlwifi: pcie: dont access periphery registers when not available

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach [ Upstream commit f98ad635c097c29339b7a7d6947173000485893d ] The periphery can't be accessed before we set the INIT_DONE bit which initializes the device. A previous patch

[PATCH 4.18 096/158] rpmsg: core: add support to power domains for devices

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Kandagatla [ Upstream commit fe782affd0f440a4e60e2cc81b8f2eccb2923113 ] Some of the rpmsg devices need to switch on power domains to communicate with remote processor. For example on

[PATCH 4.18 099/158] MIPS: Fix ISA virt/bus conversion for non-zero PHYS_OFFSET

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton [ Upstream commit 0494d7ffdcebc6935410ea0719b24ab626675351 ] isa_virt_to_bus() & isa_bus_to_virt() claim to treat ISA bus addresses as being identical to physical addresses, but

[PATCH 4.18 100/158] ata: libahci: Allow reconfigure of DEVSLP register

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada [ Upstream commit 11c291461b6ea8d1195a96d6bba6673a94aacebc ] There are two modes in which DEVSLP can be entered. The OS initiated or hardware autonomous. In hardware

[PATCH 4.18 075/158] iwlwifi: pcie: dont access periphery registers when not available

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach [ Upstream commit f98ad635c097c29339b7a7d6947173000485893d ] The periphery can't be accessed before we set the INIT_DONE bit which initializes the device. A previous patch

[PATCH 4.18 096/158] rpmsg: core: add support to power domains for devices

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Kandagatla [ Upstream commit fe782affd0f440a4e60e2cc81b8f2eccb2923113 ] Some of the rpmsg devices need to switch on power domains to communicate with remote processor. For example on

Re: [PATCH 16/18] LSM: Allow arbitrary LSM ordering

On 9/18/18 00:36, John Johansen wrote: > On 09/17/2018 02:57 PM, Casey Schaufler wrote: >> On 9/17/2018 12:55 PM, John Johansen wrote: >>> On 09/17/2018 12:23 PM, Casey Schaufler wrote: On 9/17/2018 11:14 AM, Kees Cook wrote: >> Keep security=$lsm with the existing exclusive behavior.

[PATCH 4.18 090/158] macintosh/via-pmu: Add missing mmio accessors

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain [ Upstream commit 576d5290d678a651b9f36050fc1717e0573aca13 ] Add missing in_8() accessors to init_pmu() and pmu_sr_intr(). This fixes several sparse warnings:

[PATCH 4.18 035/158] cpu/hotplug: Adjust misplaced smb() in cpuhp_thread_fun()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Neeraj Upadhyay commit f8b7530aa0a1def79c93101216b5b17cf408a70a upstream. The smp_mb() in cpuhp_thread_fun() is misplaced. It needs to be after the load of st->should_run to prevent

[PATCH 4.18 074/158] uio: fix possible circular locking dependency

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Xiubo Li [ Upstream commit b34e9a15b37b8ddbf06a4da142b0c39c74211eb4 ] The call trace: XXX/1910 is trying to acquire lock: (>mmap_sem){++}, at: [] might_fault+0x57/0xb0 but task is

[PATCH 4.18 087/158] perf c2c report: Fix crash for empty browser

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa [ Upstream commit 73978332572ccf5e364c31e9a70ba953f8202b46 ] 'perf c2c' scans read/write accesses and tries to find false sharing cases, so when the events it wants were not asked

[PATCH RESEND] mm: don't raise MEMCG_OOM event due to failed high-order allocation

The memcg OOM killer is never invoked due to a failed high-order allocation, however the MEMCG_OOM event can be raised. As shown below, it can happen under conditions, which are very far from a real OOM: e.g. there is plenty of clean pagecache and low memory pressure. There is no sense in

[PATCH 4.18 044/158] tc-testing: remove duplicate spaces in connmark match patterns

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Buslov [ Upstream commit 757a9a39d483ae415a712388c33d4042a98b751f ] Match patterns for some connmark tests contain duplicate whitespace that is not present in actual tc output. This

[PATCH 4.18 092/158] ath9k: report tx status on EOSP

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit 36e14a787dd0b459760de3622e9709edb745a6af ] Fixes missed indications of end of U-APSD service period to mac80211 Signed-off-by: Felix Fietkau Signed-off-by:

[PATCH 4.18 089/158] powerpc/pseries: fix EEH recovery of some IOV devices

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sam Bobroff [ Upstream commit b87b9cf4935325c98522823caeddd333022a1c62 ] EEH recovery currently fails on pSeries for some IOV capable PCI devices, if CONFIG_PCI_IOV is on and the hypervisor

[PATCH 4.18 088/158] perf evlist: Fix error out while applying initial delay and LBR

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang [ Upstream commit 95035c5e167ae6e740b1ddd30210ae0eaf39a5db ] 'perf record' will error out if both --delay and LBR are applied. For example: # perf record -D 1000 -a -e cycles -j

[PATCH 4.18 085/158] device-dax: avoid hang on error before devm_memremap_pages()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Hajnoczi [ Upstream commit b7751410c180a05fdc21268f8661b1480169b0df ] dax_pmem_percpu_exit() waits for dax_pmem_percpu_release() to invoke the dax_pmem->cmp completion. Unfortunately

[PATCH 4.18 083/158] ASoC: soc-pcm: Use delay set in component pointer function

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akshu Agrawal [ Upstream commit 9fb4c2bf130b922c77c16a8368732699799c40de ] Take into account the base delay set in pointer callback. There are cases where a pointer function populates

Re: [PATCH 16/18] LSM: Allow arbitrary LSM ordering

On 9/18/18 00:36, John Johansen wrote: > On 09/17/2018 02:57 PM, Casey Schaufler wrote: >> On 9/17/2018 12:55 PM, John Johansen wrote: >>> On 09/17/2018 12:23 PM, Casey Schaufler wrote: On 9/17/2018 11:14 AM, Kees Cook wrote: >> Keep security=$lsm with the existing exclusive behavior.

[PATCH 4.18 090/158] macintosh/via-pmu: Add missing mmio accessors

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain [ Upstream commit 576d5290d678a651b9f36050fc1717e0573aca13 ] Add missing in_8() accessors to init_pmu() and pmu_sr_intr(). This fixes several sparse warnings:

[PATCH 4.18 035/158] cpu/hotplug: Adjust misplaced smb() in cpuhp_thread_fun()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Neeraj Upadhyay commit f8b7530aa0a1def79c93101216b5b17cf408a70a upstream. The smp_mb() in cpuhp_thread_fun() is misplaced. It needs to be after the load of st->should_run to prevent

[PATCH 4.18 074/158] uio: fix possible circular locking dependency

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Xiubo Li [ Upstream commit b34e9a15b37b8ddbf06a4da142b0c39c74211eb4 ] The call trace: XXX/1910 is trying to acquire lock: (>mmap_sem){++}, at: [] might_fault+0x57/0xb0 but task is

[PATCH 4.18 087/158] perf c2c report: Fix crash for empty browser

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa [ Upstream commit 73978332572ccf5e364c31e9a70ba953f8202b46 ] 'perf c2c' scans read/write accesses and tries to find false sharing cases, so when the events it wants were not asked

[PATCH RESEND] mm: don't raise MEMCG_OOM event due to failed high-order allocation

The memcg OOM killer is never invoked due to a failed high-order allocation, however the MEMCG_OOM event can be raised. As shown below, it can happen under conditions, which are very far from a real OOM: e.g. there is plenty of clean pagecache and low memory pressure. There is no sense in

[PATCH 4.18 044/158] tc-testing: remove duplicate spaces in connmark match patterns

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Buslov [ Upstream commit 757a9a39d483ae415a712388c33d4042a98b751f ] Match patterns for some connmark tests contain duplicate whitespace that is not present in actual tc output. This

[PATCH 4.18 092/158] ath9k: report tx status on EOSP

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit 36e14a787dd0b459760de3622e9709edb745a6af ] Fixes missed indications of end of U-APSD service period to mac80211 Signed-off-by: Felix Fietkau Signed-off-by:

[PATCH 4.18 089/158] powerpc/pseries: fix EEH recovery of some IOV devices

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sam Bobroff [ Upstream commit b87b9cf4935325c98522823caeddd333022a1c62 ] EEH recovery currently fails on pSeries for some IOV capable PCI devices, if CONFIG_PCI_IOV is on and the hypervisor

[PATCH 4.18 088/158] perf evlist: Fix error out while applying initial delay and LBR

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang [ Upstream commit 95035c5e167ae6e740b1ddd30210ae0eaf39a5db ] 'perf record' will error out if both --delay and LBR are applied. For example: # perf record -D 1000 -a -e cycles -j

[PATCH 4.18 085/158] device-dax: avoid hang on error before devm_memremap_pages()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Hajnoczi [ Upstream commit b7751410c180a05fdc21268f8661b1480169b0df ] dax_pmem_percpu_exit() waits for dax_pmem_percpu_release() to invoke the dax_pmem->cmp completion. Unfortunately

[PATCH 4.18 083/158] ASoC: soc-pcm: Use delay set in component pointer function

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akshu Agrawal [ Upstream commit 9fb4c2bf130b922c77c16a8368732699799c40de ] Take into account the base delay set in pointer callback. There are cases where a pointer function populates

[PATCH 4.18 086/158] NFSv4.0 fix client reference leak in callback

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Olga Kornievskaia [ Upstream commit 32cd3ee511f4e07ca25d71163b50e704808d22f4 ] If there is an error during processing of a callback message, it leads to refrence leak on the client structure

[PATCH 4.18 082/158] f2fs: fix to detect looped node chain correctly

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu [ Upstream commit 82902c06bd17dbf6e8184299842ca5c68880970f ] Below dmesg was printed when testing generic/388 of fstest: F2FS-fs (zram1): find_fsync_dnodes: detect looped node chain,

[PATCH 4.18 086/158] NFSv4.0 fix client reference leak in callback

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Olga Kornievskaia [ Upstream commit 32cd3ee511f4e07ca25d71163b50e704808d22f4 ] If there is an error during processing of a callback message, it leads to refrence leak on the client structure

[PATCH 4.18 082/158] f2fs: fix to detect looped node chain correctly

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu [ Upstream commit 82902c06bd17dbf6e8184299842ca5c68880970f ] Below dmesg was printed when testing generic/388 of fstest: F2FS-fs (zram1): find_fsync_dnodes: detect looped node chain,

[PATCH 4.18 093/158] ath9k_hw: fix channel maximum power level test

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit 461d8a6bb9879b0e619752d040292e67aa06f1d2 ] The tx power applied by set_txpower is limited by the CTL (conformance test limit) entries in the EEPROM. These can

[PATCH 4.18 094/158] ath10k: prevent active scans on potential unusable channels

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sven Eckelmann [ Upstream commit 3f259111583801013cb605bb4414aa529adccf1c ] The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most likely all other) seem to ignore the

[PATCH 4.18 091/158] perf build: Fix installation directory for eBPF

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Richter [ Upstream commit 83868bf71d2eb7700b37f1ea188007f0125e4ee4 ] The perf tool build and install is controlled via a Makefile. The 'install' rule creates directories and copies

[PATCH 4.18 093/158] ath9k_hw: fix channel maximum power level test

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit 461d8a6bb9879b0e619752d040292e67aa06f1d2 ] The tx power applied by set_txpower is limited by the CTL (conformance test limit) entries in the EEPROM. These can

[PATCH 4.18 094/158] ath10k: prevent active scans on potential unusable channels

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sven Eckelmann [ Upstream commit 3f259111583801013cb605bb4414aa529adccf1c ] The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most likely all other) seem to ignore the

[PATCH 4.18 091/158] perf build: Fix installation directory for eBPF

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Richter [ Upstream commit 83868bf71d2eb7700b37f1ea188007f0125e4ee4 ] The perf tool build and install is controlled via a Makefile. The 'install' rule creates directories and copies

[PATCH 4.18 043/158] tc-testing: flush gact actions on test teardown

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Buslov [ Upstream commit 0c62f8a820b7fdeacf5ad9f9e24b53043d372c97 ] Test 6fb4 creates one mirred and one pipe action, but only flushes mirred on teardown. Leaking pipe action causes

[PATCH 4.18 041/158] switchtec: Fix Spectre v1 vulnerability

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 46feb6b495f7628a6dbf36c4e6d80faf378372d4 upstream. p.port can is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.18 039/158] x86/process: Dont mix user/kernel regs in 64bit __show_regs()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 9fe6299dde587788f245e9f7a5a1b296fad4e8c7 upstream. When the kernel.print-fatal-signals sysctl has been enabled, a simple userspace crash will cause the kernel to write a

[PATCH 4.18 042/158] ARC: [plat-axs*]: Enable SWAP

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit c83532fb0fe053d2e43e9387354cb1b52ba26427 upstream. SWAP support on ARC was fixed earlier by commit 6e3761145a9b ("ARC: Fix CONFIG_SWAP") so now we may safely enable it

[PATCH 4.18 040/158] x86/apic/vector: Make error return value negative

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 47b7360ce563e18c524ce92b55fb4da72b3b3578 upstream. activate_managed() returns EINVAL instead of -EINVAL in case of error. While this is unlikely to happen, the positive

[PATCH 4.18 041/158] switchtec: Fix Spectre v1 vulnerability

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 46feb6b495f7628a6dbf36c4e6d80faf378372d4 upstream. p.port can is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.18 039/158] x86/process: Dont mix user/kernel regs in 64bit __show_regs()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 9fe6299dde587788f245e9f7a5a1b296fad4e8c7 upstream. When the kernel.print-fatal-signals sysctl has been enabled, a simple userspace crash will cause the kernel to write a

[PATCH 4.18 042/158] ARC: [plat-axs*]: Enable SWAP

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit c83532fb0fe053d2e43e9387354cb1b52ba26427 upstream. SWAP support on ARC was fixed earlier by commit 6e3761145a9b ("ARC: Fix CONFIG_SWAP") so now we may safely enable it

[PATCH 4.18 040/158] x86/apic/vector: Make error return value negative

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 47b7360ce563e18c524ce92b55fb4da72b3b3578 upstream. activate_managed() returns EINVAL instead of -EINVAL in case of error. While this is unlikely to happen, the positive

[PATCH 4.18 043/158] tc-testing: flush gact actions on test teardown

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Buslov [ Upstream commit 0c62f8a820b7fdeacf5ad9f9e24b53043d372c97 ] Test 6fb4 creates one mirred and one pipe action, but only flushes mirred on teardown. Leaking pipe action causes

[PATCH 4.18 071/158] firmware: vpd: Fix section enabled flag on vpd_section_destroy

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 45ca3f76de0507ecf143f770570af2942f263812 ] static struct ro_vpd and rw_vpd are initialized by vpd_sections_init() in vpd_probe() based on header's ro and rw

[PATCH 4.18 071/158] firmware: vpd: Fix section enabled flag on vpd_section_destroy

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 45ca3f76de0507ecf143f770570af2942f263812 ] static struct ro_vpd and rw_vpd are initialized by vpd_sections_init() in vpd_probe() based on header's ro and rw

[PATCH 4.18 053/158] powerpc/4xx: Fix error return path in ppc4xx_msi_probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit 6e0495c2e8ac39b1aad0a4588fe64413ce9028c0 ] An arbitrary error in ppc4xx_msi_probe() quite likely results in a crash similar to the following, seen after

[PATCH 4.18 070/158] uio: potential double frees if __uio_register_device() fails

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit f019f07ecf6a6b8bd6d7853bce70925d90af02d1 ] The uio_unregister_device() function assumes that if "info->uio_dev" is non-NULL that means "info" is fully

[PATCH 4.18 064/158] scsi: target: fix __transport_register_session locking

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mike Christie [ Upstream commit 6a64f6e1591322beb8ce16e952a53582caf2a15c ] When __transport_register_session is called from transport_register_session irqs will already have been disabled, so

[PATCH 4.14 123/126] tun: fix use after free for ptr_ring

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang commit b196d88aba8ac72b775137854121097f4c4c6862 upstream. We used to initialize ptr_ring during TUNSETIFF, this is because its size depends on the tx_queue_len of netdevice. And we

[PATCH 4.14 120/126] ip: process in-order fragments efficiently

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Oskolkov This patch changes the runtime behavior of IP defrag queue: incoming in-order fragments are added to the end of the current list/"run" of in-order fragments at the tail. On

[PATCH 4.18 054/158] selftests/bpf: fix a typo in map in map test

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Roman Gushchin [ Upstream commit 0069fb854364da79fd99236ea620affc8e1152d5 ] Commit fbeb1603bf4e ("bpf: verifier: MOV64 don't mark dst reg unbounded") revealed a typo in commit fb30d4b71214

[PATCH 4.18 055/158] media: davinci: vpif_display: Mix memory leak on probe error path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 61e641f36ed81ae473177c085f0bfd83ad3b55ed ] If vpif_probe() fails on v4l2_device_register() then memory allocated at initialize_vpif() for global

[PATCH 4.18 065/158] md/raid5: fix data corruption of replacements after originals dropped

4.18-stable review patch. If anyone has any objections, please let me know. -- From: BingJing Chang [ Upstream commit d63e2fc804c46e50eee825c5d3a7228e07048b47 ] During raid5 replacement, the stripes can be marked with R5_NeedReplace flag. Data can be read from being-replaced

[PATCH 4.18 066/158] timers: Clear timer_base::must_forward_clk with timer_base::lock held

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gaurav Kohli [ Upstream commit 363e934d8811d799c88faffc5bfca782fd728334 ] timer_base::must_forward_clock is indicating that the base clock might be stale due to a long idle sleep. The

[PATCH 4.18 053/158] powerpc/4xx: Fix error return path in ppc4xx_msi_probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit 6e0495c2e8ac39b1aad0a4588fe64413ce9028c0 ] An arbitrary error in ppc4xx_msi_probe() quite likely results in a crash similar to the following, seen after

[PATCH 4.18 070/158] uio: potential double frees if __uio_register_device() fails

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit f019f07ecf6a6b8bd6d7853bce70925d90af02d1 ] The uio_unregister_device() function assumes that if "info->uio_dev" is non-NULL that means "info" is fully

[PATCH 4.18 064/158] scsi: target: fix __transport_register_session locking

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mike Christie [ Upstream commit 6a64f6e1591322beb8ce16e952a53582caf2a15c ] When __transport_register_session is called from transport_register_session irqs will already have been disabled, so

[PATCH 4.14 123/126] tun: fix use after free for ptr_ring

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang commit b196d88aba8ac72b775137854121097f4c4c6862 upstream. We used to initialize ptr_ring during TUNSETIFF, this is because its size depends on the tx_queue_len of netdevice. And we

[PATCH 4.14 120/126] ip: process in-order fragments efficiently

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Oskolkov This patch changes the runtime behavior of IP defrag queue: incoming in-order fragments are added to the end of the current list/"run" of in-order fragments at the tail. On

[PATCH 4.18 054/158] selftests/bpf: fix a typo in map in map test

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Roman Gushchin [ Upstream commit 0069fb854364da79fd99236ea620affc8e1152d5 ] Commit fbeb1603bf4e ("bpf: verifier: MOV64 don't mark dst reg unbounded") revealed a typo in commit fb30d4b71214

[PATCH 4.18 055/158] media: davinci: vpif_display: Mix memory leak on probe error path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 61e641f36ed81ae473177c085f0bfd83ad3b55ed ] If vpif_probe() fails on v4l2_device_register() then memory allocated at initialize_vpif() for global

[PATCH 4.18 065/158] md/raid5: fix data corruption of replacements after originals dropped

4.18-stable review patch. If anyone has any objections, please let me know. -- From: BingJing Chang [ Upstream commit d63e2fc804c46e50eee825c5d3a7228e07048b47 ] During raid5 replacement, the stripes can be marked with R5_NeedReplace flag. Data can be read from being-replaced

[PATCH 4.18 066/158] timers: Clear timer_base::must_forward_clk with timer_base::lock held

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gaurav Kohli [ Upstream commit 363e934d8811d799c88faffc5bfca782fd728334 ] timer_base::must_forward_clock is indicating that the base clock might be stale due to a long idle sleep. The

[PATCH 4.18 057/158] net: phy: Fix the register offsets in Broadcom iProc mdio mux driver

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Arun Parameswaran [ Upstream commit 77fefa93bfebe4df44f154f2aa5938e32630d0bf ] Modify the register offsets in the Broadcom iProc mdio mux to start from the top of the register address space.

[PATCH 4.18 038/158] x86/microcode: Update the new microcode revision unconditionally

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filippo Sironi commit 8da38ebaad23fe1b0c4a205438676f6356607cfc upstream. Handle the case where microcode gets loaded on the BSP's hyperthread sibling first and the boot_cpu_data's microcode

[PATCH 4.18 069/158] misc: ti-st: Fix memory leak in the error path of probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 81ae962d7f180c0092859440c82996cccb254976 ] Free resources instead of direct return of the error code if kim_probe fails. Found by Linux Driver Verification

[PATCH 4.18 056/158] media: dw2102: Fix memleak on sequence of probes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 299c7007e93645067e1d2743f4e50156de78c4ff ] Each call to dw2102_probe() allocates memory by kmemdup for structures p1100, s660, p7500 and s421, but there is no

[PATCH 4.18 067/158] media: camss: csid: Configure data type and decode format properly

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Todor Tomov [ Upstream commit c628e78899ff8006b5f9d8206da54ed3bb994342 ] The CSID decodes the input data stream. When the input comes from the Test Generator the format of the stream is set

[PATCH 4.18 057/158] net: phy: Fix the register offsets in Broadcom iProc mdio mux driver

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Arun Parameswaran [ Upstream commit 77fefa93bfebe4df44f154f2aa5938e32630d0bf ] Modify the register offsets in the Broadcom iProc mdio mux to start from the top of the register address space.

[PATCH 4.18 038/158] x86/microcode: Update the new microcode revision unconditionally

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filippo Sironi commit 8da38ebaad23fe1b0c4a205438676f6356607cfc upstream. Handle the case where microcode gets loaded on the BSP's hyperthread sibling first and the boot_cpu_data's microcode

[PATCH 4.18 069/158] misc: ti-st: Fix memory leak in the error path of probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 81ae962d7f180c0092859440c82996cccb254976 ] Free resources instead of direct return of the error code if kim_probe fails. Found by Linux Driver Verification

[PATCH 4.18 056/158] media: dw2102: Fix memleak on sequence of probes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 299c7007e93645067e1d2743f4e50156de78c4ff ] Each call to dw2102_probe() allocates memory by kmemdup for structures p1100, s660, p7500 and s421, but there is no

[PATCH 4.18 067/158] media: camss: csid: Configure data type and decode format properly

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Todor Tomov [ Upstream commit c628e78899ff8006b5f9d8206da54ed3bb994342 ] The CSID decodes the input data stream. When the input comes from the Test Generator the format of the stream is set

[PATCH 4.18 020/158] Btrfs: fix data corruption when deduplicating between different files

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit de02b9f6bb65a6a1848f346f7a3617b7a9b930c0 upstream. If we deduplicate extents between two different files we can end up corrupting data if the source range ends at the

[PATCH 4.18 063/158] scsi: lpfc: Fix driver crash when re-registering NVME rports.

4.18-stable review patch. If anyone has any objections, please let me know. -- From: James Smart [ Upstream commit 93a3922da428ec0752e8b2ab00c42dadbbf805a9 ] During remote port loss fault testing, the driver crashed with the following trace: general protection fault:

[PATCH 4.18 061/158] clk: scmi: Fix the rounding of clock rate

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Amit Daniel Kachhap [ Upstream commit 7a8655e19bdb3be43f6a3b4768c9b0928a2585fc ] This fix rounds the clock rate properly by using quotient and not remainder in the calculation. This issue was

[PATCH 4.18 059/158] scsi: qla2xxx: Fix session state stuck in Get Port DB

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran [ Upstream commit 8fde6977ac478c00eeb2beccfdd4a6ad44219f6c ] This patch sets discovery state back to GNL (Get Name List) when session is stuck at GPDB (Get Port DataBase). This

[PATCH 4.18 060/158] scsi: qla2xxx: Silent erroneous message

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran [ Upstream commit 3f915271b12e11183c606bed1c3dfff0983662d3 ] Driver uses shadow pointer instead of Mirror pointer for firmware dump collection. Skip those entries for Mirror

[PATCH 4.18 062/158] blk-mq: fix updating tags depth

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei [ Upstream commit 75d6e175fc511e95ae3eb8f708680133bc211ed3 ] The passed 'nr' from userspace represents the total depth, meantime inside 'struct blk_mq_tags', 'nr_tags' stores the

[PATCH 4.18 002/158] i2c: i801: fix DNVs SMBCTRL register offset

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe Balbi commit 851a15114895c5bce163a6f2d57e0aa4658a1be4 upstream. DNV's iTCO is slightly different with SMBCTRL sitting at a different offset when compared to all other devices. Let's

[PATCH 4.18 021/158] arm64: KVM: Only force FPEXC32_EL2.EN if trapping FPSIMD

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 7d14919c0d475a795c0127631ac8ecb2b0f31831 upstream. If trapping FPSIMD in the context of an AArch32 guest, it is critical to set FPEXC32_EL2.EN to 1 so that the trapping is

[PATCH 4.18 058/158] scsi: qla2xxx: Fix unintended Logout

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran [ Upstream commit cb97f2c2e8d9f8c71ddbf04ad57e163ee6d86474 ] During normal IO, FW can return IO with 'port unavailble' status. Driver would send a LOGO to remote port for session

[PATCH 4.18 020/158] Btrfs: fix data corruption when deduplicating between different files

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit de02b9f6bb65a6a1848f346f7a3617b7a9b930c0 upstream. If we deduplicate extents between two different files we can end up corrupting data if the source range ends at the

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