Re: [PATCH v5] mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning

2019-03-29 Thread kbuild test robot
Hi Faiz, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on ulf.hansson-mmc/next] [also build test WARNING on v5.1-rc2 next-20190329] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH AUTOSEL 4.19 40/57] kvm: properly check debugfs dentry before using it

2019-03-29 Thread Greg Kroah-Hartman
On Fri, Mar 29, 2019 at 09:28:33PM -0400, Sasha Levin wrote: > From: Greg Kroah-Hartman > > [ Upstream commit 8ed0579c12b2fe56a1fac2f712f58fc26c1dc49b ] > > debugfs can now report an error code if something went wrong instead of > just NULL. So if the return value is to be used as a "real"

[PATCH] mm: Fix build warning

2019-03-29 Thread Aneesh Kumar K.V
mm/debug.c: In function ‘dump_mm’: include/linux/kern_levels.h:5:18: warning: format ‘%llx’ expects argument of type ‘long long unsigned int’, but argument 19 has type ‘long int’ [-Wformat=] ~~~^ Signed-off-by: Aneesh Kumar K.V --- mm/debug.c | 2 +- 1 file changed, 1

Re: [PATCH 2/4] pid: add pidfd_open()

2019-03-29 Thread Daniel Colascione
On Thu, Mar 28, 2019 at 3:38 AM Christian Brauner wrote: > > > All that said, thanks for the work on this once again. My intention is > > just that we don't end up with an API that could have been done better > > and be cleaner to use for potential users in the coming years. > > Thanks for your

Re: linux-next: Fixes tag needs some work in the tty.current tree

2019-03-29 Thread Stephen Rothwell
Hi Greg, On Fri, 29 Mar 2019 20:47:18 +0100 Greg KH wrote: > > Is there a script somewhere that I can use to run on my tree before I > push it out, much like I do now for the signed-off-by checks? Attached is what I use ... -- Cheers, Stephen Rothwell check_fixes Description:

linux-next: Fixes tag needs some work in the ext3 tree

2019-03-29 Thread Stephen Rothwell
Hi Jan, In commit 47d92aa5d33a ("quota: fix a problem about transfer quota") Fixes tag Fixes: 7b9ca4c61("quota: Reduce contention on dq_data_lock") has these problem(s): - missing space between the SHA1 and the subject - SHA1 should be at least 12 digits long Can be fixed by

Re: [PATCH] kbuild: fix warning "overriding recipe for target 'Makefile'"

2019-03-29 Thread Masahiro Yamada
On Tue, Mar 26, 2019 at 3:46 PM Masahiro Yamada wrote: > > If you do "make Makefile" with GNU Make 3.x, the following warning > is displayed: > > $ make Makefile > Makefile:165: warning: overriding recipe for target 'Makefile' > Makefile:51: warning: ignoring old recipe for target

Re: [PATCH] kbuild: move RETPOLINE flags below config-targets

2019-03-29 Thread Masahiro Yamada
On Tue, Mar 26, 2019 at 3:11 PM Masahiro Yamada wrote: > > When you run a "make *config" target, the retpoline compiler flags > are evaluated for nothing because the code is located above the > 'ifeq ($(config-targets),1)'. > > Move it a bit below to avoid unneeded computation in the Kconfig

Re: [PATCH] Remove SPDX "WITH Linux-syscall-note" from kernel-space headers

2019-03-29 Thread Masahiro Yamada
On Sat, Mar 30, 2019 at 1:54 PM Masahiro Yamada wrote: > > The "WITH Linux-syscall-note" should be added to headers exported to > the user-space. > > Some kernel-space headers have "WITH Linux-syscall-note", which seems > a mistake. > > [1] arch/x86/include/asm/hyperv-tlfs.h > > 5a4858032217

Re: [PATCH] iommu/amd: Reserve exclusion range in iova-domain

2019-03-29 Thread Stuart Hayes
Tested on a Dell PowerEdge R7425 system on which this problem is easily reproducible. Tested-by: Stuart Hayes

[PATCH] Remove SPDX "WITH Linux-syscall-note" from kernel-space headers

2019-03-29 Thread Masahiro Yamada
The "WITH Linux-syscall-note" should be added to headers exported to the user-space. Some kernel-space headers have "WITH Linux-syscall-note", which seems a mistake. [1] arch/x86/include/asm/hyperv-tlfs.h 5a4858032217 ("x86/hyper-v: move hyperv.h out of uapi") moved this file out of uapi, but

Re: [PATCH] iommu/amd: Reserve exclusion range in iova-domain

2019-03-29 Thread Stuart Hayes
Tested on a Dell PowerEdge R7425 system on which this problem is easily reproducible. Tested-by: Stuart Hayes

Please i need your help

2019-03-29 Thread Mrs. Aisha
Dear Friend, I came across your e-mail contact prior a private search while in need of your assistance. My name is Aisha Gaddafi a single Mother and a Widow with three Children. I am the only biological Daughter of late Libyan President (Late Colonel Muammar Gaddafi). I have an investment

Re: [RFC][PATCH 0/4 v2] sycalls: Remove args i and n from syscall_get_arguments()

2019-03-29 Thread Palmer Dabbelt
On Fri, 29 Mar 2019 10:40:45 PDT (-0700), rost...@goodmis.org wrote: On Fri, 29 Mar 2019 10:24:58 -0700 Linus Torvalds wrote: The whole series looks fine to me. Great! I may just send a pull request to you, after some fixes (see below). I still suspect that we should just remove the

Re: [PATCH] rcu: tree_stall: Correctly unlock root node in rcu_check_gp_start_stall

2019-03-29 Thread Neeraj Upadhyay
On 3/30/19 2:57 AM, Paul E. McKenney wrote: On Fri, Mar 29, 2019 at 07:52:15PM +0530, Neeraj Upadhyay wrote: On 3/29/19 6:58 PM, Mukesh Ojha wrote: On 3/29/2019 4:57 PM, Neeraj Upadhyay wrote: Only unlock the root node, if current node (rnp) is not root node. Signed-off-by: Neeraj

Re: [PATCH 5/6] acpi/cppc: Add support for optional CPPC registers

2019-03-29 Thread Pandruvada, Srinivas
On Fri, 2019-03-29 at 20:18 +, Ghannam, Yazen wrote: > > -Original Message- > > From: linux-acpi-ow...@vger.kernel.org < > > linux-acpi-ow...@vger.kernel.org> On Behalf Of Pandruvada, Srinivas > > Sent: Wednesday, March 27, 2019 10:48 AM > > To: linux-kernel@vger.kernel.org;

Compliment of the day to you Dear Friend.

2019-03-29 Thread mcompola
Compliment of the day to you Dear Friend. Dear Friend. I am Mrs.M Compola. am sending this brief letter to solicit your partnership to transfer $5 million US Dollars. I shall send you more information and procedures when I receive positive response from you. Mrs M Compola

Re: [PATCH] Convert struct pid count to refcount_t

2019-03-29 Thread Joel Fernandes
On Thu, Mar 28, 2019 at 10:37:07AM -0700, Paul E. McKenney wrote: > On Thu, Mar 28, 2019 at 05:26:42PM +0100, Oleg Nesterov wrote: > > On 03/28, Jann Horn wrote: > > > > > > Since we're just talking about RCU stuff now, adding Paul McKenney to > > > the thread. > > > > Since you added Paul let me

[PATCH v2 2/2] clk:mmp: clk-mix.c fix divide-by-zero

2019-03-29 Thread nixiaoming
The _get_div() function has a branch with a return value of 0 Add a check on the return value of _get_div() to avoid divide-by-zero Signed-off-by: nixiaoming Reviewed-by: Mukesh Ojha --- drivers/clk/mmp/clk-mix.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 1/2] clk:Fix divide-by-zero in divider_ro_round_rate_parent

2019-03-29 Thread nixiaoming
In the function divider_recalc_rate() The judgment of the return value of _get_div() indicates that the return value of _get_div() may be 0. In order to avoid the divide-by-zero error, add check the return value of _get_div() in the divider_ro_round_rate_parent() Signed-off-by: nixiaoming ---

RE: [PATCH] clk:mmp: clk-mix.c fix divide-by-zero

2019-03-29 Thread Nixiaoming
On 3/30/2019 6:48 AM Stephen Boyd wrote: >Quoting nixiaoming (2019-03-29 04:46:00) >> The _get_div function has a branch with a return value of 0 >> Add a check on the return value of _get_div to avoid divide-by-zero >> >> Signed-off-by: nixiaoming > >Similar questions apply here as they do on

Re: [PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

2019-03-29 Thread Christian Brauner
On Sat, Mar 30, 2019 at 03:12:32AM +0100, Jann Horn wrote: > The current sys_pidfd_send_signal() silently turns signals with explicit > SI_USER context that are sent to non-current tasks into signals with > kernel-generated siginfo. > This is unlike do_rt_sigqueueinfo(), which returns -EPERM in

[PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

2019-03-29 Thread Jann Horn
The current sys_pidfd_send_signal() silently turns signals with explicit SI_USER context that are sent to non-current tasks into signals with kernel-generated siginfo. This is unlike do_rt_sigqueueinfo(), which returns -EPERM in this case. If a user actually wants to send a signal with

RE: [PATCH] clk:Fix divide by 0 error in divider_ro_round_rate_parent

2019-03-29 Thread Nixiaoming
On 3/30/2019 6:42 AM Stephen Boyd wrote: >Quoting nixiaoming (2019-03-29 02:05:24) >> In the function divider_recalc_rate The judgment of the return value of > >Please write divider_recalc_rate() with parenthesis to show it's a >function. > >> _get_div indicates that the return value of _get_div

Re: [PATCH v2 4/5] signal: PIDFD_SIGNAL_TID threads via pidfds

2019-03-29 Thread Christian Brauner
On Sat, Mar 30, 2019 at 02:34:16AM +0100, Christian Brauner wrote: > On Sat, Mar 30, 2019 at 02:22:29AM +0100, Christian Brauner wrote: > > On Sat, Mar 30, 2019 at 02:06:34AM +0100, Jann Horn wrote: > > > On Fri, Mar 29, 2019 at 4:54 PM Christian Brauner > > > wrote: > > > > With the addition of

[PATCH AUTOSEL 4.19 21/57] compiler.h: update definition of unreachable()

2019-03-29 Thread Sasha Levin
From: "ndesaulni...@google.com" [ Upstream commit fe0640eb30b7da261ae84d252ed9ed3c7e68dfd8 ] Fixes the objtool warning seen with Clang: arch/x86/mm/fault.o: warning: objtool: no_context()+0x220: unreachable instruction Fixes commit 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h

[PATCH AUTOSEL 4.19 14/57] HID: i2c-hid: override HID descriptors for certain devices

2019-03-29 Thread Sasha Levin
From: Julian Sax [ Upstream commit 9ee3e06610fdb8a601cde59c92089fb6c1deb4aa ] A particular touchpad (SIPODEV SP1064) refuses to supply the HID descriptors. This patch provides the framework for overriding these descriptors based on DMI data. It also includes the descriptors for said touchpad,

[PATCH AUTOSEL 4.19 05/57] 9p: do not trust pdu content for stat item size

2019-03-29 Thread Sasha Levin
From: Gertjan Halkes [ Upstream commit 2803cf4379ed252894f046cb8812a48db35294e3 ] v9fs_dir_readdir() could deadloop if a struct was sent with a size set to -2 Link: http://lkml.kernel.org/r/1536134432-11997-1-git-send-email-asmad...@codewreck.org Bugzilla:

[PATCH AUTOSEL 4.19 17/57] usbip: fix vhci_hcd controller counting

2019-03-29 Thread Sasha Levin
From: Maciej Żenczykowski [ Upstream commit e0a2e73e501c77037c8756137e87b12c7c3c9793 ] Without this usbip fails on a machine with devices that lexicographically come after vhci_hcd. ie. $ ls -l /sys/devices/platform ... drwxr-xr-x. 4 root root0 Sep 19 16:21 serial8250 -rw-r--r--. 1

[PATCH AUTOSEL 4.19 11/57] powerpc/pseries: Remove prrn_work workqueue

2019-03-29 Thread Sasha Levin
From: Nathan Fontenot [ Upstream commit cd24e457fd8b2d087d9236700c8d2957054598bf ] When a PRRN event is received we are already running in a worker thread. Instead of spawning off another worker thread on the prrn_work workqueue to handle the PRRN event we can just call the PRRN handler routine

[PATCH AUTOSEL 4.19 19/57] HID: usbhid: Add quirk for Redragon/Dragonrise Seymur 2

2019-03-29 Thread Sasha Levin
From: Kai-Heng Feng [ Upstream commit ce9d58d3eafcb2d452a69bdcc1c5f8b8ff640de5 ] Redragon Seymur 2 stops working since commit 190d7f02ce8e ("HID: input: do not increment usages when a duplicate is found"). Use quirk HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE suggested by the commit can solve the

[PATCH AUTOSEL 4.19 06/57] 9p locks: add mount option for lock retry interval

2019-03-29 Thread Sasha Levin
From: Dinu-Razvan Chis-Serban [ Upstream commit 5e172f75e51e3de1b4274146d9b990f803cb5c2a ] The default P9_LOCK_TIMEOUT can be too long for some users exporting a local file system to a guest VM (30s), make this configurable at mount time. Link:

[PATCH AUTOSEL 4.19 18/57] ACPI / SBS: Fix GPE storm on recent MacBookPro's

2019-03-29 Thread Sasha Levin
From: Ronald Tschalär [ Upstream commit ca1721c5bee77105829cbd7baab8ee0eab85b06d ] On Apple machines, plugging-in or unplugging the power triggers a GPE for the EC. Since these machines expose an SBS device, this GPE ends up triggering the acpi_sbs_callback(). This in turn tries to get the

[PATCH AUTOSEL 4.19 07/57] ASoC: Fix UBSAN warning at snd_soc_get/put_volsw_sx()

2019-03-29 Thread Sasha Levin
From: Rohit kumar [ Upstream commit ae7d1247d8673ebfd686b17e759d4be391165368 ] In functions snd_soc_get_volsw_sx() or snd_soc_put_volsw_sx(), if the result of (min + max) is negative, then fls() returns signed integer with value as 32. This leads to signed integer overflow as complete operation

[PATCH AUTOSEL 4.19 03/57] rsi: improve kernel thread handling to fix kernel panic

2019-03-29 Thread Sasha Levin
From: Siva Rebbagondla [ Upstream commit 4c62764d0fc21a34ffc44eec1210038c3a2e4473 ] While running regressions, observed below kernel panic when sdio disconnect called. This is because of, kthread_stop() is taking care of wait_for_completion() by default. When wait_for_completion triggered in

[PATCH AUTOSEL 4.19 16/57] ARM: samsung: Limit SAMSUNG_PM_CHECK config option to non-Exynos platforms

2019-03-29 Thread Sasha Levin
From: Bartlomiej Zolnierkiewicz [ Upstream commit 6862fdf2201ab67cd962dbf0643d37db909f4860 ] "S3C2410 PM Suspend Memory CRC" feature (controlled by SAMSUNG_PM_CHECK config option) is incompatible with highmem (uses phys_to_virt() instead of proper mapping) which is used by the majority of

[PATCH AUTOSEL 4.19 02/57] gpio: pxa: handle corner case of unprobed device

2019-03-29 Thread Sasha Levin
From: Robert Jarzmik [ Upstream commit 9ce3ebe973bf4073426f35f282c6b955ed802765 ] In the corner case where the gpio driver probe fails, for whatever reason, the suspend and resume handlers will still be called as they have to be registered as syscore operations. This applies as well when no

[PATCH AUTOSEL 4.19 09/57] netfilter: xt_cgroup: shrink size of v2 path

2019-03-29 Thread Sasha Levin
From: Pablo Neira Ayuso [ Upstream commit 0d704967f4a49cc2212350b3e4a8231f8b4283ed ] cgroup v2 path field is PATH_MAX which is too large, this is placing too much pressure on memory allocation for people with many rules doing cgroup v1 classid matching, side effects of this are bug reports

[PATCH AUTOSEL 4.19 30/57] ALSA: hda: fix front speakers on Huawei MBXP

2019-03-29 Thread Sasha Levin
From: Ayman Bagabas [ Upstream commit 8ac51bbc4cfec4ef08b03bef24b31e2d50ef8b37 ] This patch solves bug 200501 'Only 2 of 4 speakers playing sound.' It enables the front speakers on Huawei Matebook X Pro laptops. These laptops come with Dolby Atmos sound system and these pins configuration

[PATCH AUTOSEL 4.19 29/57] drm/ttm: Fix bo_global and mem_global kfree error

2019-03-29 Thread Sasha Levin
From: Trigger Huang [ Upstream commit 30f33126feca0fe16df9e9302ffc28a953e2eb37 ] ttm_bo_glob and ttm_mem_glob are defined as structure instance, while not allocated by kzalloc, so kfree should not be invoked to release them anymore. Otherwise, it will cause the following kernel BUG when

[PATCH AUTOSEL 4.19 28/57] nvme-pci: fix conflicting p2p resource adds

2019-03-29 Thread Sasha Levin
From: Keith Busch [ Upstream commit 9fe5c59ff6a1e5e26a39b75489a1420e7eaaf0b1 ] The nvme pci driver had been adding its CMB resource to the P2P DMA subsystem everytime on on a controller reset. This results in the following warning: [ cut here ] nvme

[PATCH AUTOSEL 4.19 40/57] kvm: properly check debugfs dentry before using it

2019-03-29 Thread Sasha Levin
From: Greg Kroah-Hartman [ Upstream commit 8ed0579c12b2fe56a1fac2f712f58fc26c1dc49b ] debugfs can now report an error code if something went wrong instead of just NULL. So if the return value is to be used as a "real" dentry, it needs to be checked if it is an error before dereferencing it.

[PATCH AUTOSEL 4.19 33/57] blk-mq: protect debugfs_create_files() from failures

2019-03-29 Thread Sasha Levin
From: Greg Kroah-Hartman [ Upstream commit 36991ca68db9dd43bac7f3519f080ee3939263ef ] If debugfs were to return a non-NULL error for a debugfs call, using that pointer later in debugfs_create_files() would crash. Fix that by properly checking the pointer before referencing it. Reported-by:

[PATCH AUTOSEL 4.19 44/57] lkdtm: Add tests for NULL pointer dereference

2019-03-29 Thread Sasha Levin
From: Christophe Leroy [ Upstream commit 59a12205d3c32aee4c13ca36889fdf7cfed31126 ] Introduce lkdtm tests for NULL pointer dereference: check access or exec at NULL address, since these errors tend to be reported differently from the general fault error text. For example from x86:

[PATCH AUTOSEL 4.19 37/57] net: ip6_gre: fix possible NULL pointer dereference in ip6erspan_set_version

2019-03-29 Thread Sasha Levin
From: Lorenzo Bianconi [ Upstream commit efcc9bcaf77c07df01371a7c34e50424c291f3ac ] Fix a possible NULL pointer dereference in ip6erspan_set_version checking nlattr data pointer kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general

[PATCH AUTOSEL 4.19 41/57] soc/tegra: pmc: Drop locking from tegra_powergate_is_powered()

2019-03-29 Thread Sasha Levin
From: Dmitry Osipenko [ Upstream commit b6e1fd17a38bd1d97c11d69fd3207b3ef9bfa4b3 ] This fixes splats like the one below if CONFIG_DEBUG_ATOMIC_SLEEP=y and machine (Tegra30) booted with SMP=n or all secondary CPU's are put offline. Locking isn't needed because it protects atomic operation. BUG:

[PATCH AUTOSEL 4.19 43/57] lkdtm: Print real addresses

2019-03-29 Thread Sasha Levin
From: Christophe Leroy [ Upstream commit 4c411157a42f122051ae3469bee0b5cabe89e139 ] Today, when doing a lkdtm test before the readiness of the random generator, (ptrval) is printed instead of the address at which it perform the fault: [ 1597.337030] lkdtm: Performing direct entry

[PATCH AUTOSEL 4.19 42/57] ext4: prohibit fstrim in norecovery mode

2019-03-29 Thread Sasha Levin
From: "Darrick J. Wong" [ Upstream commit 18915b5873f07e5030e6fb108a050fa7c71c59fb ] The ext4 fstrim implementation uses the block bitmaps to find free space that can be discarded. If we haven't replayed the journal, the bitmaps will be stale and we absolutely *cannot* use stale metadata to

[PATCH AUTOSEL 4.19 38/57] iommu/dmar: Fix buffer overflow during PCI bus notification

2019-03-29 Thread Sasha Levin
From: Julia Cartwright [ Upstream commit cffaaf0c816238c45cd2d06913476c83eb50f682 ] Commit 57384592c433 ("iommu/vt-d: Store bus information in RMRR PCI device path") changed the type of the path data, however, the change in path type was not reflected in size calculations. Update to use the

[PATCH AUTOSEL 4.14 13/37] ACPI / SBS: Fix GPE storm on recent MacBookPro's

2019-03-29 Thread Sasha Levin
From: Ronald Tschalär [ Upstream commit ca1721c5bee77105829cbd7baab8ee0eab85b06d ] On Apple machines, plugging-in or unplugging the power triggers a GPE for the EC. Since these machines expose an SBS device, this GPE ends up triggering the acpi_sbs_callback(). This in turn tries to get the

[PATCH AUTOSEL 4.14 14/37] KVM: nVMX: restore host state in nested_vmx_vmexit for VMFail

2019-03-29 Thread Sasha Levin
From: Sean Christopherson [ Upstream commit bd18bffca35397214ae68d85cf7203aca25c3c1d ] A VMEnter that VMFails (as opposed to VMExits) does not touch host state beyond registers that are explicitly noted in the VMFail path, e.g. EFLAGS. Host state does not need to be loaded because VMFail is

[PATCH AUTOSEL 4.14 02/37] rsi: improve kernel thread handling to fix kernel panic

2019-03-29 Thread Sasha Levin
From: Siva Rebbagondla [ Upstream commit 4c62764d0fc21a34ffc44eec1210038c3a2e4473 ] While running regressions, observed below kernel panic when sdio disconnect called. This is because of, kthread_stop() is taking care of wait_for_completion() by default. When wait_for_completion triggered in

[PATCH AUTOSEL 4.14 15/37] compiler.h: update definition of unreachable()

2019-03-29 Thread Sasha Levin
From: "ndesaulni...@google.com" [ Upstream commit fe0640eb30b7da261ae84d252ed9ed3c7e68dfd8 ] Fixes the objtool warning seen with Clang: arch/x86/mm/fault.o: warning: objtool: no_context()+0x220: unreachable instruction Fixes commit 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h

[PATCH AUTOSEL 4.14 04/37] 9p locks: add mount option for lock retry interval

2019-03-29 Thread Sasha Levin
From: Dinu-Razvan Chis-Serban [ Upstream commit 5e172f75e51e3de1b4274146d9b990f803cb5c2a ] The default P9_LOCK_TIMEOUT can be too long for some users exporting a local file system to a guest VM (30s), make this configurable at mount time. Link:

[PATCH AUTOSEL 4.14 18/37] nvme-pci: fix conflicting p2p resource adds

2019-03-29 Thread Sasha Levin
From: Keith Busch [ Upstream commit 9fe5c59ff6a1e5e26a39b75489a1420e7eaaf0b1 ] The nvme pci driver had been adding its CMB resource to the P2P DMA subsystem everytime on on a controller reset. This results in the following warning: [ cut here ] nvme

[PATCH AUTOSEL 4.14 03/37] 9p: do not trust pdu content for stat item size

2019-03-29 Thread Sasha Levin
From: Gertjan Halkes [ Upstream commit 2803cf4379ed252894f046cb8812a48db35294e3 ] v9fs_dir_readdir() could deadloop if a struct was sent with a size set to -2 Link: http://lkml.kernel.org/r/1536134432-11997-1-git-send-email-asmad...@codewreck.org Bugzilla:

[PATCH AUTOSEL 4.14 23/37] kvm: properly check debugfs dentry before using it

2019-03-29 Thread Sasha Levin
From: Greg Kroah-Hartman [ Upstream commit 8ed0579c12b2fe56a1fac2f712f58fc26c1dc49b ] debugfs can now report an error code if something went wrong instead of just NULL. So if the return value is to be used as a "real" dentry, it needs to be checked if it is an error before dereferencing it.

[PATCH AUTOSEL 4.14 17/37] kernel: hung_task.c: disable on suspend

2019-03-29 Thread Sasha Levin
From: Vitaly Kuznetsov [ Upstream commit a1c6ca3c6de763459a6e93b644ec6518c890ba1c ] It is possible to observe hung_task complaints when system goes to suspend-to-idle state: # echo freeze > /sys/power/state PM: Syncing filesystems ... done. Freezing user space processes ... (elapsed 0.001

[PATCH AUTOSEL 4.14 19/37] blk-mq: protect debugfs_create_files() from failures

2019-03-29 Thread Sasha Levin
From: Greg Kroah-Hartman [ Upstream commit 36991ca68db9dd43bac7f3519f080ee3939263ef ] If debugfs were to return a non-NULL error for a debugfs call, using that pointer later in debugfs_create_files() would crash. Fix that by properly checking the pointer before referencing it. Reported-by:

[PATCH AUTOSEL 4.14 25/37] ext4: prohibit fstrim in norecovery mode

2019-03-29 Thread Sasha Levin
From: "Darrick J. Wong" [ Upstream commit 18915b5873f07e5030e6fb108a050fa7c71c59fb ] The ext4 fstrim implementation uses the block bitmaps to find free space that can be discarded. If we haven't replayed the journal, the bitmaps will be stale and we absolutely *cannot* use stale metadata to

[PATCH AUTOSEL 4.14 16/37] cifs: fallback to older infolevels on findfirst queryinfo retry

2019-03-29 Thread Sasha Levin
From: Steve French [ Upstream commit 3b7960caceafdfc2cdfe2850487f8d091eb41144 ] In cases where queryinfo fails, we have cases in cifs (vers=1.0) where with backupuid mounts we retry the query info with findfirst. This doesn't work to some NetApp servers which don't support WindowsXP (and later)

[PATCH AUTOSEL 4.14 27/37] lkdtm: Add tests for NULL pointer dereference

2019-03-29 Thread Sasha Levin
From: Christophe Leroy [ Upstream commit 59a12205d3c32aee4c13ca36889fdf7cfed31126 ] Introduce lkdtm tests for NULL pointer dereference: check access or exec at NULL address, since these errors tend to be reported differently from the general fault error text. For example from x86:

[PATCH AUTOSEL 4.14 24/37] soc/tegra: pmc: Drop locking from tegra_powergate_is_powered()

2019-03-29 Thread Sasha Levin
From: Dmitry Osipenko [ Upstream commit b6e1fd17a38bd1d97c11d69fd3207b3ef9bfa4b3 ] This fixes splats like the one below if CONFIG_DEBUG_ATOMIC_SLEEP=y and machine (Tegra30) booted with SMP=n or all secondary CPU's are put offline. Locking isn't needed because it protects atomic operation. BUG:

[PATCH AUTOSEL 4.9 09/21] ACPI / SBS: Fix GPE storm on recent MacBookPro's

2019-03-29 Thread Sasha Levin
From: Ronald Tschalär [ Upstream commit ca1721c5bee77105829cbd7baab8ee0eab85b06d ] On Apple machines, plugging-in or unplugging the power triggers a GPE for the EC. Since these machines expose an SBS device, this GPE ends up triggering the acpi_sbs_callback(). This in turn tries to get the

[PATCH AUTOSEL 4.9 02/21] rsi: improve kernel thread handling to fix kernel panic

2019-03-29 Thread Sasha Levin
From: Siva Rebbagondla [ Upstream commit 4c62764d0fc21a34ffc44eec1210038c3a2e4473 ] While running regressions, observed below kernel panic when sdio disconnect called. This is because of, kthread_stop() is taking care of wait_for_completion() by default. When wait_for_completion triggered in

[PATCH AUTOSEL 4.9 01/21] gpio: pxa: handle corner case of unprobed device

2019-03-29 Thread Sasha Levin
From: Robert Jarzmik [ Upstream commit 9ce3ebe973bf4073426f35f282c6b955ed802765 ] In the corner case where the gpio driver probe fails, for whatever reason, the suspend and resume handlers will still be called as they have to be registered as syscore operations. This applies as well when no

[PATCH AUTOSEL 4.9 03/21] 9p: do not trust pdu content for stat item size

2019-03-29 Thread Sasha Levin
From: Gertjan Halkes [ Upstream commit 2803cf4379ed252894f046cb8812a48db35294e3 ] v9fs_dir_readdir() could deadloop if a struct was sent with a size set to -2 Link: http://lkml.kernel.org/r/1536134432-11997-1-git-send-email-asmad...@codewreck.org Bugzilla:

[PATCH AUTOSEL 4.14 26/37] lkdtm: Print real addresses

2019-03-29 Thread Sasha Levin
From: Christophe Leroy [ Upstream commit 4c411157a42f122051ae3469bee0b5cabe89e139 ] Today, when doing a lkdtm test before the readiness of the random generator, (ptrval) is printed instead of the address at which it perform the fault: [ 1597.337030] lkdtm: Performing direct entry

[PATCH AUTOSEL 4.9 07/21] HID: i2c-hid: override HID descriptors for certain devices

2019-03-29 Thread Sasha Levin
From: Julian Sax [ Upstream commit 9ee3e06610fdb8a601cde59c92089fb6c1deb4aa ] A particular touchpad (SIPODEV SP1064) refuses to supply the HID descriptors. This patch provides the framework for overriding these descriptors based on DMI data. It also includes the descriptors for said touchpad,

[PATCH AUTOSEL 4.9 17/21] lkdtm: Add tests for NULL pointer dereference

2019-03-29 Thread Sasha Levin
From: Christophe Leroy [ Upstream commit 59a12205d3c32aee4c13ca36889fdf7cfed31126 ] Introduce lkdtm tests for NULL pointer dereference: check access or exec at NULL address, since these errors tend to be reported differently from the general fault error text. For example from x86:

[PATCH AUTOSEL 4.9 20/21] lib/div64.c: off by one in shift

2019-03-29 Thread Sasha Levin
From: Stanislaw Gruszka [ Upstream commit cdc94a37493135e355dfc0b0e086d84e3eadb50d ] fls counts bits starting from 1 to 32 (returns 0 for zero argument). If we add 1 we shift right one bit more and loose precision from divisor, what cause function incorect results with some numbers. Corrected

[PATCH AUTOSEL 4.4 03/16] 9p locks: add mount option for lock retry interval

2019-03-29 Thread Sasha Levin
From: Dinu-Razvan Chis-Serban [ Upstream commit 5e172f75e51e3de1b4274146d9b990f803cb5c2a ] The default P9_LOCK_TIMEOUT can be too long for some users exporting a local file system to a guest VM (30s), make this configurable at mount time. Link:

[PATCH AUTOSEL 4.9 18/21] ARM: 8839/1: kprobe: make patch_lock a raw_spinlock_t

2019-03-29 Thread Sasha Levin
From: Yang Shi [ Upstream commit 143c2a89e0e5fda6c6fd08d7bc1126438c19ae90 ] When running kprobe on -rt kernel, the below bug is caught: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931 |in_atomic(): 1, irqs_disabled(): 128, pid: 14, name: migration/0

[PATCH AUTOSEL 3.18 04/10] serial: uartps: console_setup() can't be placed to init section

2019-03-29 Thread Sasha Levin
From: Michal Simek [ Upstream commit 4bb1ce2350a598502b23088b169e16b43d4bc639 ] When console device is rebinded, console_setup() is called again. But marking it as __init means that function will be clear after boot is complete. If console device is binded again console_setup() is not found and

[PATCH AUTOSEL 3.18 03/10] 9p locks: add mount option for lock retry interval

2019-03-29 Thread Sasha Levin
From: Dinu-Razvan Chis-Serban [ Upstream commit 5e172f75e51e3de1b4274146d9b990f803cb5c2a ] The default P9_LOCK_TIMEOUT can be too long for some users exporting a local file system to a guest VM (30s), make this configurable at mount time. Link:

[PATCH AUTOSEL 3.18 01/10] rsi: improve kernel thread handling to fix kernel panic

2019-03-29 Thread Sasha Levin
From: Siva Rebbagondla [ Upstream commit 4c62764d0fc21a34ffc44eec1210038c3a2e4473 ] While running regressions, observed below kernel panic when sdio disconnect called. This is because of, kthread_stop() is taking care of wait_for_completion() by default. When wait_for_completion triggered in

[PATCH AUTOSEL 3.18 07/10] iommu/dmar: Fix buffer overflow during PCI bus notification

2019-03-29 Thread Sasha Levin
From: Julia Cartwright [ Upstream commit cffaaf0c816238c45cd2d06913476c83eb50f682 ] Commit 57384592c433 ("iommu/vt-d: Store bus information in RMRR PCI device path") changed the type of the path data, however, the change in path type was not reflected in size calculations. Update to use the

Re: [PATCH v2 4/5] signal: PIDFD_SIGNAL_TID threads via pidfds

2019-03-29 Thread Christian Brauner
On Sat, Mar 30, 2019 at 02:22:29AM +0100, Christian Brauner wrote: > On Sat, Mar 30, 2019 at 02:06:34AM +0100, Jann Horn wrote: > > On Fri, Mar 29, 2019 at 4:54 PM Christian Brauner > > wrote: > > > With the addition of pidfd_open() it is possible for users to reference a > > > specific thread

[PATCH AUTOSEL 4.4 07/16] ACPI / SBS: Fix GPE storm on recent MacBookPro's

2019-03-29 Thread Sasha Levin
From: Ronald Tschalär [ Upstream commit ca1721c5bee77105829cbd7baab8ee0eab85b06d ] On Apple machines, plugging-in or unplugging the power triggers a GPE for the EC. Since these machines expose an SBS device, this GPE ends up triggering the acpi_sbs_callback(). This in turn tries to get the

[PATCH AUTOSEL 3.18 05/10] ARM: samsung: Limit SAMSUNG_PM_CHECK config option to non-Exynos platforms

2019-03-29 Thread Sasha Levin
From: Bartlomiej Zolnierkiewicz [ Upstream commit 6862fdf2201ab67cd962dbf0643d37db909f4860 ] "S3C2410 PM Suspend Memory CRC" feature (controlled by SAMSUNG_PM_CHECK config option) is incompatible with highmem (uses phys_to_virt() instead of proper mapping) which is used by the majority of

[PATCH AUTOSEL 3.18 02/10] 9p: do not trust pdu content for stat item size

2019-03-29 Thread Sasha Levin
From: Gertjan Halkes [ Upstream commit 2803cf4379ed252894f046cb8812a48db35294e3 ] v9fs_dir_readdir() could deadloop if a struct was sent with a size set to -2 Link: http://lkml.kernel.org/r/1536134432-11997-1-git-send-email-asmad...@codewreck.org Bugzilla:

[PATCH AUTOSEL 4.4 06/16] ARM: samsung: Limit SAMSUNG_PM_CHECK config option to non-Exynos platforms

2019-03-29 Thread Sasha Levin
From: Bartlomiej Zolnierkiewicz [ Upstream commit 6862fdf2201ab67cd962dbf0643d37db909f4860 ] "S3C2410 PM Suspend Memory CRC" feature (controlled by SAMSUNG_PM_CHECK config option) is incompatible with highmem (uses phys_to_virt() instead of proper mapping) which is used by the majority of

[PATCH AUTOSEL 4.4 04/16] f2fs: fix to do sanity check with current segment number

2019-03-29 Thread Sasha Levin
From: Chao Yu [ Upstream commit 042be0f849e5fc24116d0afecfaf926eed5cac63 ] https://bugzilla.kernel.org/show_bug.cgi?id=200219 Reproduction way: - mount image - run poc code - umount image F2FS-fs (loop1): Bitmap was wrongly set, blk:15364 [ cut here ] kernel BUG at

[PATCH AUTOSEL 4.4 05/16] serial: uartps: console_setup() can't be placed to init section

2019-03-29 Thread Sasha Levin
From: Michal Simek [ Upstream commit 4bb1ce2350a598502b23088b169e16b43d4bc639 ] When console device is rebinded, console_setup() is called again. But marking it as __init means that function will be clear after boot is complete. If console device is binded again console_setup() is not found and

[PATCH AUTOSEL 4.4 02/16] 9p: do not trust pdu content for stat item size

2019-03-29 Thread Sasha Levin
From: Gertjan Halkes [ Upstream commit 2803cf4379ed252894f046cb8812a48db35294e3 ] v9fs_dir_readdir() could deadloop if a struct was sent with a size set to -2 Link: http://lkml.kernel.org/r/1536134432-11997-1-git-send-email-asmad...@codewreck.org Bugzilla:

[PATCH AUTOSEL 4.4 16/16] include/linux/swap.h: use offsetof() instead of custom __swapoffset macro

2019-03-29 Thread Sasha Levin
From: Pi-Hsun Shih [ Upstream commit a4046c06be50a4f01d435aa7fe57514818e6cc82 ] Use offsetof() to calculate offset of a field to take advantage of compiler built-in version when possible, and avoid UBSAN warning when compiling with Clang: UBSAN: Undefined behaviour in mm/swapfile.c:3010:38

[PATCH AUTOSEL 3.18 10/10] include/linux/swap.h: use offsetof() instead of custom __swapoffset macro

2019-03-29 Thread Sasha Levin
From: Pi-Hsun Shih [ Upstream commit a4046c06be50a4f01d435aa7fe57514818e6cc82 ] Use offsetof() to calculate offset of a field to take advantage of compiler built-in version when possible, and avoid UBSAN warning when compiling with Clang: UBSAN: Undefined behaviour in mm/swapfile.c:3010:38

[PATCH AUTOSEL 3.18 09/10] lib/div64.c: off by one in shift

2019-03-29 Thread Sasha Levin
From: Stanislaw Gruszka [ Upstream commit cdc94a37493135e355dfc0b0e086d84e3eadb50d ] fls counts bits starting from 1 to 32 (returns 0 for zero argument). If we add 1 we shift right one bit more and loose precision from divisor, what cause function incorect results with some numbers. Corrected

[PATCH AUTOSEL 4.4 12/16] ext4: prohibit fstrim in norecovery mode

2019-03-29 Thread Sasha Levin
From: "Darrick J. Wong" [ Upstream commit 18915b5873f07e5030e6fb108a050fa7c71c59fb ] The ext4 fstrim implementation uses the block bitmaps to find free space that can be discarded. If we haven't replayed the journal, the bitmaps will be stale and we absolutely *cannot* use stale metadata to

[PATCH AUTOSEL 4.4 10/16] crypto: sha512/arm - fix crash bug in Thumb2 build

2019-03-29 Thread Sasha Levin
From: Ard Biesheuvel [ Upstream commit c64316502008064c158fa40cc250665e461b0f2a ] The SHA512 code we adopted from the OpenSSL project uses a rather peculiar way to take the address of the round constant table: it takes the address of the sha256_block_data_order() routine, and substracts a

[PATCH AUTOSEL 3.18 06/10] ACPI / SBS: Fix GPE storm on recent MacBookPro's

2019-03-29 Thread Sasha Levin
From: Ronald Tschalär [ Upstream commit ca1721c5bee77105829cbd7baab8ee0eab85b06d ] On Apple machines, plugging-in or unplugging the power triggers a GPE for the EC. Since these machines expose an SBS device, this GPE ends up triggering the acpi_sbs_callback(). This in turn tries to get the

[PATCH AUTOSEL 4.4 08/16] cifs: fallback to older infolevels on findfirst queryinfo retry

2019-03-29 Thread Sasha Levin
From: Steve French [ Upstream commit 3b7960caceafdfc2cdfe2850487f8d091eb41144 ] In cases where queryinfo fails, we have cases in cifs (vers=1.0) where with backupuid mounts we retry the query info with findfirst. This doesn't work to some NetApp servers which don't support WindowsXP (and later)

[PATCH AUTOSEL 4.4 13/16] ARM: 8839/1: kprobe: make patch_lock a raw_spinlock_t

2019-03-29 Thread Sasha Levin
From: Yang Shi [ Upstream commit 143c2a89e0e5fda6c6fd08d7bc1126438c19ae90 ] When running kprobe on -rt kernel, the below bug is caught: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931 |in_atomic(): 1, irqs_disabled(): 128, pid: 14, name: migration/0

[PATCH AUTOSEL 4.9 19/21] appletalk: Fix use-after-free in atalk_proc_exit

2019-03-29 Thread Sasha Levin
From: YueHaibing [ Upstream commit 6377f787aeb945cae7abbb6474798de129e1f3ac ] KASAN report this: BUG: KASAN: use-after-free in pde_subdir_find+0x12d/0x150 fs/proc/generic.c:71 Read of size 8 at addr 8881f41fe5b0 by task syz-executor.0/2806 CPU: 0 PID: 2806 Comm: syz-executor.0 Not tainted

[PATCH AUTOSEL 4.9 08/21] ARM: samsung: Limit SAMSUNG_PM_CHECK config option to non-Exynos platforms

2019-03-29 Thread Sasha Levin
From: Bartlomiej Zolnierkiewicz [ Upstream commit 6862fdf2201ab67cd962dbf0643d37db909f4860 ] "S3C2410 PM Suspend Memory CRC" feature (controlled by SAMSUNG_PM_CHECK config option) is incompatible with highmem (uses phys_to_virt() instead of proper mapping) which is used by the majority of

[PATCH AUTOSEL 4.9 21/21] include/linux/swap.h: use offsetof() instead of custom __swapoffset macro

2019-03-29 Thread Sasha Levin
From: Pi-Hsun Shih [ Upstream commit a4046c06be50a4f01d435aa7fe57514818e6cc82 ] Use offsetof() to calculate offset of a field to take advantage of compiler built-in version when possible, and avoid UBSAN warning when compiling with Clang: UBSAN: Undefined behaviour in mm/swapfile.c:3010:38

[PATCH AUTOSEL 4.4 15/16] lib/div64.c: off by one in shift

2019-03-29 Thread Sasha Levin
From: Stanislaw Gruszka [ Upstream commit cdc94a37493135e355dfc0b0e086d84e3eadb50d ] fls counts bits starting from 1 to 32 (returns 0 for zero argument). If we add 1 we shift right one bit more and loose precision from divisor, what cause function incorect results with some numbers. Corrected

[PATCH AUTOSEL 4.9 10/21] cifs: fallback to older infolevels on findfirst queryinfo retry

2019-03-29 Thread Sasha Levin
From: Steve French [ Upstream commit 3b7960caceafdfc2cdfe2850487f8d091eb41144 ] In cases where queryinfo fails, we have cases in cifs (vers=1.0) where with backupuid mounts we retry the query info with findfirst. This doesn't work to some NetApp servers which don't support WindowsXP (and later)

[PATCH AUTOSEL 4.4 14/16] appletalk: Fix use-after-free in atalk_proc_exit

2019-03-29 Thread Sasha Levin
From: YueHaibing [ Upstream commit 6377f787aeb945cae7abbb6474798de129e1f3ac ] KASAN report this: BUG: KASAN: use-after-free in pde_subdir_find+0x12d/0x150 fs/proc/generic.c:71 Read of size 8 at addr 8881f41fe5b0 by task syz-executor.0/2806 CPU: 0 PID: 2806 Comm: syz-executor.0 Not tainted

[PATCH AUTOSEL 4.9 05/21] f2fs: fix to do sanity check with current segment number

2019-03-29 Thread Sasha Levin
From: Chao Yu [ Upstream commit 042be0f849e5fc24116d0afecfaf926eed5cac63 ] https://bugzilla.kernel.org/show_bug.cgi?id=200219 Reproduction way: - mount image - run poc code - umount image F2FS-fs (loop1): Bitmap was wrongly set, blk:15364 [ cut here ] kernel BUG at

  1   2   3   4   5   6   7   8   9   10   >