From: Greg KH <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: yangerkun <yangerkun@huawei.com>,
sfrench@samba.org, pc@manguebit.com, lsahlber@redhat.com,
sprasad@microsoft.com, tom@talpey.com,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
stable@kernel.org, nspmangalore@gmail.com, ematsumiya@suse.de,
yangerkun@huaweicloud.com
Subject: Re: [PATCH v3] cifs: fix pagecache leak when do writepages
Date: Thu, 11 Sep 2025 18:38:56 +0200 [thread overview]
Message-ID: <2025091139-control-reshape-638a@gregkh> (raw)
In-Reply-To: <1955891.1757608316@warthog.procyon.org.uk>
On Thu, Sep 11, 2025 at 05:31:56PM +0100, David Howells wrote:
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > Yes, please include the info as to why this is not a backport from
> > upstream, and why it can only go into this one specific tree and get the
> > developers involved to agree with this.
>
> Backporting the massive amount of changes to netfslib, fscache, cifs, afs, 9p,
> ceph and nfs would kind of diminish the notion that this is a stable
> kernel;-).
Ok, then that's a good reason why, let's document that!
next prev parent reply other threads:[~2025-09-11 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 3:01 [PATCH v3] cifs: fix pagecache leak when do writepages Yang Erkun
2025-09-11 3:22 ` yangerkun
2025-09-11 10:53 ` Greg KH
2025-09-11 11:09 ` yangerkun
2025-09-11 11:17 ` Greg KH
2025-09-11 11:25 ` yangerkun
2025-09-11 11:40 ` Shyam Prasad N
2025-09-11 15:45 ` Enzo Matsumiya
2025-09-11 16:40 ` Steve French
2025-09-11 17:10 ` Greg KH
2025-09-11 16:31 ` David Howells
2025-09-11 16:38 ` Greg KH [this message]
2025-09-11 16:25 ` David Howells
2025-09-11 18:17 ` Matthew Wilcox
2025-09-12 1:12 ` yangerkun
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=2025091139-control-reshape-638a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dhowells@redhat.com \
--cc=ematsumiya@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=nspmangalore@gmail.com \
--cc=pc@manguebit.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.com \
--cc=stable@kernel.org \
--cc=tom@talpey.com \
--cc=yangerkun@huawei.com \
--cc=yangerkun@huaweicloud.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 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.