From: Sasha Levin <sashal@kernel.org>
To: Jann Horn <jannh@google.com>
Cc: stable <stable@vger.kernel.org>, stable-commits@vger.kernel.org
Subject: Re: Patch "mm/mmu_notifier: fix mmget() assert in __mmu_interval_notifier_insert" has been added to the 5.8-stable tree
Date: Mon, 26 Oct 2020 10:21:58 -0400 [thread overview]
Message-ID: <20201026142158.GI4060117@sasha-vm> (raw)
In-Reply-To: <CAG48ez3gb8E34ePqSmmqhadfLMsLFiNhX=fmCRZKNfSQztXcMQ@mail.gmail.com>
On Mon, Oct 26, 2020 at 10:25:08AM +0100, Jann Horn wrote:
>On Mon, Oct 26, 2020 at 6:30 AM Sasha Levin <sashal@kernel.org> wrote:
>>
>> This is a note to let you know that I've just added the patch titled
>>
>> mm/mmu_notifier: fix mmget() assert in __mmu_interval_notifier_insert
>>
>> 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:
>> mm-mmu_notifier-fix-mmget-assert-in-__mmu_interval_n.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.
>
>This patch has no reason to go into the stable trees. It just makes an
>assertion stricter (mm_users>0 implies mm_count>0). It only has an
>effect if your kernel is horrendously broken anyway.
>
>Please take it out of the stable queue.
Will do.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-10-26 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201026053052.9CB982085B@mail.kernel.org>
2020-10-26 9:25 ` Patch "mm/mmu_notifier: fix mmget() assert in __mmu_interval_notifier_insert" has been added to the 5.8-stable tree Jann Horn
2020-10-26 14:21 ` Sasha Levin [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=20201026142158.GI4060117@sasha-vm \
--to=sashal@kernel.org \
--cc=jannh@google.com \
--cc=stable-commits@vger.kernel.org \
--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