All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Wenwu Hou <hwenwur@gmail.com>,
	sashal@kernel.org, stable@vger.kernel.org, xiang@kernel.org,
	chao@kernel.org, zbestahu@gmail.com, jefflexu@linux.alibaba.com,
	dhavale@google.com, lihongbo22@huawei.com, guochunhai@vivo.com,
	yinxin.x@bytedance.com, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH stable] erofs: fix large folio race in erofs_fscache_req_complete
Date: Wed, 23 Sep 2026 19:30:31 +0200	[thread overview]
Message-ID: <arQMt6-Kuc_TwHeT@MacBookPro.fritz.box> (raw)
In-Reply-To: <2026092320-process-federal-6533@gregkh>

Hi Greg,

On Wed, Sep 23, 2026 at 11:30:44AM +0200, Greg KH wrote:
> On Wed, Sep 23, 2026 at 04:48:23PM +0800, Wenwu Hou wrote:
> > This patch is for stable only. Commit c37460cd9b2fc ("erofs: remove fscache
> > backend entirely") upstream removed this code.
> 
> We need an ack/review from the maintainers of this code.  And if it's
> removed in newer kernels, why not do the same thing here too?

I hope the old kernels could still support fscache since some important
enterprise users (e.g. xiaomi) are still using "erofs over fscache" with
old kernels for their containers and they still need some time to
switch to the new way "erofs + fanotify" with newer kernels.

The patch looks good to me, for such simple stability fscache fixes,
I hope the fix could be landed into stable kernels:

Reviewed-by: Gao Xiang <xiang@kernel.org>

Thanks,
Gao Xiang

> 
> thanks,
> 
> greg k-h


  reply	other threads:[~2026-09-23 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  8:48 [PATCH stable] erofs: fix large folio race in erofs_fscache_req_complete Wenwu Hou
2026-09-23  9:30 ` Greg KH
2026-09-23 17:30   ` Gao Xiang [this message]
2026-09-24 17:13 ` Sasha Levin

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=arQMt6-Kuc_TwHeT@MacBookPro.fritz.box \
    --to=xiang@kernel.org \
    --cc=chao@kernel.org \
    --cc=dhavale@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guochunhai@vivo.com \
    --cc=hwenwur@gmail.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=lihongbo22@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yinxin.x@bytedance.com \
    --cc=zbestahu@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 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.