From: Chas Williams <3chas3@gmail.com>
To: yskoh@mellanox.com
Cc: stable@dpdk.org, mark.rutland@arm.com, Chas Williams <chas3@att.com>
Subject: Re: [dpdk-stable] [PATCH][v4.9.y] Fixes: 3c226c637b69 ("mm: numa: avoid waiting on freed migrated pages")
Date: Wed, 5 Sep 2018 05:00:38 -0400 [thread overview]
Message-ID: <CAG2-Gk=ns5qEFTZCMNC4agHzAsQ0ynK4STdR+1GtFs=sV+8gUw@mail.gmail.com> (raw)
In-Reply-To: <2310432A-D93A-4D6A-B3F3-8C885F95D819@mellanox.com>
On Wed, Sep 5, 2018 at 2:34 AM Yongseok Koh <yskoh@mellanox.com> wrote:
>
> > On Sep 4, 2018, at 5:51 PM, Chas Williams <3chas3@gmail.com> 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(-)
> >
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index 9efe88ef9702..e4c6c3edaf6a 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
>
> Looks like a kernel patch has been sent to DPDK community. ;-)
>
Well they both start stable... :) Thanks for the heads up!
>
> Thanks,
> Yongseok
>
> > @@ -1259,12 +1259,12 @@ int do_huge_pmd_numa_page(struct fault_env *fe,
> pmd_t pmd)
> >
> > /* Migration could have started since the pmd_trans_migrating
> check */
> > if (!page_locked) {
> > + page_nid = -1;
> > if (!get_page_unless_zero(page))
> > goto out_unlock;
> > spin_unlock(fe->ptl);
> > wait_on_page_locked(page);
> > put_page(page);
> > - page_nid = -1;
> > goto out;
> > }
> >
> > --
> > 2.14.4
> >
>
>
prev parent reply other threads:[~2018-09-05 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 0:51 Chas Williams
2018-09-05 6:34 ` Yongseok Koh
2018-09-05 9:00 ` Chas Williams [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='CAG2-Gk=ns5qEFTZCMNC4agHzAsQ0ynK4STdR+1GtFs=sV+8gUw@mail.gmail.com' \
--to=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=mark.rutland@arm.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.com \
/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).