From: Hugh Dickins <hughd@google.com>
To: yong w <yongw.pur@gmail.com>
Cc: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
cgel.zte@gmail.com, kirill@shutemov.name, songliubraving@fb.com,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
yang.yang29@zte.com.cn, wang.yong12@zte.com.cn
Subject: Re: [PATCH] memfd: fix F_SEAL_WRITE after shmem huge page allocated
Date: Wed, 2 Mar 2022 11:52:58 -0800 (PST) [thread overview]
Message-ID: <5bacaf7a-dc6b-9435-e6a7-377b8f9d67e@google.com> (raw)
In-Reply-To: <CAOH5QeA4w+CKW+K58k3c5pRWdkx6uT5ouyQ6hepMd1wKF51mcw@mail.gmail.com>
On Wed, 2 Mar 2022, yong w wrote:
> Hello,
> this patch does not apply to the 4.19 kernel.
> Is it necessary to make corresponding patches for each stable version?
I expect there will be three variants (if it's worth porting back
to older stables: you make it clear that you do want 4.19, thanks):
one for xarray kernels, one for radix-tree kernels, and one for
old shmem.c-not-memfd.c kernels; or perhaps I've missed a variant.
Once this patch has gone to Linus, then been picked up by GregKH
for recent kernels, I'll respond to the mail when it goes into his
tree to provide the others (or maybe I won't bother with the oldest).
We didn't research a "Fixes:" tag for the patch, so Greg may quietly
stop at the oldest kernel to which the patch does not apply, instead
of sending out explicit pleas for substitute patches as he usually does;
but I'll know anyway when the recent ones go in, and respond then.
Hugh
prev parent reply other threads:[~2022-03-02 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 7:37 [PATCH linux-next] Fix shmem huge page failed to set F_SEAL_WRITE attribute problem cgel.zte
2022-02-15 22:12 ` Andrew Morton
2022-02-16 6:57 ` CGEL
2022-02-17 1:00 ` Mike Kravetz
2022-02-17 1:25 ` Hugh Dickins
2022-02-17 13:43 ` Matthew Wilcox
2022-02-27 3:00 ` Hugh Dickins
2022-02-27 5:20 ` [PATCH] memfd: fix F_SEAL_WRITE after shmem huge page allocated Hugh Dickins
2022-03-02 1:11 ` yong w
2022-03-02 19:52 ` Hugh Dickins [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=5bacaf7a-dc6b-9435-e6a7-377b8f9d67e@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=songliubraving@fb.com \
--cc=wang.yong12@zte.com.cn \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
--cc=yongw.pur@gmail.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