From: Wang Yugui <wangyugui@e16-tech.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Jann Horn <jannh@google.com>
Subject: Re: should stable 6.1.y include 6c21e066f925 mm/mempolicy: Take VMA lock before replacing policy?
Date: Tue, 01 Aug 2023 17:12:31 +0800 [thread overview]
Message-ID: <20230801171226.1330.409509F4@e16-tech.com> (raw)
In-Reply-To: <2023080144-coasting-decathlon-74f1@gregkh>
Hi,
> On Tue, Aug 01, 2023 at 04:21:05PM +0800, Wang Yugui wrote:
> > Hi,
> >
> > should stable 6.1.y include
> > 6c21e066f925 mm/mempolicy: Take VMA lock before replacing policy
> > ?
>
> Did you test it and see if it works? Why do you think it is needed in
> 6.1.y when the "Fixes:" tag references a commit that is in 6.4 only?
> Is the tag incorrect?
Sorry that it should not be included in stable 6.1.y.
I checked all mm-patches of 6.1.36-6.1.42 again.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/08/01
prev parent reply other threads:[~2023-08-01 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 8:21 should stable 6.1.y include 6c21e066f925 mm/mempolicy: Take VMA lock before replacing policy? Wang Yugui
2023-08-01 8:42 ` Greg KH
2023-08-01 9:12 ` Wang Yugui [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=20230801171226.1330.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.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