Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiucheng Xu <jiucheng.xu@amlogic.com>
Cc: stable@vger.kernel.org, jianxin.pan@amlogic.com,
	tuan.zhang@amlogic.com, JY <JY.Ho@mediatek.com>,
	Chao Yu <chao@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH] f2fs: fix UAF issue in f2fs_merge_page_bio()
Date: Tue, 21 Jul 2026 15:04:50 +0200	[thread overview]
Message-ID: <2026072110-tweet-comment-9180@gregkh> (raw)
In-Reply-To: <21c69c82-f947-49b6-a046-cd0cd3037dce@amlogic.com>

On Fri, Jul 10, 2026 at 11:17:19AM +0800, Jiucheng Xu wrote:
> 
> On 7/9/2026 7:04 PM, Greg KH wrote:
> > [ EXTERNAL EMAIL ]
> > 
> > On Thu, Jul 09, 2026 at 05:35:40PM +0800, Jiucheng Xu via B4 Relay wrote:
> > > From: Jiucheng Xu <jiucheng.xu@amlogic.com>
> > > 
> > > commit edf7e9040fc52c922db947f9c6c36f07377c52ea upstream.
> > > 
> > > As JY reported in bugzilla [1],
> > 
> > What kernel(s) is this for?
> 
> I'm really sorry, Greg.
> 
> This is my first time submitting code to the stable git tree, and I'm not
> quite familiar with the process and rules yet. Please forgive me.
> 
> I hope this patch can be applied to the v5.15.y branch. I referred to other
> patches and added a "[Mark: backport to v5.15.y]" in the commit message. I'm
> not sure if this is correct.

It needs to go to the newer kernels first, so that you do not have a
regression when moving to a newer release.  So can you submit backports
for all of the relevant stable kernel trees, including 5.15.y, and we
will be glad to queue them all up then.

thanks,

greg k-h

  reply	other threads:[~2026-07-21 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  9:35 [PATCH] f2fs: fix UAF issue in f2fs_merge_page_bio() Jiucheng Xu via B4 Relay
2026-07-09 11:04 ` Greg KH
2026-07-10  3:17   ` Jiucheng Xu
2026-07-21 13:04     ` Greg KH [this message]
2026-07-24  1:46       ` Jiucheng Xu
2026-07-24  5:50         ` Greg KH

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=2026072110-tweet-comment-9180@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=JY.Ho@mediatek.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=jianxin.pan@amlogic.com \
    --cc=jiucheng.xu@amlogic.com \
    --cc=stable@vger.kernel.org \
    --cc=tuan.zhang@amlogic.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