Re: [PATCH 0/3] fs: reduce export usage of kerne_read*() calls

On Wed, May 13, 2020 at 11:17:36AM -0700, Christoph Hellwig wrote: > Can you also move kernel_read_* out of fs.h? That header gets pulled > in just about everywhere and doesn't really need function not related > to the general fs interface. Sure, where should I dump these? Luis __

Re: kexec: arm: possible overwrite of initrd

On Fri, May 15, 2020 at 03:57:12PM +0200, Corentin Labbe wrote: > Hello > > Following https://lkml.org/lkml/2020/4/6/96 I was able to boot my Cubieboard4 > via kexec reliabily. You can try increasing the kernel size that kexec thinks the kernel needs, but it should be extremely accurate with mod

Re: [PATCH v5] kernel: add panic_on_taint

On Fri, May 15, 2020 at 01:55:02PM -0400, Rafael Aquini wrote: > Analogously to the introduction of panic_on_warn, this patch introduces a > kernel > option named panic_on_taint in order to provide a simple and generic way to > stop > execution and catch a coredump when the kernel gets tainted by

[PATCH v5] kernel: add panic_on_taint

Analogously to the introduction of panic_on_warn, this patch introduces a kernel option named panic_on_taint in order to provide a simple and generic way to stop execution and catch a coredump when the kernel gets tainted by any given flag. This is useful for debugging sessions as it avoids having

kexec: arm: possible overwrite of initrd

Hello Following https://lkml.org/lkml/2020/4/6/96 I was able to boot my Cubieboard4 via kexec reliabily. But now I have started to use kernelCI builds, I got problems. All sunxi_defconfig kernel works but not multi_v7_defconfig which got: [1.896540] Trying to unpack rootfs image as initramfs

kdump: Getting "warn_alloc" warning during boot of kdump kernel

Hi All, We are getting "warn_alloc" warning during boot of kdump kernel. This warning is observed with latest upstream tag (v5.7-rc5). Primary/1st Kernel # dmesg | grep crash [0.00] crashkernel reserved: 0xd600 - 0xf600 (512 MB) [0.

Re: [PATCH v2 0/3] printk: replace ringbuffer

On (20/05/01 11:46), John Ogness wrote: > Hello, > > Here is a v2 for the first series to rework the printk subsystem. The > v1 and history are here [0]. This first series only replaces the > existing ringbuffer implementation. No locking is removed. No > semantics/behavior of printk are changed.

Re: [PATCH] arm64/defconfig: Enable CONFIG_KEXEC_FILE

Hi Arnd, On Thu, Apr 30, 2020 at 10:05 AM Bhupesh Sharma wrote: > > On Tue, Apr 28, 2020 at 3:37 PM Catalin Marinas > wrote: > > > > On Tue, Apr 28, 2020 at 01:55:58PM +0530, Bhupesh Sharma wrote: > > > On Wed, Apr 8, 2020 at 4:17 PM Mark Rutland wrote: > > > > On Tue, Apr 07, 2020 at 04:01:40