From: Nathan Chancellor <natechancellor@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Chas Williams <3chas3@gmail.com>,
stable@vger.kernel.org, mark.rutland@arm.com,
Chas Williams <chas3@att.com>
Subject: Re: [PATCH v4.9.y] Fixes: Commit 3c226c637b69 ("mm: numa: avoid waiting on freed migrated pages")
Date: Wed, 5 Sep 2018 02:18:13 -0700 [thread overview]
Message-ID: <20180905091813.GA26736@flashbox> (raw)
In-Reply-To: <20180905090515.GA31571@kroah.com>
On Wed, Sep 05, 2018 at 11:05:15AM +0200, Greg KH wrote:
> On Wed, Sep 05, 2018 at 04:58:52AM -0400, Chas Williams wrote:
> > From: Chas Williams <chas3@att.com>
> >
> > Commit 3c226c637b69 ("mm: numa: avoid waiting on freed migrated pages")
> > was an incomplete backport of the upstream commit. It is necessary to
> > always reset page_nid before attempting any early exit.
> > ---
> > mm/huge_memory.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> </formletter>
This is an issue with the 4.9 tree, not mainline. The hash is
incorrect but the problem appears valid.
Compare:
2aa6d036b716 ("mm: numa: avoid waiting on freed migrated pages")
from v4.9.36 with the upstream commit from 4.12:
3c226c637b69 ("mm: numa: avoid waiting on freed migrated pages")
It is missing this diff.
The original commit conflicted due to lack of commit 82b0f8c39a38 ("mm:
join struct fault_env and vm_fault") in 4.9 so it wasn't a clean
application, must have just gotten lost in the noise.
Cheers,
Nathan
next prev parent reply other threads:[~2018-09-05 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 8:58 [PATCH v4.9.y] Fixes: Commit 3c226c637b69 ("mm: numa: avoid waiting on freed migrated pages") Chas Williams
2018-09-05 9:05 ` Greg KH
2018-09-05 9:18 ` Nathan Chancellor [this message]
[not found] ` <CAG2-Gkn69EFYV2XwBraSt2nPwxRh2i+vV-XRfzxsZH2_7cORhg@mail.gmail.com>
2018-09-05 9:32 ` Greg Kroah-Hartman
2018-09-05 9:41 ` Chas Williams
2018-09-05 10:07 ` Greg Kroah-Hartman
2018-09-05 14:43 ` [PATCH] Fixes: Commit 2aa6d036b716 " Chas Williams
2018-09-05 15:02 ` Greg KH
2018-09-05 17:46 ` Chas Williams
2018-09-06 15:09 ` [PATCH][4.9.y] " Chas Williams
2018-09-06 15:10 ` [PATCH][v3.18.y] Fixes: Commit 86af955d02bb " Chas Williams
2018-09-06 15:11 ` [PATCH][v4.4.y] Fixes: Commit cdbf92675fad " Chas Williams
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=20180905091813.GA26736@flashbox \
--to=natechancellor@gmail.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=gregkh@linuxfoundation.org \
--cc=mark.rutland@arm.com \
--cc=stable@vger.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