RE: [PATCH v2 0/4] makedumpfile: harden parsing of old prink buffer

2022-03-17 Thread 萩尾 一仁
-Original Message- > On Wed, Mar 16, 2022 at 9:17 AM David Wysochanski wrote: > > > > On Mon, Mar 14, 2022 at 12:04 PM Philipp Rudo wrote: > > > > > > Hi, > > > > > > dumping the dmesg can cause an endless loop for the old prink mechanism (> > > > v3.5.0 and < v5.10.0) when the log_buf

RE: [PATCH v2 4/4] makedumpfile: print error when reading with unsupported compression

2022-03-17 Thread 萩尾 一仁
-Original Message- > Currently makedumpfile only checks if the required compression algorithm > was enabled during build when compressing a dump but not when reading > from one. This can lead to situations where, one version of makedumpfile > creates the dump using a compression algorithm

RE: [PATCH v2 2/4] makedumpfile: use pointer arithmetics for dump_dmesg

2022-03-17 Thread 萩尾 一仁
-Original Message- > When parsing the printk buffer for the old printk mechanism (> v3.5.0+ and > < 5.10.0) a log entry is currently specified by the offset into the > buffer where the entry starts. Change this to use a pointers instead. > This is done in preparation for using the new

Re: [RESEND PATCH v3 1/3] kexec: clean up arch_kexec_kernel_verify_sig

2022-03-17 Thread Baoquan He
On 03/18/22 at 10:48am, Coiby Xu wrote: > On Thu, Mar 17, 2022 at 08:45:35PM +0800, Baoquan He wrote: > > On 03/04/22 at 10:03am, Coiby Xu wrote: > > > From: Coiby Xu > > > > > > commit 9ec4ecef0af7790551109283ca039a7c52de343c ("kexec_file,x86, > > > powerpc: factor out kexec_file_ops functions"

Re: [RESEND PATCH v3 1/3] kexec: clean up arch_kexec_kernel_verify_sig

2022-03-17 Thread Coiby Xu
On Thu, Mar 17, 2022 at 08:45:35PM +0800, Baoquan He wrote: On 03/04/22 at 10:03am, Coiby Xu wrote: From: Coiby Xu commit 9ec4ecef0af7790551109283ca039a7c52de343c ("kexec_file,x86, powerpc: factor out kexec_file_ops functions" allows implementing the arch-specific implementation of kernel

Re: [RESEND PATCH v3 1/3] kexec: clean up arch_kexec_kernel_verify_sig

2022-03-17 Thread Baoquan He
On 03/04/22 at 10:03am, Coiby Xu wrote: > From: Coiby Xu > > commit 9ec4ecef0af7790551109283ca039a7c52de343c ("kexec_file,x86, > powerpc: factor out kexec_file_ops functions" allows implementing > the arch-specific implementation of kernel image verification > in kexec_file_ops->verify_sig.

Re: [PATCH v5 4/8] crash: generic crash hotplug support infrastructure

2022-03-17 Thread Sourabh Jain
On 15/03/22 19:42, Eric DeVolder wrote: On 3/15/22 07:08, Sourabh Jain wrote: Hello Eric, On 03/03/22 21:57, Eric DeVolder wrote: This patch introduces a generic crash hot plug/unplug infrastructure for CPU and memory changes. Upon CPU and memory changes, a generic crash_hotplug_handler()

Re: Qemu does not like kexec initrd

2022-03-17 Thread Tobias Powalowski
Hi, after doing tests with initrds, it seems the error on kernel message is wrong, the ZSTD archive is fine and decompression is not faulty. For what's it worth for, the shown error is wrong. All works as expected. greetings tpowa Am Do., 17. März 2022 um 09:45 Uhr schrieb Tobias Powalowski : > >

Re: Qemu does not like kexec initrd

2022-03-17 Thread Tobias Powalowski
Hi, Which upstream code? Arch Linux kernel is upstream Qemu is upstream - Kernel message prints the error greetings tpowa Am Do., 17. März 2022 um 09:34 Uhr schrieb Tao Liu : > > Hi Tobias, > > The kernel you provided is not an upstream kernel, which contains > distribution specific modification,

Re: Qemu does not like kexec initrd

2022-03-17 Thread Tao Liu
Hi Tobias, The kernel you provided is not an upstream kernel, which contains distribution specific modification, as well as the kexec. Since you are reporting an issue to the upstream, I suggest you: 1) re-run your tests against the upstream code, instead of distribution specific code. 2) if the

Re: [PATCH v21 3/5] arm64: kdump: reimplement crashkernel=X

2022-03-17 Thread Leizhen (ThunderTown)
On 2022/3/17 11:47, Baoquan He wrote: > On 03/17/22 at 11:19am, Leizhen (ThunderTown) wrote: >> >> >> On 2022/3/17 10:36, Baoquan He wrote: >>> On 03/16/22 at 09:11pm, Leizhen (ThunderTown) wrote: On 2022/3/16 20:11, Baoquan He wrote: > On 02/27/22 at 11:07am, Zhen Lei wrote: