make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.S', needed by 'arch/sh/boot/dts/.dtb.o'.

Hi Rob, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: e255aee5b66ce4af025e6f77122114c01303b861 commit: 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 kbuild: consolidate Devicetree dtb build rules date: 6 weeks ago co

Re: [PATCH v3 1/2] dt-bindings: phy: Document cadence Sierra PHY bindings

On Mon, Nov 12, 2018 at 04:42:01PM +, Alan Douglas wrote: > Add DT binding documentation for Sierra PHY. The PHY supports > a number of different protocols, including PCIe and USB. > > The PHY lanes may be configured as single or multi-lane links. > Each link is treated as a separate sub-node

Re: [RFC PATCH 06/13] m68k: Drop ARCH_USES_GETTIMEOFFSET

On Tue, 13 Nov 2018, Michael Schmitz wrote: > Hi Finn, > > Am 12.11.2018 um 22:06 schrieb Finn Thain: > > On Mon, 12 Nov 2018, Geert Uytterhoeven wrote: > > > > > Hi Finn, > > > > > > Thanks for your patch! > > > > > > On Mon, Nov 12, 2018 at 5:46 AM Finn Thain > > > wrote: > > > > The functi

Re: [PATCH v3] driver-staging: vsoc.c: Add sysfs support for examining the permissions of regions.

> On 12 Nov 2018, at 8:40 PM, Greg Kroah-Hartman wrote: > > On Mon, Nov 12, 2018 at 04:49:30PM +0800, wahahab wrote: >> >>> On 10 Nov 2018, at 1:15 AM, Dan Carpenter >> > wrote: >>> >>> On Wed, Nov 07, 2018 at 10:30:43AM +0800, Jerry Lin wrote: Add a attr

Re: [RFC PATCH 01/13] arm: Fix mutual exclusion in arch_gettimeoffset

On Mon, 12 Nov 2018, Christoph Hellwig wrote: > On Mon, Nov 12, 2018 at 03:12:39PM +1100, Finn Thain wrote: > > Implementations of arch_gettimeoffset are generally not re-entrant and > > assume that interrupts have been disabled. Unfortunately this > > pre-condition got broken in v2.6.32. > > >

Re: [RFC PATCH] ptrace: add PTRACE_GET_SYSCALL_INFO request

On Wed, Nov 07, 2018 at 12:44:58PM -0800, Andy Lutomirski wrote: > > On Nov 6, 2018, at 7:27 PM, Elvira Khabirova > > wrote: > > > > PTRACE_GET_SYSCALL_INFO lets ptracer obtain details of the syscall > > the tracee is blocked in. The request returns meaningful data only > > when the tracee is in

Proposal

Hello , My name is Sgt Major John Dailey. I am here in Afghanistan , I came upon a project I think we can work together on. I and my partner (1st Lt. Daniel Farkas ) have the sum of $15 Million United State Dollars which we got from a Crude Oil Deal in Iraq before he was killed by an explosion wh

Re: [PATCH 1/2] dt-bindings: phy: Add Qualcomm Synopsys High-Speed USB PHY binding

Hi Rob, On Mon, Nov 12, 2018 at 01:24:51PM -0600, Rob Herring wrote: > On Thu, Nov 08, 2018 at 03:04:48PM +0800, Shawn Guo wrote: > > From: Sriharsha Allenki > > > > It adds bindings for Synopsys 28nm femto phy controller that supports > > LS/FS/HS usb connectivity on Qualcomm chipsets. > > > >

[PATCH v6 3/4] dt-bindings: pps: pps-gpio PPS ECHO implementation

This patch implements the device tree changes required for the pps echo functionality for pps-gpio, that sysfs claims is available already. This patch was originally written by Lukas Senger as part of a masters thesis project and modified for inclusion into the linux kernel by Tom Burkart. Signed

[PATCH v6 4/4] pps: pps-gpio pps-echo implementation

This patch implements the pps echo functionality for pps-gpio, that sysfs claims is available already. Configuration is done via device tree bindings. This patch was originally written by Lukas Senger as part of a masters thesis project and modified for inclusion into the linux kernel by Tom Burk

[PATCH v6 1/4] dt-bindings: pps: descriptor-based gpio, capture-clear addition

This patch changes the devicetree bindings for the pps-gpio driver from the integer based API to the descriptor based API. It also adds documentation for the device tree capture-clear option. The change from integer based GPIO API to the descriptor based API breaks backward compatibility for the

[PATCH v6 2/4] pps: descriptor-based gpio, capture-clear addition

This patch changes the GPIO access for the pps-gpio driver from the integer based API to the descriptor based API. It also adds documentation for the device tree capture-clear option and device tree capture-clear extraction. The change from integer based GPIO API to the descriptor based API break

[PATCH v6 0/4] PPS: pps-gpio PPS ECHO implementation

Hi all, please find attached the PPS-GPIO PPS ECHO implementation patch. The driver claims to have echo functionality in the sysfs interface but this functionality is not present. This patch provides this functionality. Parts 1 and 2 of the patch change the original driver from the number based G

Re: [PATCH 0/2] opp: ti-opp-supply: Fixes

On 07-11-18, 10:04, Keerthy wrote: > The series brings in couple of fixes to the ti-opp-supply driver. > One of them updates u_volt_min dynamically and avoids hang due > to lesser static u_volt_min and the other fixes the supply in > _get_optimal_vdd_voltage. Applied both patches after manually ad

[PATCH 3/3] arm64: dts: Add USB DT nodes for Stingray SoC

Add DT nodes for - Two xHCI host controllers - Two BDC Broadcom USB device controller - Five USB PHY controllers [xHCI0] [BDC0][xHCI1][BDC1] | | | | --- --- |

[PATCH 2/3] phy: sr-usb: Add stingray usb phy driver

This driver supports all versions of stingray SS and HS USB phys. In version 1 is combo phy contain both SS and HS phys in a common IO space. In version 2 a single HS phy. These phys support both xHCI host driver and BDC Broadcom device controller driver. Signed-off-by: Srinath Mannam Reviewed-by

[PATCH 1/3] dt-bindings: phy: Add binding document for stingray usb phy

Add DT binding document for stingray usb phy. Signed-off-by: Srinath Mannam Reviewed-by: Florian Fainelli Reviewed-by: Scott Branden --- .../bindings/phy/brcm,stingray-usb-phy.txt | 62 ++ 1 file changed, 62 insertions(+) create mode 100644 Documentation/devicetre

[PATCH 0/3] Stingray usb phy driver support

These patches add stingray usb phy driver and its corresponding DT nodes with documentation. All patches are based on Linux-4.19. Srinath Mannam (3): dt-bindings: phy: Add binding document for stingray usb phy phy: sr-usb: Add stingray usb phy driver arm64: dts: Add USB DT nodes for Stingra

Hello

I Have decided with the support of my family to voluntarily donate part of our foundation funds to you as a charitable project to improve the lives of five different individuals randomly selected all over the world. If you have received this message, then you are among the lucky recipients to b

[PATCH] vmscan: return NODE_RECLAIM_NOSCAN in node_reclaim() when CONFIG_NUMA is n

Commit fa5e084e43eb ("vmscan: do not unconditionally treat zones that fail zone_reclaim() as full") changed the return value of node_reclaim(). The original return value 0 means NODE_RECLAIM_SOME after this commit. While the return value of node_reclaim() when CONFIG_NUMA is n is not changed. This

Re: [PATCH] xfs: Remove noinline from #define STATIC

On Tue, 2018-11-13 at 14:09 +1100, Dave Chinner wrote: > On Mon, Nov 12, 2018 at 08:54:10PM -0500, Theodore Y. Ts'o wrote: > > On Tue, Nov 13, 2018 at 12:18:05PM +1100, Dave Chinner wrote: > > > I'm not interested in making code fast if distro support engineers > > > can't debug problems on user sy

Re: ODEBUG: Out of memory. ODEBUG disabled

> On Nov 10, 2018, at 9:11 AM, Qian Cai wrote: > > On 11/10/18 at 8:59 AM, Waiman Long wrote: > >> On 11/09/2018 08:45 PM, Qian Cai wrote: Sent: Friday, November 09, 2018 at 5:08 PM From: "Waiman Long" To: "Qian Cai" , "Yang Shi" Cc: "open list" , "Thomas Gleixner"

[PATCH] x86/tsc: Fix -Wmissing-prototypes warning for calibrate_delay_is_known()

We get a warning when building kernel with W=1: arch/x86/kernel/tsc.c:1497:15: warning: no previous prototype for ‘calibrate_delay_is_known’ [-Wmissing-prototypes] unsigned long calibrate_delay_is_known(void) ^ Add the missing declaration in head file to fix this. Signed-off-by:

linux-next: Tree for Nov 13

Hi all, Changes since 20181112: The kbuild tree gained a conflict against the kbuild-current tree. The tip tree still had its build failure for which I applied a fix patch. Non-merge commits (relative to Linus' tree): 2535 2699 files changed, 105795 insertions(+), 93590 dele

Kernel panic - not syncing: corrupted stack end detected inside scheduler

Running LTP oom01 [1] test triggered kernel panic on an aarch64 server with the latest mainline (rc2). [1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/oom/oom01.c [ 3433.338741] Kernel panic - not syncing: corrupted stack end detected inside scheduler [ 3433.3476

Re: [RFC PATCH 06/13] m68k: Drop ARCH_USES_GETTIMEOFFSET

Hi Finn, Am 13.11.2018 um 16:14 schrieb Finn Thain: On Tue, 13 Nov 2018, Michael Schmitz wrote: Hi Finn, Am 12.11.2018 um 22:06 schrieb Finn Thain: On Mon, 12 Nov 2018, Geert Uytterhoeven wrote: Hi Finn, Thanks for your patch! On Mon, Nov 12, 2018 at 5:46 AM Finn Thain wrote: The funct

Re: [PATCH v9 02/10] Makefile: Prepare for using macros for inline asm

On 10/11/18 03:04 PM, Nadav Amit wrote: > Err.. I hate makefiles and distcc doesn’t make life easier. For instance, if > it sees two source files on the command-line, it freaks out and compiles it > locally. It also has an option to distribute assembly, but it is not enabled > by default. > > A

Re: [PATCH 1/2] dt-bindings: phy: Add Qualcomm Synopsys High-Speed USB PHY binding

Hi Sriharsha, On Tue, Nov 13, 2018 at 11:42 AM Shawn Guo wrote: > > > +- qcom,init-seq: > > > +Value type: > > > +Definition: Should contain a sequence of tuples > > > to > > > +program 'value' into phy register at 'offset' with > > > 'delay' > > > + in us a

[PATCH] x86/process: Fix some -Wmissing-prototypes warnings

We get a warning when building kernel with W=1: arch/x86/kernel/process.c:653:13: warning: no previous prototype for ‘arch_post_acpi_subsys_init’ [-Wmissing-prototypes] arch/x86/kernel/process.c:717:15: warning: no previous prototype for ‘arch_randomize_brk’ [-Wmissing-prototypes] arch/x86/kernel

Linux Foundation Technical Advisory Board Elections

Hello everyone, The Linux Foundation Technical Advisory Board (TAB) serves as the interface between the kernel development community and the Linux Foundation. The TAB advises the Foundation on kernel-related matters, helps member companies learn to work with the community, and works to resolve

Re: [PATCH 2/2] exec: increase BINPRM_BUF_SIZE to 256

On Mon, Nov 12, 2018 at 5:52 PM, Andrew Morton wrote: > On Mon, 12 Nov 2018 17:09:56 +0100 Oleg Nesterov wrote: > >> Large enterprise clients often times run applications out of networked >> file systems where the IT mandated layout of project volumes can end up >> leading to paths that are longe

Re: [PATCH 4.19 000/361] 4.19.2-stable review

On Mon, Nov 12, 2018 at 04:58:28PM -0800, Guenter Roeck wrote: > On Sun, Nov 11, 2018 at 02:15:47PM -0800, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.2 release. > > There are 361 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.9 000/141] 4.9.137-stable review

On Mon, 12 Nov 2018 at 19:03, Greg Kroah-Hartman wrote: > > On Mon, Nov 12, 2018 at 08:38:44AM -0200, Rafael David Tinoco wrote: > > On 11/11/18 8:24 PM, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.9.137 release. > > > There are 141 patches in this series

[PATCH] mtd: change len type from signed to unsigned type

From: "huijin.park" This patch casts the "len" parameter to an unsigned int. The callers of erase_write() pass the "len" parameter as unsigned int. Signed-off-by: huijin.park --- drivers/mtd/mtdblock.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/mtdblock.

Re: [PATCH v2 1/2] Makefile: Export clang toolchain variables

On Tue, Nov 13, 2018 at 3:56 AM Nick Desaulniers wrote: > > On Sun, Nov 11, 2018 at 8:21 PM Joel Stanley wrote: > > > > The powerpc makefile will use these in it's boot wrapper. > > > > Signed-off-by: Joel Stanley > > --- > > Makefile | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git

[PATCH] mtd: spi-nor: cast to u64 to avoid uint overflows

From: "huijin.park" The "params->size" is defined as "u64". And "info->sector_size" and "info->n_sectors" are defined as unsigned int and u16. Thus, u64 data might have strange data(loss data) if the result overflows an unsigned int. This patch casts "info->sector_size" and "info->n_sectors" to a

Re: [PATCH] xfs: Remove noinline from #define STATIC

On Mon, Nov 12, 2018 at 08:23:42PM -0800, Joe Perches wrote: > On Tue, 2018-11-13 at 14:09 +1100, Dave Chinner wrote: > > On Mon, Nov 12, 2018 at 08:54:10PM -0500, Theodore Y. Ts'o wrote: > > > On Tue, Nov 13, 2018 at 12:18:05PM +1100, Dave Chinner wrote: > > > > I'm not interested in making code f

Re: [PATCH] xfs: Remove noinline from #define STATIC

On Tue, 2018-11-13 at 16:26 +1100, Dave Chinner wrote: > On Mon, Nov 12, 2018 at 08:23:42PM -0800, Joe Perches wrote: > > On Tue, 2018-11-13 at 14:09 +1100, Dave Chinner wrote: > > > On Mon, Nov 12, 2018 at 08:54:10PM -0500, Theodore Y. Ts'o wrote: > > > > On Tue, Nov 13, 2018 at 12:18:05PM +1100,

Re: [PATCH] vmscan: return NODE_RECLAIM_NOSCAN in node_reclaim() when CONFIG_NUMA is n

On Tue, Nov 13, 2018 at 12:17:50PM +0800, Wei Yang wrote: > Commit fa5e084e43eb ("vmscan: do not unconditionally treat zones that > fail zone_reclaim() as full") changed the return value of node_reclaim(). > The original return value 0 means NODE_RECLAIM_SOME after this commit. > > While the retur

Re: [PATCH] xfs: Remove noinline from #define STATIC

On Mon, Nov 12, 2018 at 09:31:51PM -0800, Joe Perches wrote: > On Tue, 2018-11-13 at 16:26 +1100, Dave Chinner wrote: > > On Mon, Nov 12, 2018 at 08:23:42PM -0800, Joe Perches wrote: > > > On Tue, 2018-11-13 at 14:09 +1100, Dave Chinner wrote: > > > > On Mon, Nov 12, 2018 at 08:54:10PM -0500, Theod

[PATCH AUTOSEL 4.19 02/44] cifs: don't dereference smb_file_target before null check

From: Colin Ian King [ Upstream commit 8c6c9bed8773375b1d54ccca2911ec892c59db5d ] There is a null check on dst_file->private data which suggests it can be potentially null. However, before this check, pointer smb_file_target is derived from dst_file->private and dereferenced in the call to tlink

[PATCH AUTOSEL 4.19 25/44] perf symbols: Set PLT entry/header sizes properly on Sparc

From: David Miller [ Upstream commit d6afa561e1471ccfdaf7191230c0c59a37e45a5b ] Using the sh_entsize for both values isn't correct. It happens to be correct on x86... For both 32-bit and 64-bit sparc, there are four PLT entries in the PLT section. Signed-off-by: David S. Miller Cc: Alexander

[PATCH AUTOSEL 4.19 16/44] hfs: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit d057c036672f33d43a5f7344acbb08cf3a8a0c09 ] This bug is triggered whenever hfs_brec_update_parent() needs to split the root node. The height of the btree is not increased, which leaves the new node orphaned and its records lost. It is not possible fo

[PATCH AUTOSEL 4.19 17/44] hfsplus: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit 0a3021d4f5295aa073c7bf5c5e4de60a2e292578 ] Creating, renaming or deleting a file may cause catalog corruption and data loss. This bug is randomly triggered by xfstests generic/027, but here is a faster reproducer: truncate -s 50M fs.iso mkfs.hfs

[PATCH AUTOSEL 4.19 18/44] mm/gup_benchmark.c: prevent integer overflow in ioctl

From: Dan Carpenter [ Upstream commit 4b408c74ee5a0b74fc9265c2fe39b0e7dec7c056 ] The concern here is that "gup->size" is a u64 and "nr_pages" is unsigned long. On 32 bit systems we could trick the kernel into allocating fewer pages than expected. Link: http://lkml.kernel.org/r/20181025061546.h

[PATCH AUTOSEL 4.19 09/44] net: hns3: bugfix for rtnl_lock's range in the hclge_reset()

From: Huazhong Tan [ Upstream commit a963052e539887df481d4d3a6ad4c92ca6461852 ] Since hclge_reset_wait() is used to wait for the hardware to complete the reset, it is not necessary to hold the rtnl_lock during hclge_reset_wait(). So this patch releases the lock for the duration of hclge_reset_wa

[PATCH AUTOSEL 4.19 15/44] reiserfs: propagate errors from fill_with_dentries() properly

From: Jann Horn [ Upstream commit b10298d56c9623f9b173f19959732d3184b35f4f ] fill_with_dentries() failed to propagate errors up to reiserfs_for_each_xattr() properly. Plumb them through. Note that reiserfs_for_each_xattr() is only used by reiserfs_delete_xattrs() and reiserfs_chown_xattrs().

[PATCH AUTOSEL 4.19 10/44] net: hns3: bugfix for handling mailbox while the command queue reinitialized

From: Huazhong Tan [ Upstream commit 3c88ed1d798da355859ca083d3884a16ce0841f2 ] In a multi-core machine, the mailbox service and reset service will be executed at the same time. The reset service will re-initialize the command queue, before that, the mailbox handler can only get some invalid mes

[PATCH AUTOSEL 4.19 13/44] mm: Fix warning in insert_pfn()

From: Jan Kara [ Upstream commit f2c57d91b0d96aa13ccff4e3b178038f17b00658 ] In DAX mode a write pagefault can race with write(2) in the following way: CPU0CPU1 write fault for mapped zero page (hole) dax_iomap_rw() iomap_apply()

[PATCH AUTOSEL 4.19 08/44] net: hns3: bugfix for rtnl_lock's range in the hclgevf_reset()

From: Huazhong Tan [ Upstream commit 29118ab962d5476fdc65fae312ac38db68092d78 ] Since hclgevf_reset_wait() is used to wait for the hardware to complete the reset, it is not necessary to hold the rtnl_lock during hclgevf_reset_wait(). So this patch releases the lock for the duration of hclgevf_re

[PATCH AUTOSEL 4.19 37/44] mm: thp: fix MADV_DONTNEED vs migrate_misplaced_transhuge_page race condition

From: Andrea Arcangeli [ Upstream commit d7c3393413fe7e7dc54498ea200ea94742d61e18 ] Patch series "migrate_misplaced_transhuge_page race conditions". Aaron found a new instance of the THP MADV_DONTNEED race against pmdp_clear_flush* variants, that was apparently left unfixed. While looking into

[PATCH AUTOSEL 4.19 41/44] mm/vmstat.c: assert that vmstat_text is in sync with stat_items_size

From: Jann Horn [ Upstream commit f0ecf25a093fc0589f0a6bc4c1ea068bbb67d220 ] Having two gigantic arrays that must manually be kept in sync, including ifdefs, isn't exactly robust. To make it easier to catch such issues in the future, add a BUILD_BUG_ON(). Link: http://lkml.kernel.org/r/2018100

[PATCH AUTOSEL 4.18 06/39] block: brd: associate with queue until adding disk

From: Ming Lei [ Upstream commit 153fcd5f6d93b8e1e4040b1337f564a10f8d93af ] brd_free() may be called in failure path on one brd instance which disk isn't added yet, so release handler of gendisk may free the associated request_queue early and causes the following use-after-free[1]. This patch f

[PATCH AUTOSEL 4.19 42/44] userfaultfd: allow get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) to trigger userfaults

From: Andrea Arcangeli [ Upstream commit 3b9aadf7278d16d7bed4d5d808501065f70898d8 ] get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) called a get_user_pages that would not be waiting for userfaults before failing and it would hit on a SIGBUS instead. Using get_user_pages_locked/unlocked instead will allo

[PATCH AUTOSEL 4.18 07/39] net: hns3: bugfix for rtnl_lock's range in the hclgevf_reset()

From: Huazhong Tan [ Upstream commit 29118ab962d5476fdc65fae312ac38db68092d78 ] Since hclgevf_reset_wait() is used to wait for the hardware to complete the reset, it is not necessary to hold the rtnl_lock during hclgevf_reset_wait(). So this patch releases the lock for the duration of hclgevf_re

[PATCH AUTOSEL 4.19 39/44] mm: calculate deferred pages after skipping mirrored memory

From: Pavel Tatashin [ Upstream commit d3035be4ce2345d98633a45f93a74e526e94b802 ] update_defer_init() should be called only when struct page is about to be initialized. Because it counts number of initialized struct pages, but there we may skip struct pages if there is some mirrored memory. So

[PATCH AUTOSEL 4.19 38/44] mm: thp: fix mmu_notifier in migrate_misplaced_transhuge_page()

From: Andrea Arcangeli [ Upstream commit 7066f0f933a1fd707bb38781866657769cff7efc ] change_huge_pmd() after arming the numa/protnone pmd doesn't flush the TLB right away. do_huge_pmd_numa_page() flushes the TLB before calling migrate_misplaced_transhuge_page(). By the time do_huge_pmd_numa_pag

[PATCH AUTOSEL 4.18 03/39] cifs: fix return value for cifs_listxattr

From: Ronnie Sahlberg [ Upstream commit 0c5d6cb6643f48ad3775322f3ebab6c7eb67484e ] If the application buffer was too small to fit all the names we would still count the number of bytes and return this for listxattr. This would then trigger a BUG in usercopy.c Fix the computation of the size so

[PATCH AUTOSEL 4.18 11/39] mm: Fix warning in insert_pfn()

From: Jan Kara [ Upstream commit f2c57d91b0d96aa13ccff4e3b178038f17b00658 ] In DAX mode a write pagefault can race with write(2) in the following way: CPU0CPU1 write fault for mapped zero page (hole) dax_iomap_rw() iomap_apply()

[PATCH AUTOSEL 4.18 14/39] hfs: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit d057c036672f33d43a5f7344acbb08cf3a8a0c09 ] This bug is triggered whenever hfs_brec_update_parent() needs to split the root node. The height of the btree is not increased, which leaves the new node orphaned and its records lost. It is not possible fo

[PATCH AUTOSEL 4.18 23/39] perf symbols: Set PLT entry/header sizes properly on Sparc

From: David Miller [ Upstream commit d6afa561e1471ccfdaf7191230c0c59a37e45a5b ] Using the sh_entsize for both values isn't correct. It happens to be correct on x86... For both 32-bit and 64-bit sparc, there are four PLT entries in the PLT section. Signed-off-by: David S. Miller Cc: Alexander

[PATCH AUTOSEL 4.18 15/39] hfsplus: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit 0a3021d4f5295aa073c7bf5c5e4de60a2e292578 ] Creating, renaming or deleting a file may cause catalog corruption and data loss. This bug is randomly triggered by xfstests generic/027, but here is a faster reproducer: truncate -s 50M fs.iso mkfs.hfs

[PATCH AUTOSEL 4.18 12/39] mm/memory_hotplug: make add_memory() take the device_hotplug_lock

From: David Hildenbrand [ Upstream commit 8df1d0e4a265f25dc1e7e7624ccdbcb4a6630c89 ] add_memory() currently does not take the device_hotplug_lock, however is aleady called under the lock from arch/powerpc/platforms/pseries/hotplug-memory.c drivers/acpi/acpi_memhotplug.c to synchr

[PATCH AUTOSEL 4.18 16/39] mm/gup_benchmark.c: prevent integer overflow in ioctl

From: Dan Carpenter [ Upstream commit 4b408c74ee5a0b74fc9265c2fe39b0e7dec7c056 ] The concern here is that "gup->size" is a u64 and "nr_pages" is unsigned long. On 32 bit systems we could trick the kernel into allocating fewer pages than expected. Link: http://lkml.kernel.org/r/20181025061546.h

[PATCH AUTOSEL 4.18 13/39] reiserfs: propagate errors from fill_with_dentries() properly

From: Jann Horn [ Upstream commit b10298d56c9623f9b173f19959732d3184b35f4f ] fill_with_dentries() failed to propagate errors up to reiserfs_for_each_xattr() properly. Plumb them through. Note that reiserfs_for_each_xattr() is only used by reiserfs_delete_xattrs() and reiserfs_chown_xattrs().

[PATCH AUTOSEL 4.18 20/39] afs: Handle EIO from delivery function

From: David Howells [ Upstream commit 4ac15ea53622272c01954461b4814892b7481b40 ] Fix afs_deliver_to_call() to handle -EIO being returned by the operation delivery function, indicating that the call found itself in the wrong state, by printing an error and aborting the call. Currently, an assert

[PATCH AUTOSEL 4.18 35/39] mm: calculate deferred pages after skipping mirrored memory

From: Pavel Tatashin [ Upstream commit d3035be4ce2345d98633a45f93a74e526e94b802 ] update_defer_init() should be called only when struct page is about to be initialized. Because it counts number of initialized struct pages, but there we may skip struct pages if there is some mirrored memory. So

[PATCH AUTOSEL 4.9 03/17] mm/memory_hotplug: make add_memory() take the device_hotplug_lock

From: David Hildenbrand [ Upstream commit 8df1d0e4a265f25dc1e7e7624ccdbcb4a6630c89 ] add_memory() currently does not take the device_hotplug_lock, however is aleady called under the lock from arch/powerpc/platforms/pseries/hotplug-memory.c drivers/acpi/acpi_memhotplug.c to synchr

[PATCH AUTOSEL 4.14 20/26] x86/earlyprintk: Add a force option for pciserial device

From: Feng Tang [ Upstream commit d2266bbfa9e3e32e3b642965088ca461bd24a94f ] The "pciserial" earlyprintk variant helps much on many modern x86 platforms, but unfortunately there are still some platforms with PCI UART devices which have the wrong PCI class code. In that case, the current class co

[PATCH AUTOSEL 4.18 28/39] platform/x86: acerhdf: Add BIOS entry for Gateway LT31 v1.3307

From: Paul Gortmaker [ Upstream commit 684238d79ad85c5e19a71bb5818e77e329912fbc ] To fix: acerhdf: unknown (unsupported) BIOS version Gateway /LT31 /v1.3307 , please report, aborting! As can be seen in the context, the BIOS registers haven't changed in the previous versions, so the assum

[PATCH AUTOSEL 4.18 36/39] mm/vmstat.c: assert that vmstat_text is in sync with stat_items_size

From: Jann Horn [ Upstream commit f0ecf25a093fc0589f0a6bc4c1ea068bbb67d220 ] Having two gigantic arrays that must manually be kept in sync, including ifdefs, isn't exactly robust. To make it easier to catch such issues in the future, add a BUILD_BUG_ON(). Link: http://lkml.kernel.org/r/2018100

[PATCH AUTOSEL 4.14 24/26] userfaultfd: allow get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) to trigger userfaults

From: Andrea Arcangeli [ Upstream commit 3b9aadf7278d16d7bed4d5d808501065f70898d8 ] get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) called a get_user_pages that would not be waiting for userfaults before failing and it would hit on a SIGBUS instead. Using get_user_pages_locked/unlocked instead will allo

[PATCH AUTOSEL 4.14 10/26] hfs: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit d057c036672f33d43a5f7344acbb08cf3a8a0c09 ] This bug is triggered whenever hfs_brec_update_parent() needs to split the root node. The height of the btree is not increased, which leaves the new node orphaned and its records lost. It is not possible fo

[PATCH AUTOSEL 4.18 29/39] arm64: percpu: Initialize ret in the default case

From: Nathan Chancellor [ Upstream commit b5bb425871186303e6936fa2581521bdd1964a58 ] Clang warns that if the default case is taken, ret will be uninitialized. ./arch/arm64/include/asm/percpu.h:196:2: warning: variable 'ret' is used uninitialized whenever switch default is taken [-Wsometimes-uni

[PATCH AUTOSEL 4.18 34/39] mm: thp: fix mmu_notifier in migrate_misplaced_transhuge_page()

From: Andrea Arcangeli [ Upstream commit 7066f0f933a1fd707bb38781866657769cff7efc ] change_huge_pmd() after arming the numa/protnone pmd doesn't flush the TLB right away. do_huge_pmd_numa_page() flushes the TLB before calling migrate_misplaced_transhuge_page(). By the time do_huge_pmd_numa_pag

[PATCH AUTOSEL 4.9 14/17] arm64: percpu: Initialize ret in the default case

From: Nathan Chancellor [ Upstream commit b5bb425871186303e6936fa2581521bdd1964a58 ] Clang warns that if the default case is taken, ret will be uninitialized. ./arch/arm64/include/asm/percpu.h:196:2: warning: variable 'ret' is used uninitialized whenever switch default is taken [-Wsometimes-uni

[PATCH AUTOSEL 4.14 23/26] mm/vmstat.c: assert that vmstat_text is in sync with stat_items_size

From: Jann Horn [ Upstream commit f0ecf25a093fc0589f0a6bc4c1ea068bbb67d220 ] Having two gigantic arrays that must manually be kept in sync, including ifdefs, isn't exactly robust. To make it easier to catch such issues in the future, add a BUILD_BUG_ON(). Link: http://lkml.kernel.org/r/2018100

[PATCH AUTOSEL 4.18 37/39] userfaultfd: allow get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) to trigger userfaults

From: Andrea Arcangeli [ Upstream commit 3b9aadf7278d16d7bed4d5d808501065f70898d8 ] get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) called a get_user_pages that would not be waiting for userfaults before failing and it would hit on a SIGBUS instead. Using get_user_pages_locked/unlocked instead will allo

[PATCH AUTOSEL 4.18 33/39] mm: thp: fix MADV_DONTNEED vs migrate_misplaced_transhuge_page race condition

From: Andrea Arcangeli [ Upstream commit d7c3393413fe7e7dc54498ea200ea94742d61e18 ] Patch series "migrate_misplaced_transhuge_page race conditions". Aaron found a new instance of the THP MADV_DONTNEED race against pmdp_clear_flush* variants, that was apparently left unfixed. While looking into

[PATCH AUTOSEL 4.9 02/17] cifs: don't dereference smb_file_target before null check

From: Colin Ian King [ Upstream commit 8c6c9bed8773375b1d54ccca2911ec892c59db5d ] There is a null check on dst_file->private data which suggests it can be potentially null. However, before this check, pointer smb_file_target is derived from dst_file->private and dereferenced in the call to tlink

[PATCH AUTOSEL 4.14 07/26] mm: Fix warning in insert_pfn()

From: Jan Kara [ Upstream commit f2c57d91b0d96aa13ccff4e3b178038f17b00658 ] In DAX mode a write pagefault can race with write(2) in the following way: CPU0CPU1 write fault for mapped zero page (hole) dax_iomap_rw() iomap_apply()

[PATCH AUTOSEL 4.14 15/26] clk: fixed-rate: fix of_node_get-put imbalance

From: Alan Tull [ Upstream commit 52091c256bdcad0d01e2852a63f19cd2cce6af96 ] When the fixed rate clock is created by devicetree, of_clk_add_provider is called. Add a call to of_clk_del_provider in the remove function to balance it out. Signed-off-by: Alan Tull Fixes: 435779fe1336 ("clk: fixed

[PATCH AUTOSEL 4.14 02/26] cifs: don't dereference smb_file_target before null check

From: Colin Ian King [ Upstream commit 8c6c9bed8773375b1d54ccca2911ec892c59db5d ] There is a null check on dst_file->private data which suggests it can be potentially null. However, before this check, pointer smb_file_target is derived from dst_file->private and dereferenced in the call to tlink

[PATCH AUTOSEL 4.14 08/26] mm/memory_hotplug: make add_memory() take the device_hotplug_lock

From: David Hildenbrand [ Upstream commit 8df1d0e4a265f25dc1e7e7624ccdbcb4a6630c89 ] add_memory() currently does not take the device_hotplug_lock, however is aleady called under the lock from arch/powerpc/platforms/pseries/hotplug-memory.c drivers/acpi/acpi_memhotplug.c to synchr

[PATCH AUTOSEL 4.14 04/26] arm64: kprobe: make page to RO mode when allocate it

From: Anders Roxell [ Upstream commit 966866892cf89d606544bca22d584ba2ef9ec208 ] Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable pages") has successfully identified code that leaves a page with W+X permissions. [3.245140] arm64/mm: Found insecure W+X mapping at

[PATCH AUTOSEL 4.14 17/26] fs/exofs: fix potential memory leak in mount option parsing

From: Chengguang Xu [ Upstream commit 515f1867addaba49c1c6ac73abfaffbc192c1db4 ] There are some cases can cause memory leak when parsing option 'osdname'. Signed-off-by: Chengguang Xu Signed-off-by: Al Viro Signed-off-by: Sasha Levin --- fs/exofs/super.c | 5 - 1 file changed, 4 inserti

[PATCH AUTOSEL 3.18 5/9] um: Give start_idle_thread() a return code

From: Richard Weinberger [ Upstream commit 7ff1e34bbdc15acab823b1ee4240e94623d50ee8 ] Fixes: arch/um/os-Linux/skas/process.c:613:1: warning: control reaches end of non-void function [-Wreturn-type] longjmp() never returns but gcc still warns that the end of the function can be reached. Add a re

[PATCH AUTOSEL 3.18 3/9] hfs: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit d057c036672f33d43a5f7344acbb08cf3a8a0c09 ] This bug is triggered whenever hfs_brec_update_parent() needs to split the root node. The height of the btree is not increased, which leaves the new node orphaned and its records lost. It is not possible fo

[PATCH AUTOSEL 3.18 9/9] mm: don't warn about large allocations for slab

From: Dmitry Vyukov [ Upstream commit 61448479a9f2c954cde0cfe778cb6bec5d0a748d ] Slub does not call kmalloc_slab() for sizes > KMALLOC_MAX_CACHE_SIZE, instead it falls back to kmalloc_large(). For slab KMALLOC_MAX_CACHE_SIZE == KMALLOC_MAX_SIZE and it calls kmalloc_slab() for all allocations re

[PATCH AUTOSEL 3.18 8/9] mm/vmstat.c: assert that vmstat_text is in sync with stat_items_size

From: Jann Horn [ Upstream commit f0ecf25a093fc0589f0a6bc4c1ea068bbb67d220 ] Having two gigantic arrays that must manually be kept in sync, including ifdefs, isn't exactly robust. To make it easier to catch such issues in the future, add a BUILD_BUG_ON(). Link: http://lkml.kernel.org/r/2018100

[PATCH AUTOSEL 3.18 7/9] clk: samsung: exynos5420: Enable PERIS clocks for suspend

From: Marek Szyprowski [ Upstream commit b33228029d842269e17bba591609e83ed422005d ] Ensure that clocks for core SoC modules (including TZPC0..9 modules) are enabled for suspend/resume cycle. This fixes suspend/resume support on Exynos5422-based Odroid XU3/XU4 boards. Suggested-by: Joonyoung Shi

[PATCH AUTOSEL 3.18 4/9] hfsplus: prevent btree data loss on root split

From: Ernesto A. Fernández [ Upstream commit 0a3021d4f5295aa073c7bf5c5e4de60a2e292578 ] Creating, renaming or deleting a file may cause catalog corruption and data loss. This bug is randomly triggered by xfstests generic/027, but here is a faster reproducer: truncate -s 50M fs.iso mkfs.hfs

[PATCH AUTOSEL 4.9 16/17] userfaultfd: allow get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) to trigger userfaults

From: Andrea Arcangeli [ Upstream commit 3b9aadf7278d16d7bed4d5d808501065f70898d8 ] get_mempolicy(MPOL_F_NODE|MPOL_F_ADDR) called a get_user_pages that would not be waiting for userfaults before failing and it would hit on a SIGBUS instead. Using get_user_pages_locked/unlocked instead will allo

[PATCH AUTOSEL 3.18 2/9] reiserfs: propagate errors from fill_with_dentries() properly

From: Jann Horn [ Upstream commit b10298d56c9623f9b173f19959732d3184b35f4f ] fill_with_dentries() failed to propagate errors up to reiserfs_for_each_xattr() properly. Plumb them through. Note that reiserfs_for_each_xattr() is only used by reiserfs_delete_xattrs() and reiserfs_chown_xattrs().

[PATCH AUTOSEL 4.4 08/11] platform/x86: acerhdf: Add BIOS entry for Gateway LT31 v1.3307

From: Paul Gortmaker [ Upstream commit 684238d79ad85c5e19a71bb5818e77e329912fbc ] To fix: acerhdf: unknown (unsupported) BIOS version Gateway /LT31 /v1.3307 , please report, aborting! As can be seen in the context, the BIOS registers haven't changed in the previous versions, so the assum

[PATCH AUTOSEL 4.9 15/17] mm/vmstat.c: assert that vmstat_text is in sync with stat_items_size

From: Jann Horn [ Upstream commit f0ecf25a093fc0589f0a6bc4c1ea068bbb67d220 ] Having two gigantic arrays that must manually be kept in sync, including ifdefs, isn't exactly robust. To make it easier to catch such issues in the future, add a BUILD_BUG_ON(). Link: http://lkml.kernel.org/r/2018100

[PATCH AUTOSEL 3.18 6/9] fs/exofs: fix potential memory leak in mount option parsing

From: Chengguang Xu [ Upstream commit 515f1867addaba49c1c6ac73abfaffbc192c1db4 ] There are some cases can cause memory leak when parsing option 'osdname'. Signed-off-by: Chengguang Xu Signed-off-by: Al Viro Signed-off-by: Sasha Levin --- fs/exofs/super.c | 5 - 1 file changed, 4 inserti

[PATCH AUTOSEL 3.18 1/9] bfs: add sanity check at bfs_fill_super()

From: Tetsuo Handa [ Upstream commit 9f2df09a33aa2c76ce6385d382693f98d7f2f07e ] syzbot is reporting too large memory allocation at bfs_fill_super() [1]. Since file system image is corrupted such that bfs_sb->s_start == 0, bfs_fill_super() is trying to allocate 8MB of continuous memory. Fix this

[PATCH AUTOSEL 4.4 11/11] mm: don't warn about large allocations for slab

From: Dmitry Vyukov [ Upstream commit 61448479a9f2c954cde0cfe778cb6bec5d0a748d ] Slub does not call kmalloc_slab() for sizes > KMALLOC_MAX_CACHE_SIZE, instead it falls back to kmalloc_large(). For slab KMALLOC_MAX_CACHE_SIZE == KMALLOC_MAX_SIZE and it calls kmalloc_slab() for all allocations re

[PATCH AUTOSEL 4.4 09/11] arm64: percpu: Initialize ret in the default case

From: Nathan Chancellor [ Upstream commit b5bb425871186303e6936fa2581521bdd1964a58 ] Clang warns that if the default case is taken, ret will be uninitialized. ./arch/arm64/include/asm/percpu.h:196:2: warning: variable 'ret' is used uninitialized whenever switch default is taken [-Wsometimes-uni

<    1   2   3   4   5   6   7   8   >