From: Greg KH <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: akpm@linux-foundation.org, cgel.zte@gmail.com,
kirill@shutemov.name, mike.kravetz@oracle.com,
songliubraving@fb.com, torvalds@linux-foundation.org,
wang.yong12@zte.com.cn, willy@infradead.org,
yang.yang29@zte.com.cn, zealci@zte.com.cn, yongw.pur@gmail.com,
stable@vger.kernel.org
Subject: Re: Patch "memfd: fix F_SEAL_WRITE after shmem huge page allocated" has been added to the 5.4-stable tree
Date: Sun, 6 Mar 2022 11:47:47 +0100 [thread overview]
Message-ID: <YiSRUwgyRot6f2io@kroah.com> (raw)
In-Reply-To: <d169b785-1486-7c3d-7843-e2c23870a048@google.com>
On Sun, Mar 06, 2022 at 01:09:16AM -0800, Hugh Dickins wrote:
> On Sat, 5 Mar 2022, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > memfd: fix F_SEAL_WRITE after shmem huge page allocated
> >
> > to the 5.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:
> > memfd-fix-f_seal_write-after-shmem-huge-page-allocated.patch
> > and it can be found in the queue-5.4 subdirectory.
>
> Thank you for adding that patch to 5.16, 5.15, 5.10 and 5.4:
> please accept the substitute patch below for 4.14 and 4.9 - thanks.
> A different patch for 4.19 has been sent separately.
All now queued up, thanks for the backports!
greg k-h
prev parent reply other threads:[~2022-03-06 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1646512773164108@kroah.com>
2022-03-06 9:05 ` Patch "memfd: fix F_SEAL_WRITE after shmem huge page allocated" has been added to the 5.4-stable tree Hugh Dickins
2022-03-06 9:09 ` Hugh Dickins
2022-03-06 10:47 ` Greg KH [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=YiSRUwgyRot6f2io@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=mike.kravetz@oracle.com \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wang.yong12@zte.com.cn \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
--cc=yongw.pur@gmail.com \
--cc=zealci@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.