[PATCH v4 0/7] Introduce on-chip interconnect API

Modern SoCs have multiple processors and various dedicated cores (video, gpu, graphics, modem). These cores are talking to each other and can generate a lot of data flowing through the on-chip interconnects. These interconnect buses could form different topologies such as crossbar, point to point

Re: [PATCH] f2fs: avoid selinux denial on CAP_SYS_RESOURCE

On 03/09, Chao Yu wrote: > On 2018/3/9 12:49, Jaegeuk Kim wrote: > > This fixes CAP_SYS_RESOURCE denial of selinux when using resgid. > > A little confusion, if capable(CAP_SYS_RESOURCE) is false, we still have > chance > to return true for below resuid & resgid cases, right? I didn't dig it

[PATCH v5 17/36] drm/bridge: analogix_dp: Fix AUX_PD bit for Rockchip

From: zain wang There are some different bits between Rockchip and Exynos in register "AUX_PD". This patch fixes the incorrect operations about it. Cc: Douglas Anderson Signed-off-by: zain wang Signed-off-by: Sean Paul

Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0

Em Fri, Mar 09, 2018 at 03:00:40PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: > > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo > > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > > @@ -13,5 +13,5 @@ > >

Applied "ASoC: uniphier: add support for UniPhier PXs2 AIO" to the asoc tree

The patch ASoC: uniphier: add support for UniPhier PXs2 AIO has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: da7219: Add common clock usage for providing DAI clks" to the asoc tree

The patch ASoC: da7219: Add common clock usage for providing DAI clks has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: 88pg86x: add DT bindings document" to the regulator tree

The patch regulator: 88pg86x: add DT bindings document has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "ASoC: TSCS42xx: Add missing headers" to the asoc tree

The patch ASoC: TSCS42xx: Add missing headers has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "regulator: 88pg86x: new i2c dual regulator chip" to the regulator tree

The patch regulator: 88pg86x: new i2c dual regulator chip has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: [PATCH] perf tools arm64: Add libdw DWARF post unwind support for ARM64

On Fri, 9 Mar 2018 12:06:27 -0300 Arnaldo Carvalho de Melo wrote: Hi Arnaldo, > Em Thu, Mar 08, 2018 at 09:10:30PM -0600, Kim Phillips escreveu: > > Based on prior work: > > > > https://lkml.org/lkml/2014/5/6/395 > > Thanks, looks good, applying. > > Jean, is everything ok

Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0

On Fri, Mar 9, 2018 at 11:32 PM, Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 09, 2018 at 03:00:40PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: >> > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho

Re: [RFC PATCH 1/2] riscv/spinlock: Strengthen implementations with fences

On Fri, 09 Mar 2018 04:16:43 PST (-0800), parri.and...@gmail.com wrote: On Thu, Mar 08, 2018 at 02:11:12PM -0800, Palmer Dabbelt wrote: On Thu, 08 Mar 2018 13:03:03 PST (-0800), parri.and...@gmail.com wrote: >On Wed, Mar 07, 2018 at 10:33:49AM -0800, Palmer Dabbelt wrote: > >[...] > >>I'm going

Re: x86 performance monitor counters save/restore on context switch

On Fri, 9 Mar 2018 02:29:55 -0500 Will Hawkins wrote: > Mr. Rostedt and others interested reading on the LKML, > > I hope that this is the proper venue to ask this (longwinded) > question. If it is not, I apologize for the SPAM and wasting > everyone's time and bits. I am

Re: [PATCH] staging: vchiq_arm: Clear VLA warning

"Tobin C. Harding" writes: > The kernel would like to have all stack VLA usage removed[1]. The > array here is fixed (declared with a const variable) but it appears > like VLA to the compiler. We can use a pre-processor define to quiet > the compiler. > > [1]:

Re: [RFC 3/3] arch/x86/kvm: SVM: Introduce pause loop exit logic in SVM

2018-03-02 11:17-0500, Babu Moger: > Bring the PLE(pause loop exit) logic to AMD svm driver. > We have noticed it help in situations where numerous pauses are generated > due to spinlock or other scenarios. Tested it with idle=poll and noticed > pause interceptions go down considerably. > >

Re: [PATCH net-next] modules: allow modprobe load regular elf binaries

On Fri, Mar 09, 2018 at 09:32:36AM -0800, Alexei Starovoitov wrote: > On 3/9/18 8:24 AM, Andy Lutomirski wrote: > > On Fri, Mar 9, 2018 at 3:39 PM, Alexei Starovoitov wrote: > > > On 3/9/18 7:16 AM, Andy Lutomirski wrote: > > > > > > > > > > > > On Mar 8, 2018, at 9:08 PM, Alexei

Re: [PATCH v4] cpuset: Enable cpuset controller in default hierarchy

On Fri, 2018-03-09 at 12:45 -0500, Waiman Long wrote: > On 03/09/2018 11:34 AM, Mike Galbraith wrote: > > On Fri, 2018-03-09 at 10:35 -0500, Waiman Long wrote: > >> Given the fact that thread mode had been merged into 4.14, it is now > >> time to enable cpuset to be used in the default hierarchy

Re: [PATCH net-next] modules: allow modprobe load regular elf binaries

On Thu, Mar 8, 2018 at 9:08 PM, Alexei Starovoitov wrote: > > there is not abi breakage and file cannot disappear from running task. > One cannot umount fs while file is still being used. I think that "cannot umount" part _is_ the ABI breakage that Andy is talking about. > Not only

Re: [PATCH v4] cpuset: Enable cpuset controller in default hierarchy

On 03/09/2018 01:17 PM, Mike Galbraith wrote: > On Fri, 2018-03-09 at 12:45 -0500, Waiman Long wrote: >> On 03/09/2018 11:34 AM, Mike Galbraith wrote: >>> On Fri, 2018-03-09 at 10:35 -0500, Waiman Long wrote: Given the fact that thread mode had been merged into 4.14, it is now time to

Re: [PATCH net-next] modules: allow modprobe load regular elf binaries

> On Mar 9, 2018, at 10:15 AM, Greg KH wrote: > > > Oh, and for the record, I like Andy's proposal as well as dumping this > into a kernel module "blob" with the exception that this now would take > up unswapable memory, which isn't the nicest and is one big

Re: [PATCH] perf tools arm64: Add libdw DWARF post unwind support for ARM64

Em Fri, Mar 09, 2018 at 12:07:20PM -0600, Kim Phillips escreveu: > On Fri, 9 Mar 2018 12:06:27 -0300 > Arnaldo Carvalho de Melo wrote: > > Hi Arnaldo, > > > Em Thu, Mar 08, 2018 at 09:10:30PM -0600, Kim Phillips escreveu: > > > Based on prior work: > > > > > >

Re: [PATCH] clk: clk-fixed-factor: Use new macro CLK_OF_DECLARE_DRIVER

Quoting Rajan Vaja (2018-03-08 06:15:00) > Fixed factor clock has two initialization at of_clk_init() > time and also during platform driver probe. So declare the > fixed factor clock with CLK_OF_DECLARE_DRIVER instead of > CLK_OF_DECLARE. > > See below commit for reference: > "clk: sunxi: apb0:

[PATCH v2] power: supply: da9150-fg: remove VLA usage

In preparation to enabling -Wvla, remove VLA usage and replace it with fixed-length arrays. DA9150_QIF_LONG_SIZE (4 bytes) is the biggest size of an attribute which can be accessed [1]. Fixed as part of the directive to remove all VLAs from the kernel: https://lkml.org/lkml/2018/3/7/621 [1]

[GIT PULL] xen: fix for V4.16-rc5

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.16a-rc5-tag xen: fix for V4.16-rc5 It contains just one fix for the correct error handling after a negative rc from device_register(). Thanks. Juergen

RE: [PATCH 5/6] dma-mapping: support fsl-mc bus

> -Original Message- > From: Christoph Hellwig [mailto:h...@lst.de] > Sent: Thursday, March 08, 2018 13:11 > > On Tue, Mar 06, 2018 at 04:41:56AM +, Nipun Gupta wrote: > > Sorry for asking a trivial question - looking into dma_configure() I see > > that > > PCI is used in the start

Re: [PATCH net-next] modules: allow modprobe load regular elf binaries

On Fri, Mar 09, 2018 at 10:23:27AM -0800, Andy Lutomirski wrote: > > > > On Mar 9, 2018, at 10:15 AM, Greg KH wrote: > > > > > > > Oh, and for the record, I like Andy's proposal as well as dumping this > > into a kernel module "blob" with the exception that this

Re: [PATCH] pktgen: Remove VLA usage

On 03/09/2018 10:58 AM, David Miller wrote: From: "Gustavo A. R. Silva" Date: Thu, 8 Mar 2018 23:43:40 -0600 In preparation to enabling -Wvla, remove VLA usage and replace it with a fixed-length array instead. Signed-off-by: Gustavo A. R. Silva

Re: [PATCH net-next] modules: allow modprobe load regular elf binaries

From: Linus Torvalds Date: Fri, 9 Mar 2018 10:17:42 -0800 > - use deny_write_access() to make sure that we don't have active > writers and cannot get them during the execve. I agree that this is necessary for image validation purposes.

Re: [PATCH] net: ipv6: xfrm6_state: remove VLA usage

Hello! On 03/09/2018 03:21 PM, Andreas Christoforou wrote: > The kernel would like to have all stack VLA usage removed[1]. > > Signed-off-by: Andreas Christoforou > --- > net/ipv6/xfrm6_state.c | 8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) > >

Re: [PATCH] staging: vchiq_arm: Clear VLA warning

On Fri, Mar 9, 2018 at 10:11 AM, Eric Anholt wrote: > "Tobin C. Harding" writes: > >> The kernel would like to have all stack VLA usage removed[1]. The >> array here is fixed (declared with a const variable) but it appears >> like VLA to the compiler. We can use

Re: [PATCH v2 2/2] riscv/atomic: Strengthen implementations with fences

On Fri, Mar 09, 2018 at 09:56:21AM -0800, Palmer Dabbelt wrote: > On Fri, 09 Mar 2018 04:13:40 PST (-0800), parri.and...@gmail.com wrote: > >Atomics present the same issue with locking: release and acquire > >variants need to be strengthened to meet the constraints defined > >by the Linux-kernel

Re: [PATCH net-next] hv_netvsc: Correct filter setting for multicast/broadcast

Hello! On 03/09/2018 04:25 PM, Mohammed Gamal wrote: > Commit 009f766 intended to filter multicast/broadcast, however At least 12 digits needed here, and the summary line too, just like you do for the Fixes: tag. > the NDIS filter wasn't set properly in non-promiscuous modes, > which

[PATCH v2] mm: make start_isolate_page_range() fail if already isolated

start_isolate_page_range() is used to set the migrate type of a set of pageblocks to MIGRATE_ISOLATE while attempting to start a migration operation. It assumes that only one thread is calling it for the specified range. This routine is used by CMA, memory hotplug and gigantic huge pages. Each

Re: [PATCH] device_handler: remove VLAs

On Fri, 2018-03-09 at 23:32 +0100, Stephen Kitt wrote: > In preparation to enabling -Wvla, remove VLAs and replace them with > fixed-length arrays instead. > > scsi_dh_{alua,emc,rdac} use variable-length array declarations to > store command blocks, with the appropriate size as determined by >

Re: WARNING in __proc_create

On Fri, Mar 9, 2018 at 1:59 PM, syzbot wrote: > Hello, > > syzbot hit the following crash on net-next commit > 617aebe6a97efa539cc4b8a52adccd89596e6be0 (Sun Feb 4 00:25:42 2018 +) > Merge tag 'usercopy-v4.16-rc1' of >

Re: Make set_handle_irq and handle_arch_irq generic, v3

On Fri, 9 Mar 2018, Palmer Dabbelt wrote: > On Fri, 09 Mar 2018 02:20:12 PST (-0800), t...@linutronix.de wrote: > > This looks sensible. We have two options for getting this merged: > > > > 1) I'll take the whole lot through tip/irq/core > > > > 2) I'll apply patch 1/N to a special branch in

Re: Nokia N900: v4.16-rc4: oops in iio when grepping sysfs

Hi! > > Hmm. Looks like there's a lot of fun to be had with sysfs. > > > > > > pavel@n900:~$ uname -a > > Linux n900 4.16.0-rc4-59690-g7f84626-dirty #543 Thu Mar 8 19:53:30 CET > > 2018 armv7l GNU/Linux > > > > [ 306.402496] bq2415x: command Timer reset > > [ 312.761322] adp1653 2-0030: Read

Re: [PATCH v6 2/6] regulator: bindings: Add properties for coupled regulators

On Fri, Mar 09, 2018 at 01:22:04PM +0100, Maciej Purski wrote: > Some regulators require keeping their voltage spread below defined > max_spread. > > Add properties to provide information on regulators' coupling. > > Signed-off-by: Maciej Purski > --- >

Re: WARNING in __proc_create

Eric Dumazet wrote: > >>fs/proc/generic.c:354 > > > >We need to reject empty names. > > > > I sent a patch a while back, but Pablo/Florian wanted more than that simple > fix. > > We also need to filter special characters like '/' > > Or maybe I am mixing with something

Re: WARNING in __proc_create

On Fri, Mar 9, 2018 at 2:58 PM, Eric Dumazet wrote: > > > On 03/09/2018 02:56 PM, Eric Dumazet wrote: > >> >> I sent a patch a while back, but Pablo/Florian wanted more than that >> simple fix. >> >> We also need to filter special characters like '/' proc_create_data()

[PATCH v4 10/10] drivers: qcom: rpmh-rsc: allow active requests from wake TCS

Some RSCs may only have sleep and wake TCS, i.e, there is no dedicated TCS for active mode request, but drivers may still want to make active requests from these RSCs. In such cases re-purpose the wake TCS to send active state requests. The requirement for this is that the driver is aware that

[PATCH v4 05/10] drivers: qcom: rpmh-rsc: write sleep/wake requests to TCS

Sleep and wake requests are sent when the application processor subsystem of the SoC is entering deep sleep states like in suspend. These requests help lower the system power requirements when the resources are not in use. Sleep and wake requests are written to the TCS slots but are not triggered

[PATCH v4 08/10] drivers: qcom: rpmh: allow requests to be sent asynchronously

Platform drivers that want to send a request but do not want to block until the RPMH request completes have now a new API - rpmh_write_async(). The API allocates memory and send the requests and returns the control back to the platform driver. The tx_done callback from the controller is handled

[PATCH v4 09/10] drivers: qcom: rpmh: add support for batch RPMH request

Platform drivers need make a lot of resource state requests at the same time, say, at the start or end of an usecase. It can be quite inefficient to send each request separately. Instead they can give the RPMH library a batch of requests to be sent and wait on the whole transaction to be complete.

Re: [PATCH v2 2/2] dt-bindings: backlight: Add binding for RAVE SP backlight driver

On Thu, Mar 08, 2018 at 11:20:46AM -0800, Andrey Smirnov wrote: > Add Device Tree bindings for RAVE SP backlight driver - an MFD cell of > parent RAVE SP driver (documented in > Documentation/devicetree/bindings/mfd/zii,rave-sp.txt). > > Cc: Lee Jones > Cc: Daniel Thompson

Re: [PATCH v2 02/12] clk: stm32mp1: Introduce STM32MP1 clock driver

On Thu, Mar 08, 2018 at 05:53:55PM +0100, gabriel.fernan...@st.com wrote: > From: Gabriel Fernandez > > This patch introduces the mechanism to probe stm32mp1 driver. > It also defines registers definition. > This patch also introduces the generic mechanism to register >

[PATCH 4/4] gpio: Remove VLA from stmpe driver

The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) This patch replaces a VLA with an appropriate call to kmalloc_array. Signed-off-by: Laura Abbott --- drivers/gpio/gpio-stmpe.c | 7 ++- 1 file changed, 6 insertions(+), 1

[PATCH 0/4] VLA removal from the GPIO subsystem

Hi, For those who haven't seen it, there's an effort to remove VLAs from the kernel so we can turn on -Wvla in the name of security. See https://lkml.org/lkml/2018/3/7/621 for more details and discussion. This is a series to remove a few VLAs from the gpio subsystem. These are compile tested

[PATCH 3/4] gpio: Remove VLA from xra1403 driver

The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) This patch replaces a VLA with an appropriate call to kmalloc_array. Signed-off-by: Laura Abbott --- drivers/gpio/gpio-xra1403.c | 8 +++- 1 file changed, 7 insertions(+), 1

[PATCH] proc: reject "." and ".." as filenames

Various subsystems can create files and directories in /proc with names directly controlled by userspace. Which means "/", "." and ".." are no-no. "/" split is already taken care of, do the other 2 prohibited names. Signed-off-by: Alexey Dobriyan --- fs/proc/generic.c |

[PATCH 2/4] gpio: Remove VLA from MAX3191X driver

The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) This patch replaces several a VLA with an appropriate call to kmalloc_array. Signed-off-by: Laura Abbott --- drivers/gpio/gpio-max3191x.c | 7 ++- 1 file changed, 6

mmotm 2018-03-09-16-34 uploaded

The mm-of-the-moment snapshot 2018-03-09-16-34 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH 4.9 42/65] sctp: fix dst refcnt leak in sctp_v4_get_dst

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tommi Rantala [ Upstream commit 4a31a6b19f9ddf498c81f5c9b089742b7472a6f8 ] Fix dst reference count leak in sctp_v4_get_dst() introduced in commit 410f03831 ("sctp:

RE: [PATCH V2 2/3] efi: Introduce efi_rts_workqueue and some infrastructure to invoke all efi_runtime_services()

> > That's true! AFAIK, we don't have any issues handling NMI while in efi_pgd. > > We might have issues only when, we are already in efi_pgd, NMI comes > > along > > Can you trigger this? Or is it something hypothetical? > AFAIK, it's hypothetical. I did try to trigger the issue, but failed

[PATCH 4.9 49/65] s390/qeth: fix underestimated count of buffer elements

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit 89271c65edd599207dd982007900506283c90ae3 ] For a memory range/skb where the last byte falls onto a page boundary (ie. 'end' is of the

[PATCH 4.9 24/65] PCI/ASPM: Deal with missing root ports in link state handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit ee8bdfb6568d86bb93f55f8d99c4c643e77304ee upstream. Even though it is unconventional, some PCIe host implementations omit the root ports

[PATCH 4.9 45/65] tcp: Honor the eor bit in tcp_mtu_probe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Lesokhin [ Upstream commit 808cf9e38cd7923036a99f459ccc8cf2955e47af ] Avoid SKB coalescing if eor bit is set in one of the relevant SKBs. Fixes: c134ecb87817 ("tcp:

[PATCH] x86/microcode/AMD: check microcode file sanity before loading it

Currently, it is very easy to make the AMD microcode update driver crash or spin on a malformed microcode file since it does very little consistency checking on data loaded from such file. This commit introduces various checks, mostly on length-type fields, so all corrupted microcode files are

[PATCH 4.9 41/65] udplite: fix partial checksum initialization

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 15f35d49c93f4fa9875235e7bf3e3783d2dd7a1b ] Since UDP-Lite is always using checksum, the following path is triggered when

[PATCH 4.9 44/65] net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 08f5138512180a479ce6b9d23b825c9f4cd3be77 ] This condition wasn't adjusted when PHY_IGNORE_INTERRUPT (-2) was added long ago. In case of

Re: [PATCH] staging: lustre: o2iblnd: fix race at kiblnd_connect_peer

Please ignore this patch. Turns out it depends on a series which has not been submitted yet. I’ll resend this one once all of those are done. Doug > On Mar 9, 2018, at 3:29 PM, Doug Oucharek wrote: > > cmid will be destroyed at OFED if kiblnd_cm_callback return error. > if

[PATCH 4.4 01/36] tpm: st33zp24: fix potential buffer overruns caused by bit glitches on the bus

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Boone commit 6d24cd186d9fead3722108dec1b1c993354645ff upstream. Discrete TPMs are often connected over slow serial buses which, on some platforms, can have

[PATCH 3.18 21/21] dm io: fix duplicate bio completion due to missing ref count

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit feb7695fe9fb83084aa29de0094774f4c9d4c9fc upstream. If only a subset of the devices associated with multiple regions support a given special operation

[PATCH 3.18 18/21] sctp: verify size of a new chunk in _sctp_make_chunk()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 07f2c7ab6f8d0a7e7c5764c4e6cc9c52951b9d9c ] When SCTP makes INIT or INIT_ACK packet the total chunk length can exceed

[PATCH 3.18 19/21] net: ipv4: dont allow setting net.ipv4.route.min_pmtu below 68

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit c7272c2f1229125f74f22dcdd59de9bbd804f1c8 ] According to RFC 1191 sections 3 and 4, ICMP frag-needed messages indicating an MTU below

[PATCH 3.18 20/21] fib_semantics: Dont match route with mismatching tclassid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit a8c6db1dfd1b1d18359241372bb204054f2c3174 ] In fib_nh_match(), if output interface or gateway are passed in the FIB configuration, we

[PATCH 4.4 14/36] x86/apic/vector: Handle legacy irq data correctly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner The backport of upstream commit 45d55e7bac40 ("x86/apic/vector: Fix off by one in error path") missed to fixup the legacy interrupt data which is not longer

[PATCH 4.4 11/36] x86/syscall: Sanitize syscall table de-references under speculation fix

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby In 4.4.118, we have commit c8961332d6da (x86/syscall: Sanitize syscall table de-references under speculation), which is a backport of upstream commit 2fbd7af5af86.

[PATCH 4.4 12/36] btrfs: Dont clear SGID when inheriting ACLs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit b7f8a09f8097db776b8d160862540e4fc1f51296 upstream. When new directory 'DIR1' is created in a directory 'DIR0' with SGID bit set, DIR1 is expected to have SGID bit

[PATCH 3.18 12/21] netlink: ensure to loop over all netns in genlmsg_multicast_allns()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Dichtel [ Upstream commit cb9f7a9a5c96a773bbc9c70660dc600cfff82f82 ] Nowadays, nlmsg_multicast() returns only 0 or -ESRCH but this was not the case when

Re: [PATCH v3] kernel.h: Skip single-eval logic on literals in min()/max()

On Fri, Mar 9, 2018 at 5:30 PM, Kees Cook wrote: > -- > Kees Cook > Pixel SecurityOn > [...] WTF, gmail just blasted HTML into my explicitly plain-text email?! Apologies... -- Kees Cook Pixel SecurityOn Fri, Mar 9, 2018 at 5:30 PM, Kees Cook mailto:keesc...@chromium.org;

Re: [PATCH] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

On 03/09/2018 04:28 PM, Jiandi An wrote: On 03/08/2018 03:08 PM, miny...@acm.org wrote: From: Corey Minyard The IPMI spec states:    The purpose of the SPMI Table is to provide a mechanism that can    be used by the OSPM (an ACPI term for “OS Operating System-directed  

[PATCH 1/2] watchdog: dw: RMW the control register

RK3399 has rst_pulse_length in CONTROL_REG[4:2], determining the length of pulse to issue for system reset. We shouldn't clobber this value, because that might make the system reset ineffective. On RK3399, we're seeing that a value of 000b (meaning 2 cycles) yields an unreliable (partial?) reset,

[PATCH 2/2] watchdog: dw: save/restore control and timeout across suspend/resume

Some platforms lose this state in suspend. It should be safe to do this unconditionally. Signed-off-by: Brian Norris --- drivers/watchdog/dw_wdt.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/watchdog/dw_wdt.c b/drivers/watchdog/dw_wdt.c index

Re: [PATCH 1/2] watchdog: dw: RMW the control register

Hi Brian, On 03/09/2018 06:44 PM, Brian Norris wrote: RK3399 has rst_pulse_length in CONTROL_REG[4:2], determining the length of pulse to issue for system reset. We shouldn't clobber this value, because that might make the system reset ineffective. On RK3399, we're seeing that a value of 000b

Re: [PATCH v2 1/2] watchdog: dw: RMW the control register

On 03/09/2018 07:46 PM, Brian Norris wrote: RK3399 has rst_pulse_length in CONTROL_REG[4:2], determining the length of pulse to issue for system reset. We shouldn't clobber this value, because that might make the system reset ineffective. On RK3399, we're seeing that a value of 000b (meaning 2

Re: [PATCH 1/2] watchdog: dw: RMW the control register

Hi Brian, On 03/09/2018 07:28 PM, Brian Norris wrote: Hi, On Fri, Mar 09, 2018 at 07:20:38PM -0800, Guenter Roeck wrote: On 03/09/2018 06:44 PM, Brian Norris wrote: RK3399 has rst_pulse_length in CONTROL_REG[4:2], determining the length of pulse to issue for system reset. We shouldn't

Re: [PATCH 4.9 00/65] 4.9.87-stable review

On 03/09/2018 05:18 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.87 release. > There are 65 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

Re: [PATCH 4.4 00/36] 4.4.121-stable review

On 03/09/2018 05:18 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.121 release. > There are 36 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

Re: [PATCH] x86, powerpc : pkey-mprotect must allow pkey-0

On Fri, Mar 09, 2018 at 02:40:32PM -0800, Dave Hansen wrote: > On 03/09/2018 12:12 AM, Ram Pai wrote: > > Once an address range is associated with an allocated pkey, it cannot be > > reverted back to key-0. There is no valid reason for the above behavior. On > > the contrary applications need the

Re: [PATCH] scsi: resolve COMMAND_SIZE at compile time

On Fri, 2018-03-09 at 23:33 +0100, Stephen Kitt wrote: > +/* > + * SCSI command sizes are as follows, in bytes, for fixed size commands, per > + * group: 6, 10, 10, 12, 16, 12, 10, 10. The top three bits of an opcode > + * determine its group. > + * The size table is encoded into a 32-bit value by

Re: WARNING in __proc_create

On 03/09/2018 02:48 PM, Cong Wang wrote: On Fri, Mar 9, 2018 at 1:59 PM, syzbot wrote: Hello, syzbot hit the following crash on net-next commit 617aebe6a97efa539cc4b8a52adccd89596e6be0 (Sun Feb 4 00:25:42 2018 +) Merge tag

Re: [PATCH v4] cpuset: Enable cpuset controller in default hierarchy

On 03/09/2018 05:17 PM, Peter Zijlstra wrote: > On Fri, Mar 09, 2018 at 03:43:34PM -0500, Waiman Long wrote: >> The isolcpus= parameter just reduce the cpus available to the rests of >> the system. The cpuset controller does look at that value and make >> adjustment accordingly, but it has no

Re: WARNING in __proc_create

Cong Wang wrote: > On Fri, Mar 9, 2018 at 2:58 PM, Eric Dumazet wrote: > > > > > > On 03/09/2018 02:56 PM, Eric Dumazet wrote: > > > >> > >> I sent a patch a while back, but Pablo/Florian wanted more than that > >> simple fix. > >> > >> We also

[PATCH] drm/panel: simple: Fix the bus_format for the Ontat panel.

This fixes bad color output. When I was first testing the device I had the DPI hardware set to 666 mode, but apparently in the refactor to use the bus_format information from the panel driver, I failed to actually update the panel. Signed-off-by: Eric Anholt Fixes: e8b6f561b2ee

[PATCH] drm/vc4: Fix oops dereferencing DPI's connector since panel_bridge.

In the cleanup, I didn't notice that we needed to dereference the connector for the bus_format. Fix the regression by looking up the first (and only) connector attached to us, and assume that its bus_format is what we want. Some day it would be good to have that part of display_info attached to

Re: [PATCH 1/2] dt-bindings: trivial: add various mcp4017/18/19 potentiometers

On Thu, Mar 08, 2018 at 08:58:29PM +0100, Peter Rosin wrote: > They come in 5 kOhm, 10 kOhm, 50 kOhm and 100 kOhm variations. > > Signed-off-by: Peter Rosin > --- > Documentation/devicetree/bindings/trivial-devices.txt | 12 > 1 file changed, 12 insertions(+) I've

[PATCH 4.15 09/11] scsi: mpt3sas: fix oops in error handlers after shutdown/unload

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Mauricio Faria de Oliveira commit 9ff549ffb4fb4cc9a4b24d1de9dc3e68287797c4 upstream. This patch adds checks for 'ioc->remove_host' in the SCSI error handlers, so

[PATCH 4.15 07/11] bpf: allow xadd only on aligned memory

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit ca36960211eb228bcbc7aaebfa0d027368a94c60 ] The requirements around atomic_add() / atomic64_add() resp. their JIT implementations differ

[PATCH 4.15 00/11] 4.15.9-stable review

This is the start of the stable review cycle for the 4.15.9 release. There are 11 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 Mon Mar 12 00:18:21 UTC 2018. Anything

[PATCH 4.15 10/11] scsi: mpt3sas: wait for and flush running commands on shutdown/unload

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Sreekanth Reddy commit c666d3be99c000bb889a33353e9be0fa5808d3de upstream. This patch finishes all outstanding SCSI IO commands (but not other commands, e.g.,

[PATCH 4.14 3/9] bpf: fix rcu lockdep warning for lpm_trie map_free callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ upstream commit 6c5f61023c5b0edb0c8a64c902fe97c6453b1852 ] Commit 9a3efb6b661f ("bpf: fix memory leak in lpm_trie map_free callback function") fixed a memory

[PATCH 4.14 1/9] bpf: fix mlock precharge on arraymaps

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 9c2d63b843a5c8a8d0559cc067b5398aa5ec3ffc ] syzkaller recently triggered OOM during percpu map allocation; while there is work in

[PATCH 4.15 06/11] bpf: add schedule points in percpu arrays management

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to

[PATCH 4.9 40/65] ppp: prevent unregistered channels from connecting to PPP units

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault [ Upstream commit 77f840e3e5f09c6d7d727e85e6e08276dd813d11 ] PPP units don't hold any reference on the channels connected to it. It is the channel's

[PATCH 4.9 38/65] net: ipv4: dont allow setting net.ipv4.route.min_pmtu below 68

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit c7272c2f1229125f74f22dcdd59de9bbd804f1c8 ] According to RFC 1191 sections 3 and 4, ICMP frag-needed messages indicating an MTU below 68

[PATCH 4.9 57/65] net: mpls: Pull common label check into helper

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern commit b7b386f42f079b25b942c756820e36c6bd09b2ca upstream. mpls_route_add and mpls_route_del have the same checks on the label. Move to a helper. Avoid duplicate

[PATCH 4.15 05/11] bpf, arm64: fix out of bounds access in tail call

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ upstream commit 16338a9b3ac30740d49f5dfed81bac0ffa53b9c7 ] I recently noticed a crash on arm64 when feeding a bogus index into BPF tail call helper.

[PATCH 4.9 30/65] md: only allow remove_and_add_spares when no sync_thread running.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 39772f0a7be3b3dc26c74ea13fe7847fd1522c8b upstream. The locking protocols in md assume that a device will never be removed from an array during

[PATCH 4.14 6/9] bpf: add schedule points in percpu arrays management

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ upstream commit 32fff239de37ef226d5b66329dd133f64d63b22d ] syszbot managed to trigger RCU detected stalls in bpf_array_free_percpu() It takes time to

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