Re: [PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

ent memory walking functions for > kexec_add_buffer. Intel uses iomem to track reserved memory ranges, > but PowerPC uses the memblock subsystem. > > Signed-off-by: Thiago Jung Bauermann <bauer...@linux.vnet.ibm.com> > Cc: Eric Biederman <ebied...@xmission.com> > Cc: Dave Y

Re: [PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

ent memory walking functions for > kexec_add_buffer. Intel uses iomem to track reserved memory ranges, > but PowerPC uses the memblock subsystem. > > Signed-off-by: Thiago Jung Bauermann > Cc: Eric Biederman > Cc: Dave Young > Cc: ke...@lists.infradead.org > Cc: l

Re: [PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

lt;ebied...@xmission.com> > Cc: Dave Young <dyo...@redhat.com> > Cc: ke...@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > --- > include/linux/kexec.h | 4 > kernel/kexec_file.c | 66 > ++- > 2 f

Re: [PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

On 06/21/16 at 04:48pm, Thiago Jung Bauermann wrote: > kexec_locate_mem_hole will be used by the PowerPC kexec_file_load > implementation to find free memory for the purgatory stack. > > Signed-off-by: Thiago Jung Bauermann > Cc: Eric Biederman > Cc: Dave Young > Cc: ke..

Re: [PATCH 0/6] kexec_file: Add buffer hand-over for the next kernel

On 06/20/16 at 10:44pm, Thiago Jung Bauermann wrote: > Hello, > > This patch series implements a mechanism which allows the kernel to pass on > a buffer to the kernel that will be kexec'd. This buffer is passed as a > segment which is added to the kimage when it is being prepared by >

Re: [PATCH 0/6] kexec_file: Add buffer hand-over for the next kernel

On 06/20/16 at 10:44pm, Thiago Jung Bauermann wrote: > Hello, > > This patch series implements a mechanism which allows the kernel to pass on > a buffer to the kernel that will be kexec'd. This buffer is passed as a > segment which is added to the kimage when it is being prepared by >

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/17/16 at 05:51pm, Thiago Jung Bauermann wrote: > Am Freitag, 17 Juni 2016, 15:35:23 schrieb Dave Young: > > On 06/16/16 at 05:39pm, Thiago Jung Bauermann wrote: > > > Am Donnerstag, 16 Juni 2016, 09:58:53 schrieb Dave Young: > > > > On 06/15/16 at 01:21p

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/17/16 at 05:51pm, Thiago Jung Bauermann wrote: > Am Freitag, 17 Juni 2016, 15:35:23 schrieb Dave Young: > > On 06/16/16 at 05:39pm, Thiago Jung Bauermann wrote: > > > Am Donnerstag, 16 Juni 2016, 09:58:53 schrieb Dave Young: > > > > On 06/15/16 at 01:21p

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/16/16 at 05:39pm, Thiago Jung Bauermann wrote: > Am Donnerstag, 16 Juni 2016, 09:58:53 schrieb Dave Young: > > On 06/15/16 at 01:21pm, Thiago Jung Bauermann wrote: > > > +/** > > > + * arch_kexec_walk_mem - call func(data) on free memory regions > >

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/16/16 at 05:39pm, Thiago Jung Bauermann wrote: > Am Donnerstag, 16 Juni 2016, 09:58:53 schrieb Dave Young: > > On 06/15/16 at 01:21pm, Thiago Jung Bauermann wrote: > > > +/** > > > + * arch_kexec_walk_mem - call func(data) on free memory regions > >

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/15/16 at 01:21pm, Thiago Jung Bauermann wrote: > Hello Dave, > > Am Mittwoch, 15 Juni 2016, 15:33:02 schrieb Dave Young: > > > @@ -472,14 +498,16 @@ int kexec_add_buffer(struct kimage *image, char > > > *buffer, unsigned long bufsz,> >

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/15/16 at 01:21pm, Thiago Jung Bauermann wrote: > Hello Dave, > > Am Mittwoch, 15 Juni 2016, 15:33:02 schrieb Dave Young: > > > @@ -472,14 +498,16 @@ int kexec_add_buffer(struct kimage *image, char > > > *buffer, unsigned long bufsz,> >

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On 06/15/16 at 10:40am, Willy Tarreau wrote: > On Wed, Jun 15, 2016 at 04:33:32PM +0800, Dave Young wrote: > > On 06/14/16 at 10:41pm, Willy Tarreau wrote: > > > On Tue, Jun 14, 2016 at 01:19:06PM -0700, Andrew Morton wrote: > > > > On Sat, 11 Jun 2016 03:3

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On 06/15/16 at 10:40am, Willy Tarreau wrote: > On Wed, Jun 15, 2016 at 04:33:32PM +0800, Dave Young wrote: > > On 06/14/16 at 10:41pm, Willy Tarreau wrote: > > > On Tue, Jun 14, 2016 at 01:19:06PM -0700, Andrew Morton wrote: > > > > On Sat, 11 Jun 2016 03:3

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On 06/14/16 at 10:41pm, Willy Tarreau wrote: > On Tue, Jun 14, 2016 at 01:19:06PM -0700, Andrew Morton wrote: > > On Sat, 11 Jun 2016 03:33:08 +0200 Heinrich Schuchardt > > wrote: > > > > > An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. > > > > > >

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On 06/14/16 at 10:41pm, Willy Tarreau wrote: > On Tue, Jun 14, 2016 at 01:19:06PM -0700, Andrew Morton wrote: > > On Sat, 11 Jun 2016 03:33:08 +0200 Heinrich Schuchardt > > wrote: > > > > > An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. > > > > > > ... > > > > > > ---

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

auermann <bauer...@linux.vnet.ibm.com> > Cc: Eric Biederman <ebied...@xmission.com> > Cc: Dave Young <dyo...@redhat.com> > Cc: ke...@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > --- > include/linux/kexec.h | 3 +++ > kernel/kexec_file.c | 44 +

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

Bauermann > Cc: Eric Biederman > Cc: Dave Young > Cc: ke...@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > --- > include/linux/kexec.h | 3 +++ > kernel/kexec_file.c | 44 > 2 files changed, 39 insertions(+), 8

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

> KEXEC_ON_CRASH. > > Am Montag, 13 Juni 2016, 15:29:39 schrieb Dave Young: > > On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > > > Allow architectures to specify different memory walking functions for > > > kexec_add_buffer. Intel uses iomem to t

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

> KEXEC_ON_CRASH. > > Am Montag, 13 Juni 2016, 15:29:39 schrieb Dave Young: > > On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > > > Allow architectures to specify different memory walking functions for > > > kexec_add_buffer. Intel uses iomem to t

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > Allow architectures to specify different memory walking functions for > kexec_add_buffer. Intel uses iomem to track reserved memory ranges, > but PowerPC uses the memblock subsystem. Can the crashk_res be inserted to iomem_resource so that

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > Allow architectures to specify different memory walking functions for > kexec_add_buffer. Intel uses iomem to track reserved memory ranges, > but PowerPC uses the memblock subsystem. Can the crashk_res be inserted to iomem_resource so that

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > Allow architectures to specify different memory walking functions for > kexec_add_buffer. Intel uses iomem to track reserved memory ranges, > but PowerPC uses the memblock subsystem. > > Also, factor kexec_locate_mem_hole out of

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > Allow architectures to specify different memory walking functions for > kexec_add_buffer. Intel uses iomem to track reserved memory ranges, > but PowerPC uses the memblock subsystem. > > Also, factor kexec_locate_mem_hole out of

Re: [PATCH 1/8] kexec_file: Remove unused members from struct kexec_buf.

al.h > @@ -26,8 +26,6 @@ struct kexec_sha_region { > */ > struct kexec_buf { > struct kimage *image; > - char *buffer; > - unsigned long bufsz; > unsigned long mem; > unsigned long memsz; > unsigned long buf_align; > -- > 1.9.1 > > > ___ > kexec mailing list > ke...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/kexec Acked-by: Dave Young <dyo...@redhat.com> Thanks Dave

Re: [PATCH 1/8] kexec_file: Remove unused members from struct kexec_buf.

kexec_sha_region { > */ > struct kexec_buf { > struct kimage *image; > - char *buffer; > - unsigned long bufsz; > unsigned long mem; > unsigned long memsz; > unsigned long buf_align; > -- > 1.9.1 > > > ___ > kexec mailing list > ke...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/kexec Acked-by: Dave Young Thanks Dave

Re: [PATCH 0/8] kexec_file_load implementation for PowerPC

On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > Hello, > > This patch series implements the kexec_file_load system call on PowerPC. > > It starts by removing an x86 assumption from kexec_file: kexec_add_buffer uses > iomem to find reserved memory ranges, but PowerPC uses the memblock

Re: [PATCH 0/8] kexec_file_load implementation for PowerPC

On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote: > Hello, > > This patch series implements the kexec_file_load system call on PowerPC. > > It starts by removing an x86 assumption from kexec_file: kexec_add_buffer uses > iomem to find reserved memory ranges, but PowerPC uses the memblock

Re: [PATCH] MAINTAINERS: Kdump maintainers update

ainers as > > > they have been contributing to kdump for a long time now and they are in > > > a much better position to spend time on this than me. > > [] > > > diff --git a/MAINTAINERS b/MAINTAINERS > > [] > > > @@ -6189,8 +6189,9 @@ F: Documentation/kbuild/kconfig-la

Re: [PATCH] MAINTAINERS: Kdump maintainers update

ainers as > > > they have been contributing to kdump for a long time now and they are in > > > a much better position to spend time on this than me. > > [] > > > diff --git a/MAINTAINERS b/MAINTAINERS > > [] > > > @@ -6189,8 +6189,9 @@ F: Documentation/kbuild/kconfig-l

kexec loading fails without kernel code address in /proc/iomem

Hi, Linus Zhengyu Zhang found a kexec failure caused by below commit: commit c4004b02f8e5b9ce357a0bb1641756cc86962664 Author: Linus Torvalds Date: Wed Apr 6 13:45:07 2016 -0700 x86: remove the kernel code/data/bss resources from

kexec loading fails without kernel code address in /proc/iomem

Hi, Linus Zhengyu Zhang found a kexec failure caused by below commit: commit c4004b02f8e5b9ce357a0bb1641756cc86962664 Author: Linus Torvalds Date: Wed Apr 6 13:45:07 2016 -0700 x86: remove the kernel code/data/bss resources from /proc/iomem Let's see if anybody even notices.

[PATCH V3] proc-vmcore: wrong data type casting fix

n_t instead so that the variables in are not truncated. Signed-off-by: Baoquan He <b...@redhat.com> Signed-off-by: Dave Young <dyo...@redhat.com> --- v2->v3: tweak patch description about bug details for people to get the problem easier. v1->v2: spelling fix in patch log fs/proc/vmcore.c |7 ++

[PATCH V3] proc-vmcore: wrong data type casting fix

n_t instead so that the variables in are not truncated. Signed-off-by: Baoquan He Signed-off-by: Dave Young --- v2->v3: tweak patch description about bug details for people to get the problem easier. v1->v2: spelling fix in patch log fs/proc/vmcore.c |7 +-- 1 file changed, 5 insertions(+), 2 d

Re: [PATCH V2] proc-vmcore: wrong data type casting fix

Hi, HATAYAMA On 03/14/16 at 12:25pm, HATAYAMA Daisuke wrote: > From: Dave Young <dyo...@redhat.com> > Subject: [PATCH V2] proc-vmcore: wrong data type casting fix > Date: Fri, 11 Mar 2016 16:42:48 +0800 > > > On i686 PAE enabled machine the contiguous physical area could

Re: [PATCH V2] proc-vmcore: wrong data type casting fix

Hi, HATAYAMA On 03/14/16 at 12:25pm, HATAYAMA Daisuke wrote: > From: Dave Young > Subject: [PATCH V2] proc-vmcore: wrong data type casting fix > Date: Fri, 11 Mar 2016 16:42:48 +0800 > > > On i686 PAE enabled machine the contiguous physical area could be large > > and it

Re: [PATCH V2] proc-vmcore: wrong data type casting fix

Hi, Andrew On 03/11/16 at 12:27pm, Andrew Morton wrote: > On Fri, 11 Mar 2016 16:42:48 +0800 Dave Young <dyo...@redhat.com> wrote: > > > On i686 PAE enabled machine the contiguous physical area could be large > > and it can cause trimming down variables in below calcul

Re: [PATCH V2] proc-vmcore: wrong data type casting fix

Hi, Andrew On 03/11/16 at 12:27pm, Andrew Morton wrote: > On Fri, 11 Mar 2016 16:42:48 +0800 Dave Young wrote: > > > On i686 PAE enabled machine the contiguous physical area could be large > > and it can cause trimming down variables in below calculation in > > read_

[PATCH V2] proc-vmcore: wrong data type casting fix

trigger BUG_ON() in remap_pfn_range(). Use unsigned long long in min_t instead so that the variables are not truncated. Signed-off-by: Baoquan He <b...@redhat.com> Signed-off-by: Dave Young <dyo...@redhat.com> --- v1->v2: spelling fix in patch log fs/proc/vmcore.c |7 +-- 1 file changed

[PATCH V2] proc-vmcore: wrong data type casting fix

trigger BUG_ON() in remap_pfn_range(). Use unsigned long long in min_t instead so that the variables are not truncated. Signed-off-by: Baoquan He Signed-off-by: Dave Young --- v1->v2: spelling fix in patch log fs/proc/vmcore.c |7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) --- linux-x86.ori

[PATCH] proc-vmcore: wrong data type casting fix

remap_pfn_range(). Use unsigned long long in min_t instead so that the variables are not truncated. Signed-off-by: Baoquan He <b...@redhat.com> Signed-off-by: Dave Young <dyo...@redhat.com> --- fs/proc/vmcore.c |7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) --- linu

[PATCH] proc-vmcore: wrong data type casting fix

remap_pfn_range(). Use unsigned long long in min_t instead so that the variables are not truncated. Signed-off-by: Baoquan He Signed-off-by: Dave Young --- fs/proc/vmcore.c |7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) --- linux-x86.orig/fs/proc/vmcore.c +++ linux-x86/f

Re: [PATCH 1/2] [PATCH 1/2] Introduce new macros min_lt and max_lt for comparing with larger type

; > truncate the u64, so we need use min_t or max_t with u64. > > > > To simplify the usage introducing two more macros min_lt and max_lt, > > 'lt' means larger type. > > > > Signed-off-by: Dave Young <dyo...@redhat.com> > > --- > > inc

Re: [PATCH 1/2] [PATCH 1/2] Introduce new macros min_lt and max_lt for comparing with larger type

so we need use min_t or max_t with u64. > > > > To simplify the usage introducing two more macros min_lt and max_lt, > > 'lt' means larger type. > > > > Signed-off-by: Dave Young > > --- > > include/linux/kernel.h | 13 + > > 1 file ch

Re: [PATCH 2/2] [PATCH 2/2] proc-vmcore: wrong data type casting fix

Hi, Minfei On 03/11/16 at 03:19pm, Minfei Huang wrote: > On 03/11/16 at 02:21pm, dyo...@redhat.com wrote: > > @@ -231,7 +231,8 @@ static ssize_t __read_vmcore(char *buffe > > > > list_for_each_entry(m, _list, list) { > > if (*fpos < m->offset + m->size) { > > -

Re: [PATCH 2/2] [PATCH 2/2] proc-vmcore: wrong data type casting fix

Hi, Minfei On 03/11/16 at 03:19pm, Minfei Huang wrote: > On 03/11/16 at 02:21pm, dyo...@redhat.com wrote: > > @@ -231,7 +231,8 @@ static ssize_t __read_vmcore(char *buffe > > > > list_for_each_entry(m, _list, list) { > > if (*fpos < m->offset + m->size) { > > -

Re: [PATCH 0/2] Export new VMCOREINFO about compound page

e > > kernel/kexec_core.c | 7 +-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > Acked-by: Dave Young <dyo...@redhat.com> Thanks Dave

Re: [PATCH 0/2] Export new VMCOREINFO about compound page

e > > kernel/kexec_core.c | 7 +-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > Acked-by: Dave Young Thanks Dave

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

On 02/11/16 at 04:09pm, Matt Fleming wrote: > On Fri, 05 Feb, at 08:41:15AM, Dave Young wrote: > > On 02/04/16 at 11:56am, Matt Fleming wrote: > > > On Thu, 04 Feb, at 07:09:03PM, Dave Young wrote: > > > > > > > > Consider the original cod

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

On 02/11/16 at 04:09pm, Matt Fleming wrote: > On Fri, 05 Feb, at 08:41:15AM, Dave Young wrote: > > On 02/04/16 at 11:56am, Matt Fleming wrote: > > > On Thu, 04 Feb, at 07:09:03PM, Dave Young wrote: > > > > > > > > Consider the original cod

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

On 02/04/16 at 11:56am, Matt Fleming wrote: > On Thu, 04 Feb, at 07:09:03PM, Dave Young wrote: > > > > Consider the original code path, maybe change it to efi_kexec_setup will > > be better to remind people? Or something else like a wraper function with > > similar n

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

Hi, Matt Thanks for the feedback. On 02/04/16 at 10:03am, Matt Fleming wrote: > On Wed, 03 Feb, at 10:53:33PM, Matt Fleming wrote: > > On Thu, 04 Feb, at 05:42:00AM, Dave Young wrote: > > > > > > On 01/27/16 at 07:20pm, Dave Young wrote: > > > > For ke

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

Hi, Matt Thanks for the feedback. On 02/04/16 at 10:03am, Matt Fleming wrote: > On Wed, 03 Feb, at 10:53:33PM, Matt Fleming wrote: > > On Thu, 04 Feb, at 05:42:00AM, Dave Young wrote: > > > > > > On 01/27/16 at 07:20pm, Dave Young wrote: > > > > For ke

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

On 02/04/16 at 11:56am, Matt Fleming wrote: > On Thu, 04 Feb, at 07:09:03PM, Dave Young wrote: > > > > Consider the original code path, maybe change it to efi_kexec_setup will > > be better to remind people? Or something else like a wraper function with > > similar n

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

On 01/27/16 at 07:20pm, Dave Young wrote: > For kexec reboot the bgrt image address could contains random data because > we have freed boot service areas in 1st kernel boot phase. One possible > result is kmalloc fail in efi_bgrt_init due to large random image size. > > So chang

Re: [PATCH] x86/efi: skip bgrt init for kexec reboot

On 01/27/16 at 07:20pm, Dave Young wrote: > For kexec reboot the bgrt image address could contains random data because > we have freed boot service areas in 1st kernel boot phase. One possible > result is kmalloc fail in efi_bgrt_init due to large random image size. > > So chang

[PATCH] x86/efi: skip bgrt init for kexec reboot

-by: Dave Young --- arch/x86/platform/efi/efi.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- linux-x86.orig/arch/x86/platform/efi/efi.c +++ linux-x86/arch/x86/platform/efi/efi.c @@ -531,7 +531,8 @@ void __init efi_init(void) void __init efi_late_init(void

[PATCH] x86/efi: skip bgrt init for kexec reboot

-by: Dave Young <dyo...@redhat.com> --- arch/x86/platform/efi/efi.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- linux-x86.orig/arch/x86/platform/efi/efi.c +++ linux-x86/arch/x86/platform/efi/efi.c @@ -531,7 +531,8 @@ void __init efi_init(void) void __init efi_late_ini

Re: [PATCH v3 14/17] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

el" > > Note, the caller of walk_iomem_res() with "GART" will be removed > in a later patch. > > Cc: Borislav Petkov > Cc: Dan Williams > Cc: Dave Young > Cc: Minfei Huang > Cc: x...@kernel.org > Cc: linux-nvd...@lists.01.org > Cc: ke...@lists.in

Re: [PATCH v3 07/17] kexec: Set IORESOURCE_SYSTEM_RAM to System RAM

ystem RAM range. > > Change kexec_add_buffer() to call walk_iomem_res() with > IORESOURCE_SYSTEM_RAM type for "Crash kernel". > > Cc: Andrew Morton > Cc: Dave Young > Cc: ke...@lists.infradead.org > Signed-off-by: Toshi Kani > --- > kernel/kexec_core.c |

Re: [PATCH v3 14/17] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

el" > > Note, the caller of walk_iomem_res() with "GART" will be removed > in a later patch. > > Cc: Borislav Petkov <b...@alien8.de> > Cc: Dan Williams <dan.j.willi...@intel.com> > Cc: Dave Young <dyo...@redhat.com> > Cc: Minfei Huang <m

Re: [PATCH v3 07/17] kexec: Set IORESOURCE_SYSTEM_RAM to System RAM

ystem RAM range. > > Change kexec_add_buffer() to call walk_iomem_res() with > IORESOURCE_SYSTEM_RAM type for "Crash kernel". > > Cc: Andrew Morton <a...@linux-foundation.org> > Cc: Dave Young <dyo...@redhat.com> > Cc: ke...@lists.infradead.org > Signed-o

Kexec_file_load failed with "Missing required AuthAttr"

Hi, I saw the warning "Missing required AuthAttr" when testing kexec, known issue? Idea about how to fix it? The kernel is latest linus tree plus sevral patches from Toshi to cleanup io resource structure. in function pkcs7_sig_note_set_of_authattrs(): if

Kexec_file_load failed with "Missing required AuthAttr"

Hi, I saw the warning "Missing required AuthAttr" when testing kexec, known issue? Idea about how to fix it? The kernel is latest linus tree plus sevral patches from Toshi to cleanup io resource structure. in function pkcs7_sig_note_set_of_authattrs(): if

Re: [PATCH v2 14/16] x86, nvdimm, kexec: Use walk_iomem_res_desc() for iomem search

On 01/04/16 at 01:26pm, Borislav Petkov wrote: > On Mon, Jan 04, 2016 at 05:29:37PM +0800, Dave Young wrote: > > Replied to Toshi old kernel will export the "GART" region for amd cards. > > So for old kernel and new kexec-tools we will have problem. > >

Re: [PATCH v2 14/16] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

On 01/04/16 at 05:25pm, Dave Young wrote: > Hi, Toshi, > > On 12/25/15 at 03:09pm, Toshi Kani wrote: > > Change to call walk_iomem_res_desc() for searching resource entries > > with the following names: > > "ACPI Tables" > > "ACPI Non-v

Re: [PATCH v2 14/16] x86, nvdimm, kexec: Use walk_iomem_res_desc() for iomem search

Hi, Boris On 12/27/15 at 11:24am, Borislav Petkov wrote: > On Sun, Dec 27, 2015 at 10:12:57AM +0800, Minfei Huang wrote: > > You can refer the below link that you may get a clue about GART. This is > > the fisrt time kexec-tools tried to support to ignore GART region in 2nd > > kernel. > > > >

Re: [PATCH v2 14/16] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

Hi, Toshi, On 12/25/15 at 03:09pm, Toshi Kani wrote: > Change to call walk_iomem_res_desc() for searching resource entries > with the following names: > "ACPI Tables" > "ACPI Non-volatile Storage" > "Persistent Memory (legacy)" > "Crash kernel" > > Note, the caller of walk_iomem_res() with

Re: [PATCH v2 14/16] x86, nvdimm, kexec: Use walk_iomem_res_desc() for iomem search

Hi, Boris On 12/27/15 at 11:24am, Borislav Petkov wrote: > On Sun, Dec 27, 2015 at 10:12:57AM +0800, Minfei Huang wrote: > > You can refer the below link that you may get a clue about GART. This is > > the fisrt time kexec-tools tried to support to ignore GART region in 2nd > > kernel. > > > >

Re: [PATCH v2 14/16] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

On 01/04/16 at 05:25pm, Dave Young wrote: > Hi, Toshi, > > On 12/25/15 at 03:09pm, Toshi Kani wrote: > > Change to call walk_iomem_res_desc() for searching resource entries > > with the following names: > > "ACPI Tables" > > "ACPI Non-v

Re: [PATCH v2 14/16] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

Hi, Toshi, On 12/25/15 at 03:09pm, Toshi Kani wrote: > Change to call walk_iomem_res_desc() for searching resource entries > with the following names: > "ACPI Tables" > "ACPI Non-volatile Storage" > "Persistent Memory (legacy)" > "Crash kernel" > > Note, the caller of walk_iomem_res() with

Re: [PATCH v2 14/16] x86, nvdimm, kexec: Use walk_iomem_res_desc() for iomem search

On 01/04/16 at 01:26pm, Borislav Petkov wrote: > On Mon, Jan 04, 2016 at 05:29:37PM +0800, Dave Young wrote: > > Replied to Toshi old kernel will export the "GART" region for amd cards. > > So for old kernel and new kexec-tools we will have problem. > >

Re: [PATCH 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

Hi, Xunlei On 12/24/15 at 02:05pm, Xunlei Pang wrote: > On 12/24/2015 at 01:54 PM, Dave Young wrote: > > Ccing Vivek > > > > On 12/23/15 at 07:12pm, Xunlei Pang wrote: > >> Implement the protection method for the crash kernel memory > >> reservation for the

Re: [PATCH 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

Ccing Vivek On 12/23/15 at 07:12pm, Xunlei Pang wrote: > Implement the protection method for the crash kernel memory > reservation for the 64-bit x86 kdump. > > Signed-off-by: Xunlei Pang > --- > Only provided x86_64 implementation, as I've only tested on x86_64 so far. > >

Re: [PATCH 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

Ccing Vivek On 12/23/15 at 07:12pm, Xunlei Pang wrote: > Implement the protection method for the crash kernel memory > reservation for the 64-bit x86 kdump. > > Signed-off-by: Xunlei Pang > --- > Only provided x86_64 implementation, as I've only tested on x86_64 so far. > >

Re: [PATCH 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

Hi, Xunlei On 12/24/15 at 02:05pm, Xunlei Pang wrote: > On 12/24/2015 at 01:54 PM, Dave Young wrote: > > Ccing Vivek > > > > On 12/23/15 at 07:12pm, Xunlei Pang wrote: > >> Implement the protection method for the crash kernel memory > >> reservation for the

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

Hi, On 12/11/15 at 03:26pm, Johannes Berg wrote: > On Mon, 2015-11-23 at 09:37 +0800, Dave Young wrote: > > > Seems there're a lot of other wireless messages. Should we refactor > > them as well? I still did not get chance to see where is the code. > > (My wireless driv

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

Hi, Johannes Sorry for late feedback, I was busying on other things. On 12/11/15 at 03:38pm, Johannes Berg wrote: > On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote: > > cfg80211 module prints a lot of messages like below. Actually > > printing once is acceptable but sometime

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

Hi, Johannes Sorry for late feedback, I was busying on other things. On 12/11/15 at 03:38pm, Johannes Berg wrote: > On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote: > > cfg80211 module prints a lot of messages like below. Actually > > printing once is acceptable but sometime

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

Hi, On 12/11/15 at 03:26pm, Johannes Berg wrote: > On Mon, 2015-11-23 at 09:37 +0800, Dave Young wrote: > > > Seems there're a lot of other wireless messages. Should we refactor > > them as well? I still did not get chance to see where is the code. > > (My wireless driv

Re: [PATCH 06/14] crashdump/cris: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on cris arch even > if the functionality is not available on it. > > Signed-off-by: Daniel Kiper > --- > kexec/arch/cris/kexec-cris.c |5 + > 1

Re: [PATCH 11/14] crashdump/ppc64: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on ppc64 arch even > if the functionality is not available on it. Ditto as ppc, you can read procfs file to get the values.. > > Signed-off-by: Daniel

Re: [PATCH 10/14] crashdump/ppc: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on ppc arch even > if the functionality is not available on it. The functionality is available by reading device tree nodes in procfs.. > >

Re: [PATCH 06/14] crashdump/cris: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on cris arch even > if the functionality is not available on it. > > Signed-off-by: Daniel Kiper > --- >

Re: [PATCH 10/14] crashdump/ppc: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on ppc arch even > if the functionality is not available on it. The functionality is available by reading device tree nodes in procfs.. > >

Re: [PATCH 11/14] crashdump/ppc64: Add print_crashkernel_region_size() function

On 12/08/15 at 10:57pm, Daniel Kiper wrote: > Provide just print_crashkernel_region_size() stub. This way > we can properly build kexec utility on ppc64 arch even > if the functionality is not available on it. Ditto as ppc, you can read procfs file to get the values.. > > Signed-off-by: Daniel

Re: [PATCH 1/2] kexec: Set KEXEC_TYPE_CRASH before sanity_check_segment_list()

the flag beforehand. Looks good except a nitpick, see comments inline. Otherwise: Acked-by: Dave Young > > Signed-off-by: Xunlei Pang > --- > kernel/kexec.c | 13 - > 1 file changed, 8 insertions(+), 5 deletions(-) > > diff --git a/kernel/kexec.c b/kernel/kexec.c &

Re: [PATCH 1/2] kexec: Set KEXEC_TYPE_CRASH before sanity_check_segment_list()

the flag beforehand. Looks good except a nitpick, see comments inline. Otherwise: Acked-by: Dave Young <dyo...@redhat.com> > > Signed-off-by: Xunlei Pang <xlp...@redhat.com> > --- > kernel/kexec.c | 13 - > 1 file changed, 8 insertions(+), 5 deletions(-) >

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

On 11/20/15 at 12:55pm, Johannes Berg wrote: > On Sun, 2015-11-15 at 19:25 +0100, Stefan Lippers-Hollmann wrote: > > Hi > > > > On 2015-11-15, Dave Young wrote: > > > cfg80211 module prints a lot of messages like below. Actually > > > printing once is accep

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

On 11/20/15 at 12:55pm, Johannes Berg wrote: > On Sun, 2015-11-15 at 19:25 +0100, Stefan Lippers-Hollmann wrote: > > Hi > > > > On 2015-11-15, Dave Young wrote: > > > cfg80211 module prints a lot of messages like below. Actually > > > printing once is accep

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

On 11/15/15 at 09:38am, Joe Perches wrote: > On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote: > > cfg80211 module prints a lot of messages like below. Actually printing > > once is acceptable but sometimes it will print again and again, it looks > > very annoying. I

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

Hi, On 11/15/15 at 07:25pm, Stefan Lippers-Hollmann wrote: > Hi > > On 2015-11-15, Dave Young wrote: > > cfg80211 module prints a lot of messages like below. Actually printing > > once is acceptable but sometimes it will print again and again, it looks > > very annoy

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

On 11/15/15 at 09:38am, Joe Perches wrote: > On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote: > > cfg80211 module prints a lot of messages like below. Actually printing > > once is acceptable but sometimes it will print again and again, it looks > > very annoying. I

Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages

Hi, On 11/15/15 at 07:25pm, Stefan Lippers-Hollmann wrote: > Hi > > On 2015-11-15, Dave Young wrote: > > cfg80211 module prints a lot of messages like below. Actually printing > > once is acceptable but sometimes it will print again and again, it looks > > very annoy

[PATCH] wireless: change cfg80211 regulatory domain info as debug messages

) cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) The changes in this patch is to replace pr_info with pr_debug in function print_rd_rules and print_regdomain_info Signed-off-by: Dave Young --- net

[PATCH] wireless: change cfg80211 regulatory domain info as debug messages

) cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) The changes in this patch is to replace pr_info with pr_debug in function print_rd_rules and print_regdomain_info Signed-off-by: Dave Young <

Re: [PATCH v3 00/12] usb: early: add support for early printk through USB3 debug port

On 11/13/15 at 10:04am, Lu, Baolu wrote: > Hi Dave, > > On 11/12/2015 02:01 PM, Dave Young wrote: > >Hi, Baolu > > > >On 11/12/15 at 10:45am, Lu, Baolu wrote: > >>>Hi Dave, > >>> > >>>Which device are you testing with? This implem

Re: [PATCH v3 00/12] usb: early: add support for early printk through USB3 debug port

On 11/13/15 at 10:04am, Lu, Baolu wrote: > Hi Dave, > > On 11/12/2015 02:01 PM, Dave Young wrote: > >Hi, Baolu > > > >On 11/12/15 at 10:45am, Lu, Baolu wrote: > >>>Hi Dave, > >>> > >>>Which device are you testing with? This implem

Re: [PATCH v3 00/12] usb: early: add support for early printk through USB3 debug port

reate a verified-list and put those known-to-work devices > in it. > I have not got time to do more test. What infomation do you want? lsusb -v? > Thanks, > Baolu > > On 11/11/2015 10:25 AM, Dave Young wrote: > >Hi, > > > >On 11/11/15 at 09:32am, Lu, Baolu wrote: &

Re: [PATCH v3 00/12] usb: early: add support for early printk through USB3 debug port

reate a verified-list and put those known-to-work devices > in it. > I have not got time to do more test. What infomation do you want? lsusb -v? > Thanks, > Baolu > > On 11/11/2015 10:25 AM, Dave Young wrote: > >Hi, > > > >On 11/11/15 at 09:32am, Lu, Baolu wrote: &

<    5   6   7   8   9   10   11   12   13   14   >