Re: auxv stuff (Re: [PATCH] prctl: fix PR_SET_MM_AUXV kernel stack leak)

2021-03-14 Thread Cyrill Gorcunov
On Mon, Mar 15, 2021 at 09:00:00AM +0300, Alexey Dobriyan wrote: > On Sun, Mar 14, 2021 at 02:40:05PM -0700, Linus Torvalds wrote: > > [mm->saved_auxv] > > > > That's a separate issue, and I can't find it in myself to care (and > > nobody has ever complained), but I thought I'd mention it. > > Th

Re: [PATCH v2 0/4] enable flexspi support on imx8mp

2021-03-14 Thread Shawn Guo
On Tue, Mar 09, 2021 at 06:31:12AM +0100, Heiko Schocher wrote: > > This series enables support for the SPI NOR on the > imx8mp based phyboard-pollux-rdk board. > > Patches new in v2: > "spi: fspi: enable fspi driver for on imx8mp" > which adds own compatible entry for imx8mp > > and seperate in

Re: [PATCH v1 00/14] Multigenerational LRU

2021-03-14 Thread Yu Zhao
On Mon, Mar 15, 2021 at 09:13:50AM +0800, Hillf Danton wrote: > On Sat, 13 Mar 2021 00:57:33 -0700 Yu Zhao wrote: > > TLDR > > > > The current page reclaim is too expensive in terms of CPU usage and > > often making poor choices about what to evict. We would like to offer > > a performant, ver

Re: [PATCH v2 5/5] mtd: spi-nor: swp: Drop 'else' after 'return'

2021-03-14 Thread Joe Perches
On Mon, 2021-03-08 at 11:58 +0530, Pratyush Yadav wrote: > On 06/03/21 11:50AM, Tudor Ambarus wrote: > > else is not generally useful after a break or return. > > > > Signed-off-by: Tudor Ambarus > > Reviewed-by: Pratyush Yadav > I don't think this improves the code. Generally, checkpatch is

Re: [PATCH 0/2] Resolve NXP flexspi bindings compatibility warnings

2021-03-14 Thread Shawn Guo
On Tue, Mar 09, 2021 at 04:44:23PM +0530, Kuldeep Singh wrote: > This patches series aim is to resolve NXP flexspi bindings compatibility > warnings which were observed after running 'make dtbs_check' with > https://lore.kernel.org/linux-devicetree/20210309103528.3538910-1-kuldeep.si...@nxp.com/ >

[PATCH v3] x86/kvm: Fix broken irq restoration in kvm_wait

2021-03-14 Thread Wanpeng Li
From: Wanpeng Li After commit 997acaf6b4b59c (lockdep: report broken irq restoration), the guest splatting below during boot: raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 1 PID: 169 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x26/0x30 Modules linked in: hi

[PATCH] kconfig: use true and false for bool variable

2021-03-14 Thread Yang Li
fixed the following coccicheck: ./scripts/kconfig/confdata.c:36:9-10: WARNING: return of 0/1 in function 'is_dir' with return type bool Reported-by: Abaci Robot Signed-off-by: Yang Li --- scripts/kconfig/confdata.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/kcon

Re: [PATCH] x86/kvm: Fix broken irq restoration in kvm_wait

2021-03-14 Thread Wanpeng Li
On Sat, 13 Mar 2021 at 17:33, Paolo Bonzini wrote: > > On 13/03/21 01:57, Wanpeng Li wrote: > >> A third option would be to split the paths. In the end, it's only the > >> ptr/val > >> line that's shared. > > I just sent out a formal patch for my alternative fix, I think the > > whole logic in k

Re: [PATCH] task_work: kasan: record task_work_add() call stack

2021-03-14 Thread Dmitry Vyukov
On Mon, Mar 15, 2021 at 3:00 AM Walter Wu wrote: > > Why record task_work_add() call stack? > Syzbot reports many use-after-free issues for task_work, see [1]. > After see the free stack and the current auxiliary stack, we think > they are useless, we don't know where register the work, this work

<    1   2   3   4   5   6