public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	aarcange@redhat.com, akpm@linux-foundation.org,
	kirill.shutemov@linux.intel.com, mike.kravetz@oracle.com,
	songliubraving@fb.com, torvalds@linux-foundation.org,
	stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "khugepaged: khugepaged_test_exit() check mmget_still_valid()" has been added to the 5.8-stable tree
Date: Sat, 22 Aug 2020 17:20:53 -0400	[thread overview]
Message-ID: <20200822212053.GE8670@sasha-vm> (raw)
In-Reply-To: <alpine.LSU.2.11.2008211739460.9564@eggly.anvils>

On Fri, Aug 21, 2020 at 06:26:15PM -0700, Hugh Dickins wrote:
>On Wed, 19 Aug 2020, Greg KH wrote:
>> On Wed, Aug 19, 2020 at 06:32:26AM -0700, Hugh Dickins wrote:
>> > On Wed, 19 Aug 2020, gregkh@linuxfoundation.org wrote:
>> > >
>> > > This is a note to let you know that I've just added the patch titled
>> > >
>> > >     khugepaged: khugepaged_test_exit() check mmget_still_valid()
>> > >
>> > > to the 5.8-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:
>> > >      khugepaged-khugepaged_test_exit-check-mmget_still_valid.patch
>> > > and it can be found in the queue-5.8 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.
>> >
>> > Please hold this one back for the moment: we shall want it, but syzbot
>> > detected one place where it can lead to a VM_BUG_ON_MM().  The fix to
>> > that is currently in Andrew's tree, but not yet in Linus's - when it
>> > gets there, I'll send you its git commit id in reply to this mail.
>> >
>> > This patch failed to apply to earlier releases: I'll send the fixup for
>> > those at that time.  (Fixups for another patch to follow later today.)
>>
>> Now dropped, thanks!
>
>f3f99d63a815 khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
>has now reached Linus's tree, so will reach your tree when you next pull.
>
>When that one is ready, please reinstate this commit that we held back:
>bbe98f9cadff khugepaged: khugepaged_test_exit() check mmget_still_valid()
>
>The mmap_sem->mmap_lock change means I must then send you a backport of
>bbe98f9cadff for 5.7, 5.4, 4.19, 4.14, 4.9: one backport will do for all
>of those, and f3f99d63a815 should cherry-pick cleanly into them all.
>
>But you also marked bbe98f9cadff for 4.4: I had not expected that,
>but I think you're right - for whatever reason (probably inertia,
>it was tiresome because khugepaged.c got split from huge_memory.c),
>4.4 lacks a backport of 59ea6d06cfa9 (though it does have the commit
>that depended on), and backports of these two will serve just as well
>to fix what it was required to fix: I'll send them too.
>
>Thanks: I'm sorry that this is all so confusing,
>kudos to syzbot for catching my error as quickly as it did.

I've followed your instructions and backported the patches:

bbe98f9cadff ("khugepaged: khugepaged_test_exit() check
mmget_still_valid()") - to all branches.
f3f99d63a815 ("khugepaged: adjust VM_BUG_ON_MM() in
__khugepaged_enter()") - to all branches.
59ea6d06cfa9 ("coredump: fix race condition between collapse_huge_page()
and core dumping") - for 4.4.

Thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2020-08-22 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1597841669128213@kroah.com>
2020-08-19 13:32 ` Patch "khugepaged: khugepaged_test_exit() check mmget_still_valid()" has been added to the 5.8-stable tree Hugh Dickins
2020-08-19 13:53   ` Greg KH
2020-08-22  1:26     ` Hugh Dickins
2020-08-22 21:20       ` Sasha Levin [this message]
2020-08-23  2:16         ` Hugh Dickins
2020-08-24 15:12           ` Hugh Dickins
2020-08-26 18:53             ` Hugh Dickins
2020-08-26 21:46               ` Sasha Levin
2020-08-26 21:54                 ` Hugh Dickins
2020-08-24 15:29           ` Sasha Levin

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=20200822212053.GE8670@sasha-vm \
    --to=sashal@kernel.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=mike.kravetz@oracle.com \
    --cc=songliubraving@fb.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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