From: Luming Yu <luming.yu@gmail.com>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: "Lutomirski, Andy" <luto@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Han, Jing1" <jing1.han@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Questions on patch set: x86/fault: #PF improvements, mostly related to USER bit
Date: Thu, 5 Aug 2021 09:31:46 +0800 [thread overview]
Message-ID: <CAJRGBZxncgsMP4qu+YbVgUaTBt=Uxp=2XPvAg1-QAvh+0p=Z_Q@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB2540671F57AA4E16782FB502F9F29@DM6PR11MB2540.namprd11.prod.outlook.com>
try again.
On Thu, Aug 5, 2021 at 9:28 AM Yu, Luming <luming.yu@intel.com> wrote:
>
> Cc’ gregkh
>
>
>
> It would be nice if we can see the patch set available in 5.10-xx stable tree.
>
> But Jing’s finding on Linus tree about the commit seemed to indicate the commit id
>
> Of the patch and the commit log and patch could not lead to the revision of arch/x86/mm/fault.c
>
> By the patch of the commit itself. So it is hard for Jing to do a clean back port with the inconsistent git log.
>
>
>
> BR
>
> Luming
>
>
>
> From: Han, Jing1 <jing1.han@intel.com>
> Sent: Wednesday, August 4, 2021 8:44 PM
> To: Lutomirski, Andy <luto@kernel.org>
> Cc: Yu, Luming <luming.yu@intel.com>
> Subject: Questions on patch set: x86/fault: #PF improvements, mostly related to USER bit
>
>
>
> Hi Luto,
>
>
>
> When trying to backport your patch from upstream to 5.10.18: https://lore.kernel.org/lkml/cover.1612924255.git.luto@kernel.org/
>
> I find something wrong with this commit: 2cc624b0a7e68ba8957b18600181f7d5b0f3e1b6 x86/fault: Split the OOPS code out from no_context()
>
> The code after this commit in upstream does not align with the code showed in the patch.
>
> To be exactly, the function name is “no_context” in the patch, while it is “kernelmode_fixup_or_oops” in upstream code.
>
> Could you please check what is the problem?
>
> (Another confusion is, there are 14 patches total in the link above, but 13 patches in upstream code.)
>
>
>
> I do the backport it because it is preparation for CET, I will backport CET to 5.10.18 when it is upstreamed as there is customer request.
>
> Will you provide the backport patch to 5.10 stable branch?
>
>
>
> Thank you very much,
>
> Jing
>
>
parent reply other threads:[~2021-08-05 1:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DM6PR11MB2540671F57AA4E16782FB502F9F29@DM6PR11MB2540.namprd11.prod.outlook.com>]
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='CAJRGBZxncgsMP4qu+YbVgUaTBt=Uxp=2XPvAg1-QAvh+0p=Z_Q@mail.gmail.com' \
--to=luming.yu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jing1.han@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=luto@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).