Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-05-23 Thread Pingfan Liu
Matthias, ping? Any suggestions? Thanks, Pingfan On Thu, May 2, 2019 at 2:22 PM Pingfan Liu wrote: > > On Thu, Apr 25, 2019 at 4:20 PM Pingfan Liu wrote: > > > > On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger wrote: > > > > > > > > [...] > > > > @@ -139,6 +141,8 @@ static int __init

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-05-02 Thread Pingfan Liu
On Thu, Apr 25, 2019 at 4:20 PM Pingfan Liu wrote: > > On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger wrote: > > > > > [...] > > > @@ -139,6 +141,8 @@ static int __init parse_crashkernel_simple(char > > > *cmdline, > > > pr_warn("crashkernel: unrecognized char: %c\n", *cur); > >

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-28 Thread Dave Young
On 04/29/19 at 12:48pm, Pingfan Liu wrote: > On Mon, Apr 29, 2019 at 11:04 AM Pingfan Liu wrote: > > > > On Sun, Apr 28, 2019 at 4:37 PM Dave Young wrote: > > > > > > On 04/25/19 at 04:20pm, Pingfan Liu wrote: > > > > On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger > > > > wrote: > > > > > >

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-28 Thread Pingfan Liu
On Mon, Apr 29, 2019 at 11:04 AM Pingfan Liu wrote: > > On Sun, Apr 28, 2019 at 4:37 PM Dave Young wrote: > > > > On 04/25/19 at 04:20pm, Pingfan Liu wrote: > > > On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger > > > wrote: > > > > > > > > > > > [...] > > > > > @@ -139,6 +141,8 @@ static int

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-28 Thread Pingfan Liu
On Sun, Apr 28, 2019 at 4:37 PM Dave Young wrote: > > On 04/25/19 at 04:20pm, Pingfan Liu wrote: > > On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger wrote: > > > > > > > > [...] > > > > @@ -139,6 +141,8 @@ static int __init parse_crashkernel_simple(char > > > > *cmdline, > > > >

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-28 Thread Dave Young
On 04/25/19 at 04:20pm, Pingfan Liu wrote: > On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger wrote: > > > > > [...] > > > @@ -139,6 +141,8 @@ static int __init parse_crashkernel_simple(char > > > *cmdline, > > > pr_warn("crashkernel: unrecognized char: %c\n", *cur); > > >

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-25 Thread Pingfan Liu
On Wed, Apr 24, 2019 at 4:31 PM Matthias Brugger wrote: > > [...] > > @@ -139,6 +141,8 @@ static int __init parse_crashkernel_simple(char > > *cmdline, > > pr_warn("crashkernel: unrecognized char: %c\n", *cur); > > return -EINVAL; > > } > > + if (*crash_size

Re: [PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-24 Thread Matthias Brugger
On 24/04/2019 08:33, Pingfan Liu wrote: > At present, both return and crash_size should be checked to guarantee the > success of parse_crashkernel(). > > Take a close look at the cases, which causes crash_size=0. Beside syntax > error, three cases cause parsing to get crash_size=0. > -1st. in

[PATCHv2] kernel/crash: make parse_crashkernel()'s return value more indicant

2019-04-24 Thread Pingfan Liu
At present, both return and crash_size should be checked to guarantee the success of parse_crashkernel(). Take a close look at the cases, which causes crash_size=0. Beside syntax error, three cases cause parsing to get crash_size=0. -1st. in parse_crashkernel_mem(), the demanded crash size is