From: Greg KH <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: keno@juliacomputing.com, akpm@linux-foundation.org,
gthelen@google.com, hughd@google.com, keescook@chromium.org,
kirill.shutemov@linux.intel.com, luto@kernel.org,
mhocko@suse.com, npiggin@gmail.com, oleg@redhat.com,
torvalds@linux-foundation.org, w@1wt.eu, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp" has been added to the 4.4-stable tree
Date: Mon, 10 Apr 2017 18:04:51 +0200 [thread overview]
Message-ID: <20170410160451.GA5425@kroah.com> (raw)
In-Reply-To: <1491839297.2409.51.camel@decadent.org.uk>
On Mon, Apr 10, 2017 at 04:48:17PM +0100, Ben Hutchings wrote:
> On Mon, 2017-04-10 at 17:09 +0200, gregkh@linuxfoundation.org wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > ����mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp
> >
> > to the 4.4-stable tree which can be found at:
> > ����http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > �����mm-huge_memory.c-respect-foll_force-foll_cow-for-thp.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From 303681d5d538d81b5e23754515202b5b9febd2e9 Mon Sep 17 00:00:00 2001
> > From: Keno Fischer <keno@juliacomputing.com>
> > Date: Tue, 24 Jan 2017 15:17:48 -0800
> > Subject: mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp
> >
> > From: Keno Fischer <keno@juliacomputing.com>
> >
> > commit 8310d48b125d19fcd9521d83b8293e63eb1646aa upstream.
> [...]
> > �- Drop change to follow_devmap_pmd()
> > �- pmd_dirty() is not available; check the page flags as in older
> > ���backports of can_follow_write_pte()
> > �- Adjust context]
> [...]
>
> Aside from the fact that I got this backport wrong, I don't think you
> need the main change here. In 4.4, all arches that define
> CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE also define pmd_dirty().
Hm, ok, but Keno said people are still hitting this issue on 4.4-stable.
So, what should I do? I'll go drop this from my queue for now, but as I
don't know what to do to test this, I'm at a loss...
thanks,
greg k-h
next prev parent reply other threads:[~2017-04-10 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:09 Patch "mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp" has been added to the 4.4-stable tree gregkh
2017-04-10 15:34 ` Michal Hocko
2017-04-10 16:05 ` Greg KH
2017-04-10 16:13 ` Michal Hocko
2017-04-10 15:48 ` Ben Hutchings
2017-04-10 16:04 ` Greg KH [this message]
2017-04-10 16:13 ` Michal Hocko
2017-04-10 16:21 ` Greg KH
2017-04-10 18:10 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 14:46 gregkh
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=20170410160451.GA5425@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=gthelen@google.com \
--cc=hughd@google.com \
--cc=keescook@chromium.org \
--cc=keno@juliacomputing.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=luto@kernel.org \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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).