From: Baoquan He <bhe@redhat.com>
To: Masayoshi Mizuma <msys.mizuma@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"kirill@shutemov.name Thomas Gleixner" <tglx@linutronix.de>,
x86@kernel.org, Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, Chao Fan <fanc.fnst@cn.fujitsu.com>
Subject: Re: [PATCH v2] x86/mm: Adjust the padding size for KASLR
Date: Sat, 16 Feb 2019 22:15:49 +0800 [thread overview]
Message-ID: <20190216141549.GA2007@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190214173945.utbawbfbdjkw7dif@gabell>
On 02/14/19 at 12:39pm, Masayoshi Mizuma wrote:
> > Another thing is for the 3rd part, I also queued several patches in my
> > local branch, they are code bug fix patches, and several clean up
> > patches suggested by Ingo and Kirill. They can be found here:
> >
> > https://github.com/baoquan-he/linux/commits/kaslar-mm-bug-fix
> >
> > In my local patches, Ingo suggested opening code get_padding(), and
> > about the SGI UV bug, he suggested adding another function to calculate
> > the needed size for the direct mapping region. So I am wondering if you
> > can rebase the part 3 on top of it, or you add a new function to
> > calculate the size for the direct mapping region so that I can rebase on
> > top of your patch and reuse it.
> >
> > What do you think about it?
>
> OK, I will rebase my patches on top of your patch.
> Could you add CCing me when you post your patches?
The patchset has been sent out and added you in the CC list, please feel
free to check.
Thanks
Baoquan
prev parent reply other threads:[~2019-02-16 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 1:31 [PATCH v2] x86/mm: Adjust the padding size for KASLR Masayoshi Mizuma
2019-02-14 10:12 ` Baoquan He
2019-02-14 17:39 ` Masayoshi Mizuma
2019-02-16 14:15 ` Baoquan He [this message]
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=20190216141549.GA2007@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.mizuma@jp.fujitsu.com \
--cc=mingo@redhat.com \
--cc=msys.mizuma@gmail.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).