[PATCH 4.19 38/72] staging: rtlwifi: rtl8822b: fix to avoid potential NULL pointer dereference

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit d70d70aec9632679dd00dcc1b1e8b2517e2c7da0 ] skb allocated via dev_alloc_skb can fail and return a NULL pointer. This patch avoids such a scenario and returns, consistent with other invocations. Signed-off-by: Aditya Pakki Reviewed-by: Mukesh Ojha Signed-off-by: Greg Kroah-Hartm

Alloc refcount increments to fail

2019-05-02 Thread Matthew Wilcox
In the comments section of a recent LWN article [1], Neil asked if we could have a way for refcount users to avoid getting to the saturated state if they have a way of handling fallback gracefully. Here's an attempt to provide that functionality. I'm not sure it's compatible with Kees' "x86/asm

[PATCH 4.19 12/72] qlcnic: Avoid potential NULL pointer dereference

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 5bf7295fe34a5251b1d241b9736af4697b590670 ] netdev_alloc_skb can fail and return a NULL pointer which is dereferenced without a check. The patch avoids such a scenario. Signed-off-by: Aditya Pakki Signed-off-by: David S. Miller Signed-off-by: Sasha Levin (Microsoft) --- drive

[PATCH 4.19 27/72] usb: dwc3: pci: add support for Comet Lake PCH ID

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 7ae622c978db6b2e28b4fced6ecd2a174492059d ] This patch simply adds a new PCI Device ID Signed-off-by: Felipe Balbi Signed-off-by: Sasha Levin (Microsoft) --- drivers/usb/dwc3/dwc3-pci.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drive

[PATCH 4.19 20/72] s390/qeth: fix race when initializing the IP address table

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 7221b727f0079a32aca91f657141e1de564d4b97 ] The ucast IP table is utilized by some of the L3-specific sysfs attributes that qeth_l3_create_device_attributes() provides. So initialize the table _before_ registering the attributes. Fixes: ebccc7397e4a ("s390/qeth: add missing hash

[PATCH 4.19 07/72] ARM: dts: bcm283x: Fix hdmi hpd gpio pull

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 544e784188f1dd7c797c70b213385e67d92005b6 ] Raspberry pi board model B revison 2 have the hot plug detector gpio active high (and not low as it was in the dts). Signed-off-by: Helen Koike Fixes: 49ac67e0c39c ("ARM: bcm2835: Add VC4 to the device tree.") Reviewed-by: Eric Anholt

[PATCH 4.19 08/72] s390: limit brk randomization to 32MB

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit cd479eccd2e057116d504852814402a1e68ead80 ] For a 64-bit process the randomization of the program break is quite large with 1GB. That is as big as the randomization of the anonymous mapping base, for a test case started with '/lib/ld64.so.1 ' it can happen that the heap is placed

[PATCH 4.19 04/72] mm: add try_get_page() helper function

2019-05-02 Thread Greg Kroah-Hartman
From: Linus Torvalds commit 88b1a17dfc3ed7728316478fae0f5ad508f50397 upstream. This is the same as the traditional 'get_page()' function, but instead of unconditionally incrementing the reference count of the page, it only does so if the count was "safe". It returns whether the reference count

[PATCH 4.14 28/49] staging: rtlwifi: Fix potential NULL pointer dereference of kzalloc

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 6a8ca24590a2136921439b376c926c11a6effc0e ] phydm.internal is allocated using kzalloc which is used multiple times without a check for NULL pointer. This patch avoids such a scenario by returning 0, consistent with the failure case. Signed-off-by: Aditya Pakki Reviewed-by: Mukes

[PATCH 4.19 03/72] mm: make page ref count overflow check tighter and more explicit

2019-05-02 Thread Greg Kroah-Hartman
From: Linus Torvalds commit f958d7b528b1b40c44cfda5eabe2d82760d868c3 upstream. We have a VM_BUG_ON() to check that the page reference count doesn't underflow (or get close to overflow) by checking the sign of the count. That's all fine, but we actually want to allow people to use a "get page re

[PATCH 4.14 32/49] NFS: Fix a typo in nfs_init_timeout_values()

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 5a698243930c441afccec04e4d5dc8febfd2b775 ] Specifying a retrans=0 mount parameter to a NFS/TCP mount, is inadvertently causing the NFS client to rewrite any specified timeout parameter to the default of 60 seconds. Fixes: a956beda19a6 ("NFS: Allow the mount option retrans=0") Si

[PATCH 4.14 48/49] ptrace: take into account saved_sigmask in PTRACE{GET,SET}SIGMASK

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit fcfc2aa0185f4a731d05a21e9f359968fdfd02e7 ] There are a few system calls (pselect, ppoll, etc) which replace a task sigmask while they are running in a kernel-space When a task calls one of these syscalls, the kernel saves a current sigmask in task->saved_sigmask and sets a sysca

[PATCH 4.14 36/49] gpio: aspeed: fix a potential NULL pointer dereference

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 6cf4511e9729c00a7306cf94085f9cc3c52ee723 ] In case devm_kzalloc, the patch returns ENOMEM to avoid potential NULL pointer dereference. Signed-off-by: Kangjie Lu Reviewed-by: Andrew Jeffery Signed-off-by: Bartosz Golaszewski Signed-off-by: Sasha Levin (Microsoft) --- drivers

[PATCH 4.14 35/49] net: ethernet: ti: fix possible object reference leak

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 75eac7b5f68b0a0671e795ac636457ee27cc11d8 ] The call to of_get_child_by_name returns a node pointer with refcount incremented thus it must be explicitly decremented after the last usage. Detected by coccinelle with the following warnings: ./drivers/net/ethernet/ti/netcp_ethss.c:3

[PATCH 4.14 47/49] iommu/amd: Reserve exclusion range in iova-domain

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 8aafaaf2212192012f5bae305bb31cdf7681d777 ] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Trea

[PATCH 4.14 49/49] leds: pca9532: fix a potential NULL pointer dereference

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 0aab8e4df4702b31314a27ec4b0631dfad0fae0a ] In case of_match_device cannot find a match, return -EINVAL to avoid NULL pointer dereference. Fixes: fa4191a609f2 ("leds: pca9532: Add device tree support") Signed-off-by: Kangjie Lu Signed-off-by: Jacek Anaszewski Signed-off-by: Sas

[PATCH 4.14 44/49] libata: fix using DMA buffers on stack

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit dd08a8d9a66de4b54575c294a92630299f7e0fe7 ] When CONFIG_VMAP_STACK=y, __pa() returns incorrect physical address for a stack virtual address. Stack DMA buffers must be avoided. Signed-off-by: raymond pang Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin (Microsoft) --- dri

[PATCH 4.14 38/49] drm/meson: Uninstall IRQ handler

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 2d8f92897ad816f5dda54b2ed2fd9f2d7cb1abde ] meson_drv_unbind() doesn't unregister the IRQ handler, which can lead to use-after-free if the IRQ fires after unbind: [ 64.656876] Unable to handle kernel paging request at virtual address 11706dbc ... [ 64.662001] pc : me

[PATCH 4.14 43/49] scsi: zfcp: reduce flood of fcrscn1 trace records on multi-element RSCN

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit c8206579175c34a2546de8a74262456278a7795a ] If an incoming ELS of type RSCN contains more than one element, zfcp suboptimally causes repeated erp trigger NOP trace records for each previously failed port. These could be ports that went away. It loops over each RSCN element, and f

[PATCH 4.14 42/49] ceph: fix use-after-free on symlink traversal

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit daf5cc27eed99afdea8d96e71b89ba41f5406ef6 ] free the symlink body after the same RCU delay we have for freeing the struct inode itself, so that traversal during RCU pathwalk wouldn't step into freed memory. Signed-off-by: Al Viro Reviewed-by: Jeff Layton Signed-off-by: Ilya Dry

Re: Alloc refcount increments to fail

2019-05-02 Thread Al Viro
On Thu, May 02, 2019 at 08:26:21AM -0700, Matthew Wilcox wrote: > +/** > + * refcount_try_inc - Increment a refcount if it's below INT_MAX > + * @r: the refcount to increment > + * > + * Avoid the counter saturating by declining to increment the counter > + * if it is more than halfway to saturati

[PATCH 4.14 29/49] net: macb: Add null check for PCLK and HCLK

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit cd5afa91f078c0787be0a62b5ef90301c00b0271 ] Both PCLK and HCLK are "required" clocks according to macb devicetree documentation. There is a chance that devm_clk_get doesn't return a negative error but just a NULL clock structure instead. In such a case the driver proceeds as usual

[PATCH 4.14 26/49] staging: rtlwifi: rtl8822b: fix to avoid potential NULL pointer dereference

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit d70d70aec9632679dd00dcc1b1e8b2517e2c7da0 ] skb allocated via dev_alloc_skb can fail and return a NULL pointer. This patch avoids such a scenario and returns, consistent with other invocations. Signed-off-by: Aditya Pakki Reviewed-by: Mukesh Ojha Signed-off-by: Greg Kroah-Hartm

[PATCH 4.14 07/49] fs: prevent page refcount overflow in pipe_buf_get

2019-05-02 Thread Greg Kroah-Hartman
From: Matthew Wilcox commit 15fab63e1e57be9fdb5eec1bbc5916e9825e9acb upstream. Change pipe_buf_get() to return a bool indicating whether it succeeded in raising the refcount of the page (if the thing in the pipe is a page). This removes another mechanism for overflowing the page refcount. All c

[PATCH 4.14 06/49] mm: prevent get_user_pages() from overflowing page refcount

2019-05-02 Thread Greg Kroah-Hartman
From: Linus Torvalds commit 8fde12ca79aff9b5ba951fce1a2641901b8d8e64 upstream. If the page refcount wraps around past zero, it will be freed while there are still four billion references to it. One of the possible avenues for an attacker to try to make this happen is by doing direct IO on a pag

[PATCH 4.14 09/49] s390: limit brk randomization to 32MB

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit cd479eccd2e057116d504852814402a1e68ead80 ] For a 64-bit process the randomization of the program break is quite large with 1GB. That is as big as the randomization of the anonymous mapping base, for a test case started with '/lib/ld64.so.1 ' it can happen that the heap is placed

[PATCH 4.14 21/49] net: ks8851: Dequeue RX packets explicitly

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 536d3680fd2dab5c39857d62a3e084198fc74ff9 ] The ks8851 driver lets the chip auto-dequeue received packets once they have been read in full. It achieves that by setting the ADRFE flag in the RXQCR register ("Auto-Dequeue RXQ Frame Enable"). However if allocation of a packet's sock

[PATCH 4.14 17/49] usb: gadget: net2280: Fix overrun of OUT messages

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 9d6a54c1430647355a5e23434881b2ca3d192b48 ] The OUT endpoint normally blocks (NAK) subsequent packets when a short packet was received and returns an incomplete queue entry to the gadget driver. Thereby the gadget driver can detect a short packet when reading queue entries with a

[PATCH 4.14 14/49] sc16is7xx: missing unregister/delete driver on error in sc16is7xx_init()

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit ac0cdb3d990108df795b676cd0d0e65ac34b2273 ] Add the missing uart_unregister_driver() and i2c_del_driver() before return from sc16is7xx_init() in the error handling case. Signed-off-by: Mao Wenan Reviewed-by: Vladimir Zapolskiy Signed-off-by: Greg Kroah-Hartman Signed-off-by: S

[PATCH 4.14 10/49] qlcnic: Avoid potential NULL pointer dereference

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 5bf7295fe34a5251b1d241b9736af4697b590670 ] netdev_alloc_skb can fail and return a NULL pointer which is dereferenced without a check. The patch avoids such a scenario. Signed-off-by: Aditya Pakki Signed-off-by: David S. Miller Signed-off-by: Sasha Levin (Microsoft) --- drive

[PATCH 4.9 17/32] net: ks8851: Delay requesting IRQ until opened

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit d268f31552794abf5b6aa5af31021643411f25f5 ] The ks8851 driver currently requests the IRQ before registering the net_device. Because the net_device name is used as IRQ name and is still "eth%d" when the IRQ is requested, it's impossibe to tell IRQs apart if multiple ks8851 chips a

Re: [PATCH] kexec_buffer measure

2019-05-02 Thread Mimi Zohar
[Cc'ing Paul, John, Casey] On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote: > [Cc'ing LSM mailing list] > > On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote: > > > 2) Adding a LSM hook > > We are doing both the command line and kernel version measurement in IMA. > > Can you please

[PATCH 4.9 32/32] vfio/type1: Limit DMA mappings per container

2019-05-02 Thread Greg Kroah-Hartman
From: Alex Williamson commit 492855939bdb59c6f947b0b5b44af9ad82b7e38c upstream. Memory backed DMA mappings are accounted against a user's locked memory limit, including multiple mappings of the same memory. This accounting bounds the number of such mappings that a user can create. However, DMA

[PATCH 4.9 12/32] usb: gadget: net2280: Fix net2280_dequeue()

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit f1d3fba17cd4eeea20397f1324b7b9c69a6a935c ] When a request must be dequeued with net2280_dequeue() e.g. due to a device clear action and the same request is finished by the function scan_dma_completions() then the function net2280_dequeue() does not find the request in the followi

[GIT] Networking

2019-05-02 Thread David Miller
1) Out of bounds access in xfrm IPSEC policy unlink, from Yue Haibing. 2) Missing length check for esp4 UDP encap, from Sabrina Dubroca. 3) Fix byte order of RX STBC access in mac80211, from Johannes Berg. 4) Inifnite loop in bpftool map create, from Alban Crequy. 5) Register mark fix in ebpf

Re: [PATCH 1/2] ARM: dts: imx6ul: Add csi node

2019-05-02 Thread Rui Miguel Silva
Oi Fabio, On Thu 02 May 2019 at 16:28, Fabio Estevam wrote: > [Adding Rui] > > On Tue, Apr 30, 2019 at 4:47 AM Sébastien Szymanski > wrote: >> >> Add csi node for i.MX6UL SoC. >> >> Signed-off-by: Sébastien Szymanski >> --- >> arch/arm/boot/dts/imx6ul.dtsi | 11 +++ >> 1 file changed, 11

[PATCH 4.9 25/32] usb: u132-hcd: fix resource leak

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit f276e002793cdb820862e8ea8f76769d56bba575 ] if platform_driver_register fails, cleanup the allocated resource gracefully. Signed-off-by: Mukesh Ojha Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin (Microsoft) --- drivers/usb/host/u132-hcd.c | 3 +++ 1 file change

[PATCH 4.9 20/32] NFS: Fix a typo in nfs_init_timeout_values()

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 5a698243930c441afccec04e4d5dc8febfd2b775 ] Specifying a retrans=0 mount parameter to a NFS/TCP mount, is inadvertently causing the NFS client to rewrite any specified timeout parameter to the default of 60 seconds. Fixes: a956beda19a6 ("NFS: Allow the mount option retrans=0") Si

[PATCH 4.9 09/32] sc16is7xx: missing unregister/delete driver on error in sc16is7xx_init()

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit ac0cdb3d990108df795b676cd0d0e65ac34b2273 ] Add the missing uart_unregister_driver() and i2c_del_driver() before return from sc16is7xx_init() in the error handling case. Signed-off-by: Mao Wenan Reviewed-by: Vladimir Zapolskiy Signed-off-by: Greg Kroah-Hartman Signed-off-by: S

[PATCH 4.9 11/32] usb: gadget: net2280: Fix overrun of OUT messages

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 9d6a54c1430647355a5e23434881b2ca3d192b48 ] The OUT endpoint normally blocks (NAK) subsequent packets when a short packet was received and returns an incomplete queue entry to the gadget driver. Thereby the gadget driver can detect a short packet when reading queue entries with a

[PATCH 4.9 00/32] 4.9.173-stable review

2019-05-02 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.9.173 release. There are 32 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat 04 May 2019 02:32:02 PM UTC. Anything rec

[PATCH 4.9 04/32] ARM: dts: bcm283x: Fix hdmi hpd gpio pull

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit 544e784188f1dd7c797c70b213385e67d92005b6 ] Raspberry pi board model B revison 2 have the hot plug detector gpio active high (and not low as it was in the dts). Signed-off-by: Helen Koike Fixes: 49ac67e0c39c ("ARM: bcm2835: Add VC4 to the device tree.") Reviewed-by: Eric Anholt

[PATCH 4.9 05/32] s390: limit brk randomization to 32MB

2019-05-02 Thread Greg Kroah-Hartman
[ Upstream commit cd479eccd2e057116d504852814402a1e68ead80 ] For a 64-bit process the randomization of the program break is quite large with 1GB. That is as big as the randomization of the anonymous mapping base, for a test case started with '/lib/ld64.so.1 ' it can happen that the heap is placed

[PATCH] MAINTAINERS: include vendor specific files under arch/*/events/*

2019-05-02 Thread Phillips, Kim
From: Kim Phillips Add an explicit subdirectory specification for arch/x86/events/amd to the MAINTAINERS file, to distinguish it from its parent. This will produce the correct set of maintainers for the files found therein. Fixes: 39b0332a2158 ("perf/x86: Move perf_event_amd.c ... => x8

Re: [PATCH v2 1/2] Add polling support to pidfd

2019-05-02 Thread Oleg Nesterov
On 05/02, Christian Brauner wrote: > > On Wed, May 01, 2019 at 05:13:12PM +0200, Oleg Nesterov wrote: > > > > Otherwise I see no problems. > > I'll remove the WARN_ON() check when applying this. Can I get your > Acked/Review, Oleg? Yes, feel free to add Reviewed-by: Oleg Nesterov Hmm.

[PATCH v4] platform/chrome: mfd/cros_ec_debugfs: Add debugfs entry to retrieve EC uptime.

2019-05-02 Thread Tim Wawrzynczak
The new debugfs entry 'uptime' is being made available to userspace so that a userspace daemon can synchronize EC logs with host time. Signed-off-by: Tim Wawrzynczak --- Enric, is there something I can do to help speed this along? This patch is useful for ChromeOS board bringup, and we would lik

Re: [RFC] Disable lockref on arm64

2019-05-02 Thread Linus Torvalds
On Thu, May 2, 2019 at 1:27 AM Jan Glauber wrote: > > I'll see how x86 runs the same testcase, I thought that playing > cacheline ping-pong is not the optimal use case for any CPU. Oh, ping-pong is always bad. But from past experience, x86 tends to be able to always do tight a cmpxchg loop witho

Re: [PATCH v3 1/4] ptrace: move clearing of TIF_SYSCALL_EMU flag to core

2019-05-02 Thread Oleg Nesterov
On 05/01, Sudeep Holla wrote: > > On Wed, May 01, 2019 at 06:13:30PM +0200, Oleg Nesterov wrote: > > On 04/30, Sudeep Holla wrote: > > > > > > While the TIF_SYSCALL_EMU is set in ptrace_resume independent of any > > > architecture, currently only powerpc and x86 unset the TIF_SYSCALL_EMU > > > flag

Re: [GIT PULL] PCI fixes for v5.1

2019-05-02 Thread pr-tracker-bot
The pull request you sent on Thu, 2 May 2019 08:55:38 -0500: > git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git > tags/pci-v5.1-fixes-3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/b7a5b22b05472704ca3e891a3a3c7769c057413a Thank you! -- Deet-doot-dot,

Re: [GIT PULL] MTD fixes for 5.1 final

2019-05-02 Thread pr-tracker-bot
The pull request you sent on Thu, 2 May 2019 10:54:06 +0200 (CEST): > git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git > tags/mtd/fixes-for-5.1-rc6 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/e2a4b102d48be7f6055e0e70696ab243ee791e51 Thank you! -- Deet

Re: [RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

2019-05-02 Thread Peter Zijlstra
On Wed, May 01, 2019 at 11:24:12PM -0400, Steven Rostedt wrote: > On Wed, 01 May 2019 16:28:31 -0400 > Steven Rostedt wrote: > > > diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S > > index d309f30cf7af..50bbf4035baf 100644 > > --- a/arch/x86/entry/entry_32.S > > +++ b/arch/x86/

Re: [PATCH] mm/hmm: add ARCH_HAS_HMM_MIRROR ARCH_HAS_HMM_DEVICE Kconfig

2019-05-02 Thread Jerome Glisse
On Wed, May 01, 2019 at 12:23:58PM -0700, Guenter Roeck wrote: > On Wed, May 01, 2019 at 02:38:51PM -0400, Jerome Glisse wrote: > > Andrew just the patch that would be nice to get in 5.2 so i can fix > > device driver Kconfig before doing the real update to mm HMM Kconfig > > > > On Wed, Apr 17, 2

Re: [PATCH net] cls_matchall: avoid panic when receiving a packet before filter set

2019-05-02 Thread Cong Wang
On Thu, May 2, 2019 at 1:55 AM Matteo Croce wrote: > > On Thu, May 2, 2019 at 10:51 AM Matteo Croce wrote: > > > > When a matchall classifier is added, there is a small time interval in > > which tp->root is NULL. If we receive a packet in this small time slice > > a NULL pointer dereference will

Re: [PATCH] kasan: Zero initialize tag in __kasan_kmalloc

2019-05-02 Thread Andrey Konovalov
On Thu, May 2, 2019 at 5:36 PM Nathan Chancellor wrote: > > When building with -Wuninitialized and CONFIG_KASAN_SW_TAGS unset, Clang > warns: > > mm/kasan/common.c:484:40: warning: variable 'tag' is uninitialized when > used here [-Wuninitialized] > kasan_unpoison_shadow(set_tag(object, ta

Re: [PATCH] kexec_buffer measure

2019-05-02 Thread Casey Schaufler
On 5/2/2019 8:48 AM, Mimi Zohar wrote: [Cc'ing Paul, John, Casey] On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote: [Cc'ing LSM mailing list] On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote: 2) Adding a LSM hook We are doing both the command line and kernel version measurement

Re: [PATCH] kexec_buffer measure

2019-05-02 Thread Casey Schaufler
On 5/2/2019 8:48 AM, Mimi Zohar wrote: [Cc'ing Paul, John, Casey] On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote: [Cc'ing LSM mailing list] On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote: 2) Adding a LSM hook We are doing both the command line and kernel version measurement

Re: [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export

2019-05-02 Thread Andy Lutomirski
On Thu, May 2, 2019 at 8:41 AM Sebastian Andrzej Siewior wrote: > > On 2019-05-02 07:42:14 [-0700], Andy Lutomirski wrote: > > The FPU is not a super-Linuxy internal detail, so remove the _GPL > > from its export. Without something like this patch, it's impossible > > for even highly license-resp

Re: [RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

2019-05-02 Thread Peter Zijlstra
On Thu, May 02, 2019 at 06:21:33PM +0200, Peter Zijlstra wrote: > Much thanks to Joerg Roedel for talking entry_32.S with me. > > TL;DR, on x86_32 kernel->kernel IRET frames are only 3 entries and do > not include ESP/SS, so not only wasn't regs->sp setup, if you changed it > it wouldn't be effect

[PATCH v2] kasan: Initialize tag to 0xff in __kasan_kmalloc

2019-05-02 Thread Nathan Chancellor
When building with -Wuninitialized and CONFIG_KASAN_SW_TAGS unset, Clang warns: mm/kasan/common.c:484:40: warning: variable 'tag' is uninitialized when used here [-Wuninitialized] kasan_unpoison_shadow(set_tag(object, tag), size); ^~~ set_tag

Re: [PATCH] x86/entry/64: randomize kernel stack offset upon syscall

2019-05-02 Thread Andy Lutomirski
On Thu, May 2, 2019 at 8:09 AM Ingo Molnar wrote: > > > * Andy Lutomirski wrote: > > > Or we decide that calling get_random_bytes() is okay with IRQs off and > > this all gets a bit simpler. > > BTW., before we go down this path any further, is the plan to bind this > feature to a real CPU-RNG ca

RE: [PATCH] x86/entry/64: randomize kernel stack offset upon syscall

2019-05-02 Thread David Laight
From: Ingo Molnar > Sent: 02 May 2019 16:09 > * Andy Lutomirski wrote: > > > Or we decide that calling get_random_bytes() is okay with IRQs off and > > this all gets a bit simpler. > > BTW., before we go down this path any further, is the plan to bind this > feature to a real CPU-RNG capability,

Re: [PATCH v2] kasan: Initialize tag to 0xff in __kasan_kmalloc

2019-05-02 Thread Andrey Konovalov
On Thu, May 2, 2019 at 6:31 PM Nathan Chancellor wrote: > > When building with -Wuninitialized and CONFIG_KASAN_SW_TAGS unset, Clang > warns: > > mm/kasan/common.c:484:40: warning: variable 'tag' is uninitialized when > used here [-Wuninitialized] > kasan_unpoison_shadow(set_tag(object, ta

Re: [PATCH] edac: sifive: Add EDAC platform driver for SiFive SoCs

2019-05-02 Thread James Morse
Hi Yash, Sorry for the delay on the earlier version of this - I was trying to work out what happens when multiple edac drivers probe based on DT... On 02/05/2019 12:16, Yash Shah wrote: > The initial ver of EDAC driver supports: > - ECC event monitoring and reporting through the EDAC framework

Re: [PATCH] x86/entry/64: randomize kernel stack offset upon syscall

2019-05-02 Thread Ingo Molnar
* Andy Lutomirski wrote: > > 8 gigabits/sec sounds good throughput in principle, if there's no > > scalability pathologies with that. > > The latency is horrible. Latency would be amortized via batching anyway, so 8 gigabits/sec suggests something on the order of magnitude of 4 bits per cycl

Re: [v1] PCI: mediatek: Remove MSI inner domain

2019-05-02 Thread Lorenzo Pieralisi
On Thu, Jan 31, 2019 at 08:49:57PM +0800, Jianjun Wang wrote: > On Thu, 2019-01-31 at 09:44 +, Marc Zyngier wrote: > > On 31/01/2019 09:19, Honghui Zhang wrote: > > > On Tue, 2019-01-22 at 17:37 +0800, Jianjun Wang wrote: > > >> There is no need to create the inner domain as a parent for MSI do

Re: [PATCH] ARM: multi_v7_defconfig: Enable panic and disk LED triggers

2019-05-02 Thread Amit Kucheria
On Thu, May 2, 2019 at 4:33 PM Manivannan Sadhasivam wrote: > > Most development boards and devices have one or more LEDs. It is > useful during debugging if they can be wired to show different > behaviours such as disk or cpu activity or a load-average dependent > heartbeat. Enable panic and disk

Re: [PATCH] x86/entry/64: randomize kernel stack offset upon syscall

2019-05-02 Thread Ingo Molnar
* David Laight wrote: > It has already been measured - it is far too slow. I don't think proper buffering was tested, was it? Only a per syscall RDRAND overhead which I can imagine being not too good. > > Because calling tens of millions of system calls per second will > > deplete any non-C

Re: [PATCH v3 1/4] ptrace: move clearing of TIF_SYSCALL_EMU flag to core

2019-05-02 Thread Will Deacon
On Thu, May 02, 2019 at 06:13:30PM +0200, Oleg Nesterov wrote: > On 05/01, Sudeep Holla wrote: > > > > On Wed, May 01, 2019 at 06:13:30PM +0200, Oleg Nesterov wrote: > > > On 04/30, Sudeep Holla wrote: > > > > > > > > While the TIF_SYSCALL_EMU is set in ptrace_resume independent of any > > > > arch

Re: [PATCH v3 1/4] added a new ima policy func buffer_check, and ima hook to measure the buffer hash into ima

2019-05-02 Thread Mimi Zohar
On Mon, 2019-04-29 at 14:47 -0700, Prakhar Srivastava wrote: > From: Prakhar Srivastava > > added a new ima policy func buffer_check, and ima hook to > measure the buffer hash into ima logs. When defining a new LSN/IMA hook please conform to the existing naming conventions.  Generally LSM hooks

Re: [PATCH v3 3/4] add kexec_cmdline used to ima

2019-05-02 Thread Mimi Zohar
On Mon, 2019-04-29 at 14:47 -0700, Prakhar Srivastava wrote: > From: Prakhar Srivastava > > prepend the kernel file name to kexec_cmdline > before measuring the buffer. > kexec doesn't really know or care about IMA.  Other than the IMA call, itself, nothing should be added to kexec files.  As

Re: [PATCH v3 2/4] add the buffer to the xattr

2019-05-02 Thread Mimi Zohar
On Mon, 2019-04-29 at 14:47 -0700, Prakhar Srivastava wrote: > From: Prakhar Srivastava > > add the buffer to the xattr for a buffer case Please write full patch descriptions, here and in the other patches, explaining the current status with the motivation for the change. > > Signed-off-by: Pr

Re: [PATCH v3 4/4] added LSM hook to call ima_buffer_check

2019-05-02 Thread Mimi Zohar
On Mon, 2019-04-29 at 14:47 -0700, Prakhar Srivastava wrote: > From: Prakhar Srivastava > > added LSM hook to call ima_buffer_check Casey just responded, "I can imagine an LSM that cares about the command line, but I don't have interest in it for any work I have in progress."  Unless one of the

Re: perf tools build broken after v5.1-rc1

2019-05-02 Thread Vineet Gupta
On 4/29/19 6:18 PM, Arnaldo Carvalho de Melo wrote: >>> >>> Auto-detecting system features: >>> ... dwarf: [ OFF ] >>> ...dwarf_getlocations: [ OFF ] >>> ... glibc: [ on ] >> >> Not related to current issue, this run uses a uClibc toolcha

[PATCH 0/4] coresight: next v5.1-rc7

2019-05-02 Thread Mathieu Poirier
Hi Greg, Please see if you can add these to your tree for the coming merge window. They are confined to the CoreSight subsystem and have been in linux-next for a week now. We can simply wait for the next cycle if you think it is too late for this one. Thanks, Mathieu Leo Yan (4): dt-bindings:

[PATCH 1/4] dt-bindings: arm: coresight: Add new compatible for static replicator

2019-05-02 Thread Mathieu Poirier
From: Leo Yan CoreSight uses below bindings for replicator: Dynamic replicator, aka. configurable replicator: "arm,coresight-dynamic-replicator", "arm,primecell"; Static replicator, aka. non-configurable replicator: "arm,coresight-replicator"; The compatible string "arm,coresight-r

[PATCH 4/4] coresight: funnel: Support static funnel

2019-05-02 Thread Mathieu Poirier
From: Leo Yan Since CoreSight hardware topology can use a 'hidden' funnel in the trace data path, this kind funnel doesn't have register for accessing and is used by default from hardware design perspective. Below is an example for related hardware topology: +--+ +--+ | cpu0 |->| E

[PATCH 2/4] coresight: replicator: Add new device id for static replicator

2019-05-02 Thread Mathieu Poirier
From: Leo Yan This patch adds a device id for the new static replicator compatible string; it changes the driver name from "coresight-replicator" to "coresight-static-replicator" as well. This patch also gives warning when use the replicator obsolete DT binding. Signed-off-by: Leo Yan Reviewed

[PATCH 3/4] dt-bindings: arm: coresight: Unify funnel DT binding

2019-05-02 Thread Mathieu Poirier
From: Leo Yan Following the same fashion with replicator DT binding, this patch is to unify the DT binding for funnel to support static and dynamic modes; finally we get the funnel DT binding as below: Before patch: Static funnel, aka. non-configurable funnel: Not supported; Dynamic fu

Re: [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export

2019-05-02 Thread Borislav Petkov
On Thu, May 02, 2019 at 09:29:01AM -0700, Andy Lutomirski wrote: > I'm not saying that we should export things for ZFS's benefit. But, > as far as I know, _GPL means "this interface is sufficiently specific > to Linux details that we think that any user must be a derived work". > I don't think tha

Hallo 5/2/2019 4:06:09 PM

2019-05-02 Thread Stefanie Hubner
Hallo linux-kernel@vger.kernel.org Sehr geehrte Damen und Herren Wir gewähren Darlehen in Höhe von 20.000,00 € bis 5 Mio. € mit einem Zinssatz von 2% Die Zinsen und die Laufzeiten sind sehr attraktiv (2%) und in punkto Sicherheit beschränken wir uns auf das absolute Minimum. Interessiert? Da

[PATCH] posix_acl: Use struct_size() helper

2019-05-02 Thread Gustavo A. R. Silva
Make use of the struct_size() helper instead of an open-coded version in order to avoid any potential type mistakes, in particular in the context in which this code is being used. So, replace code of the following form: sizeof(struct posix_acl) + count * sizeof(struct posix_acl_entry) with: str

Re: [PATCH v3 3/4] add kexec_cmdline used to ima

2019-05-02 Thread Al Viro
On Thu, May 02, 2019 at 12:52:35PM -0400, Mimi Zohar wrote: > On Mon, 2019-04-29 at 14:47 -0700, Prakhar Srivastava wrote: > > From: Prakhar Srivastava > kexec doesn't really know or care about IMA.  Other than the IMA call, > itself, nothing should be added to kexec files.  As mentioned in 1/4,

Re: [PATCH V2 2/2] PCI: dwc: Export APIs to support .remove() implementation

2019-05-02 Thread Vidya Sagar
On 5/2/2019 8:21 PM, Lorenzo Pieralisi wrote: On Tue, Apr 16, 2019 at 07:45:16PM +0530, Vidya Sagar wrote: Export all configuration space access APIs and also other APIs to support host controller drivers of DesignWare core based implementations while adding support for .remove() hook to build t

Re: [PATCH V2 1/2] PCI: dwc: Add API support to de-initialize host

2019-05-02 Thread Vidya Sagar
On 5/2/2019 8:28 PM, Lorenzo Pieralisi wrote: On Tue, Apr 16, 2019 at 07:45:15PM +0530, Vidya Sagar wrote: Add an API to group all the tasks to be done to de-initialize host which can then be called by any DesignWare core based driver implementations while adding .remove() support in their respe

[PATCH V4 2/2] PCI: dwc: Export APIs to support .remove() implementation

2019-05-02 Thread Vidya Sagar
Export all configuration space access APIs and also other APIs to support host controller drivers of DesignWare core based implementations while adding support for .remove() hook to build their respective drivers as modules Signed-off-by: Vidya Sagar Acked-by: Gustavo Pimentel --- Changes from v

[PATCH V4 1/2] PCI: dwc: Add API support to de-initialize host

2019-05-02 Thread Vidya Sagar
Add an API to group all the tasks to be done to de-initialize host which can then be called by any DesignWare core based driver implementations while adding .remove() support in their respective drivers. Signed-off-by: Vidya Sagar Acked-by: Gustavo Pimentel --- Changes from v3: * Added check if

[PATCH v2] x86/fpu: Fault-in user stack if copy_fpstate_to_sigframe() fails

2019-05-02 Thread Sebastian Andrzej Siewior
In the compacted form, XSAVES may save only the XMM+SSE state but skip FP (x87 state). This is denoted by header->xfeatures = 6. The fastpath (copy_fpregs_to_sigframe()) does that but _also_ initialises the FP state (cwd to 0x37f, mxcsr as we do, remaining fields to 0). The slowpath (copy_xstate_

Re: [PATCH 0/4] coresight: next v5.1-rc7

2019-05-02 Thread Greg KH
On Thu, May 02, 2019 at 10:54:01AM -0600, Mathieu Poirier wrote: > Hi Greg, > > Please see if you can add these to your tree for the coming merge window. > They are confined to the CoreSight subsystem and have been in linux-next for > a week now. > > We can simply wait for the next cycle if you t

Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir

2019-05-02 Thread J. Bruce Fields
On Thu, May 02, 2019 at 05:08:14PM +0200, Andreas Grünbacher wrote: > You'll still see permissions that differ from what the filesystem > enforces, and copy-up would change that behavior. That's always true, and this issue isn't really specific to NFSv4 ACLs (or ACLs at all), it already exists wit

Re: [PATCH V3 02/12] misc: xilinx-sdfec: add core driver

2019-05-02 Thread Greg KH
On Sat, Apr 27, 2019 at 11:04:56PM +0100, Dragan Cvetic wrote: > +#define DRIVER_NAME "xilinx_sdfec" > +#define DRIVER_VERSION "0.3" Version means nothing with the driver in the kernel tree, please remove it. > +#define DRIVER_MAX_DEV BIT(MINORBITS) Why this number? Why limit yourself to any nu

Re: [PATCH V3 04/12] misc: xilinx_sdfec: Add open, close and ioctl

2019-05-02 Thread Greg KH
On Sat, Apr 27, 2019 at 11:04:58PM +0100, Dragan Cvetic wrote: > +static int xsdfec_dev_open(struct inode *iptr, struct file *fptr) > +{ > + struct xsdfec_dev *xsdfec; > + > + xsdfec = container_of(iptr->i_cdev, struct xsdfec_dev, xsdfec_cdev); > + > + if (!atomic_dec_and_test(&xsdfec->

Re: [PATCH V3 04/12] misc: xilinx_sdfec: Add open, close and ioctl

2019-05-02 Thread Greg KH
On Sat, Apr 27, 2019 at 11:04:58PM +0100, Dragan Cvetic wrote: > Add char device interface per DT node present and support > file operations: > - open(), > - close(), > - unlocked_ioctl(), > - compat_ioctl(). Why do you need compat_ioctl() at all? Any "new" driver should never need it. Just crea

Re: [PATCH V3 07/12] misc: xilinx_sdfec: Add ability to configure LDPC

2019-05-02 Thread Greg KH
On Sat, Apr 27, 2019 at 11:05:01PM +0100, Dragan Cvetic wrote: > --- a/include/uapi/misc/xilinx_sdfec.h > +++ b/include/uapi/misc/xilinx_sdfec.h > +/** > + * xsdfec_calculate_shared_ldpc_table_entry_size - Calculates shared code > + * table sizes. > + * @ldpc: Pointer to the LPDC Code Parameters

[PATCH] MAINTAINERS: update git tree for sound entries

2019-05-02 Thread Ross Zwisler
Several sound related entries in MAINTAINERS refer to the old git tree at "git://git.alsa-project.org/alsa-kernel.git". This is no longer used for development, and Takashi Iwai's kernel.org tree is used instead. Signed-off-by: Ross Zwisler --- MAINTAINERS | 13 ++--- 1 file changed, 6 i

hello dear

2019-05-02 Thread Aysha Gadafi
Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh, hello dear I came across your contact during my private search. Mrs Aisha Al- Qaddafi is my name, the only daughter of late Libyan president, am a single Mother and a Widow with three Children.I have funds the sum of $27.5 million USD for, investme

hello dear

2019-05-02 Thread Aysha Gadafi
Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh, hello dear I came across your contact during my private search. Mrs Aisha Al- Qaddafi is my name, the only daughter of late Libyan president, am a single Mother and a Widow with three Children.I have funds the sum of $27.5 million USD for, investme

Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir

2019-05-02 Thread Goetz, Patrick G
On 5/1/19 10:57 PM, NeilBrown wrote: > Support some day support for nfs4 acls were added to ext4 (not a totally > ridiculous suggestion). We would then want NFS to allow it's ACLs to be > copied up. Is there some reason why there hasn't been a greater effort to add NFSv4 ACL support to the main

[PATCH v8 1/4] s390: ap: kvm: add PQAP interception for AQIC

2019-05-02 Thread Pierre Morel
We prepare the interception of the PQAP/AQIC instruction for the case the AQIC facility is enabled in the guest. First of all we do not want to change existing behavior when intercepting AP instructions without the SIE allowing the guest to use AP instructions. In this patch we only handle the AQ

[PATCH v8 2/4] vfio: ap: register IOMMU VFIO notifier

2019-05-02 Thread Pierre Morel
To be able to use the VFIO interface to facilitate the mediated device memory pinning/unpinning we need to register a notifier for IOMMU. While we will start to pin one guest page for the interrupt indicator byte, this is still ok with ballooning as this page will never be used by the guest virtio

[PATCH v8 3/4] s390: ap: implement PAPQ AQIC interception in kernel

2019-05-02 Thread Pierre Morel
We register a AP PQAP instruction hook during the open of the mediated device. And unregister it on release. During the probe of the AP device, we allocate a vfio_ap_queue structure to keep track of the information we need for the PQAP/AQIC instruction interception. In the AP PQAP instruction hoo

<    1   2   3   4   5   6   7   8   9   >