public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Pingfan Liu <kernelfans@gmail.com>, dyoung@redhat.com
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Will Deacon <will.deacon@arm.com>,
	Nicolas Pitre <nico@linaro.org>,
	Chao Fan <fanc.fnst@cn.fujitsu.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] x86/boot/KASLR: skip the specified crashkernel reserved region
Date: Fri, 22 Mar 2019 16:34:19 +0800	[thread overview]
Message-ID: <20190322083419.GB18740@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190322075259.GA18740@MiWiFi-R3L-srv>

On 03/22/19 at 03:52pm, Baoquan He wrote:
> On 03/22/19 at 03:43pm, Pingfan Liu wrote:
> > > > +/* parse crashkernel=x@y option */
> > > > +static void mem_avoid_crashkernel_simple(char *option)
> > >
> > > Chao ever mentioned this, I want to ask again, why does it has to be
> > > xxx_simple()?
> > >
> > Seems that I had replied Chao's question in another email. The naming
> > follows the function parse_crashkernel_simple(), as the notes above
>                        ~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Sorry, I don't get.  typo?

OK, I misunderstood it. We do have parse_crashkernel_simple() to handle 
crashkernel=size[@offset] case, to differente with other complicated
cases, like crashkernel=size,[high|low],

Then I am fine with this naming. Soryy about the noise.

By the way, do you think if we should take care of this case:
crashkernel=<range1>:<size1>[,<range2>:<size2>,...][@offset]

It can also specify @offset. Not sure if it's too complicated, you may
have a investigation.

These two cases have dependency on your crashkernel=X bug fix patch.
The current code only allow crashkernel= to reserve under 896MB. I
noticed Boris has agreed on the solution. Maybe you can repost a new
version based on the discussion.

http://lkml.kernel.org/r/1548047768-7656-1-git-send-email-kernelfans@gmail.com
[PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

Thanks
Baoquan

> 
> > the definition
> > /*
> >  * That function parses "simple" (old) crashkernel command lines like
> >  *
> >  * crashkernel=size[@offset]
> 
> Hmm, should only crashkernel=size@offset be cared? crashkernel=size will
> auto finding a place to reserve, and that is after KASLR.
> 
> >  *
> >  * It returns 0 on success and -EINVAL on failure.
> >  */
> > static int __init parse_crashkernel_simple(char *cmdline,
> > 
> > Do you have alternative suggestion?
> > 
> > > Except of these, patch looks good to me. It's a nice catch, and only
> > > need a simple fix based on the current code.
> > >
> > Thank you for the kindly review.
> > 
> > Regards,
> > Pingfan
> > 
> > > Thanks
> > > Baoquan
> > >
> > > > +{
> > > > +     unsigned long long crash_size, crash_base;
> > > > +     char *cur = option;
> > > > +
> > > > +     crash_size = memparse(option, &cur);
> > > > +     if (option == cur)
> > > > +             return;
> > > > +
> > > > +     if (*cur == '@') {
> > > > +             option = cur + 1;
> > > > +             crash_base = memparse(option, &cur);
> > > > +             if (option == cur)
> > > > +                     return;
> > > > +             mem_avoid[MEM_AVOID_CRASHKERNEL].start = crash_base;
> > > > +             mem_avoid[MEM_AVOID_CRASHKERNEL].size = crash_size;
> > > > +     }
> > > > +}
> > > >
> > > >  static void handle_mem_options(void)
> > > >  {
> > > > @@ -250,7 +270,7 @@ static void handle_mem_options(void)
> > > >       u64 mem_size;
> > > >
> > > >       if (!strstr(args, "memmap=") && !strstr(args, "mem=") &&
> > > > -             !strstr(args, "hugepages"))
> > > > +             !strstr(args, "hugepages") && !strstr(args, "crashkernel="))
> > > >               return;
> > > >
> > > >       tmp_cmdline = malloc(len + 1);
> > > > @@ -286,6 +306,8 @@ static void handle_mem_options(void)
> > > >                               goto out;
> > > >
> > > >                       mem_limit = mem_size;
> > > > +             } else if (strstr(param, "crashkernel")) {
> > > > +                     mem_avoid_crashkernel_simple(val);
> > > >               }
> > > >       }
> > > >
> > > > @@ -414,7 +436,7 @@ static void mem_avoid_init(unsigned long input, unsigned long input_size,
> > > >
> > > >       /* We don't need to set a mapping for setup_data. */
> > > >
> > > > -     /* Mark the memmap regions we need to avoid */
> > > > +     /* Mark the regions we need to avoid */
> > > >       handle_mem_options();
> > > >
> > > >  #ifdef CONFIG_X86_VERBOSE_BOOTUP
> > > > --
> > > > 2.7.4
> > > >

  reply	other threads:[~2019-03-22  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  4:19 [PATCHv2] x86/boot/KASLR: skip the specified crashkernel reserved region Pingfan Liu
2019-03-20  0:25 ` Baoquan He
2019-03-22  7:43   ` Pingfan Liu
2019-03-22  7:52     ` Baoquan He
2019-03-22  8:34       ` Baoquan He [this message]
2019-03-25  5:56         ` Pingfan Liu
2019-03-29  5:45         ` Pingfan Liu
2019-03-29  6:27           ` Baoquan He
2019-03-29  7:25             ` Pingfan Liu
2019-03-29  7:34               ` Baoquan He
2019-03-29 10:00                 ` Pingfan Liu
2019-03-29 10:12                   ` Baoquan He
2019-03-20  1:23 ` Chao Fan
2019-03-21  6:37 ` Chao Fan
2019-03-22  7:47   ` Pingfan Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190322083419.GB18740@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=fanc.fnst@cn.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=kernelfans@gmail.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nico@linaro.org \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox