From: Baoquan He <bhe@redhat.com>
To: Fengguang Wu <lkp@intel.com>
Cc: dave.jiang@intel.com, keescook@chromium.org,
Yinghai Lu <yinghai@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
tglx@linutronix.de, kbuild-all@01.org, hpa@zytor.com,
dan.j.williams@intel.com, Borislav Petkov <bp@suse.de>,
dyoung@redhat.com, mingo@kernel.org
Subject: Re: [kbuild-all] [RFC PATCH] KASLR: mem_avoid_memmap_index can be static
Date: Mon, 24 Apr 2017 17:08:24 +0800 [thread overview]
Message-ID: <20170424090824.GA6089@x1> (raw)
In-Reply-To: <20170424090428.sa7boyuhkyklqxv5@wfg-t540p.sh.intel.com>
On 04/24/17 at 05:04pm, Fengguang Wu wrote:
> Hi Baoquan,
>
> On Mon, Apr 24, 2017 at 05:00:40PM +0800, Baoquan He wrote:
> > Hi Fengguang,
> >
> > Thanks for pointing it out!
> >
> > I am fine with defining mem_avoid_memmap_index it as static variable.
> > While Liyang suggested using a local static inside mem_avoid_memmap,
> > then mem_avoid_memmap_index is not needed any more. Do you think it's OK
> > to you?
>
> Yes, that'd be a better solution. It's a robot generated patch and is
> open for optimization or correction.
Oh, the tip robot is so great! Thanks for telling, then let me repost.
>
> > On 04/24/17 at 04:48pm, kbuild test robot wrote:
> > >
> > > Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> > > ---
> > > kaslr.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/kaslr.c
> > > index 6649ecd..7190d35 100644
> > > --- a/arch/x86/boot/compressed/kaslr.c
> > > +++ b/arch/x86/boot/compressed/kaslr.c
> > > @@ -75,7 +75,7 @@ struct mem_vector {
> > > #define MAX_MEMMAP_REGIONS 4
> > >
> > > static bool memmap_too_large;
> > > -int mem_avoid_memmap_index;
> > > +static int mem_avoid_memmap_index;
> > > extern unsigned long get_cmd_line_ptr(void);
> > >
> > >
> > _______________________________________________
> > kbuild-all mailing list
> > kbuild-all@lists.01.org
> > https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2017-04-24 9:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 2:40 [PATCH v2 0/3] Handle memmap and mem kernel options in boot stage kaslr Baoquan He
2017-04-24 2:40 ` [PATCH v2 1/3] KASLR: Parse all memmap entries in cmdline Baoquan He
2017-04-24 8:00 ` Dou Liyang
2017-04-24 9:09 ` Baoquan He
2017-04-24 8:48 ` kbuild test robot
2017-04-24 8:48 ` [RFC PATCH] KASLR: mem_avoid_memmap_index can be static kbuild test robot
2017-04-24 9:00 ` Baoquan He
2017-04-24 9:04 ` [kbuild-all] " Fengguang Wu
2017-04-24 9:08 ` Baoquan He [this message]
2017-04-24 2:40 ` [PATCH v2 2/3] KASLR: Handle memory limit specified by memmap and mem option Baoquan He
2017-04-24 19:10 ` Kees Cook
2017-04-24 2:40 ` [PATCH v2 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description Baoquan He
2017-04-24 3:53 ` Dou Liyang
2017-04-24 6:54 ` Baoquan He
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=20170424090824.GA6089@x1 \
--to=bhe@redhat.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.