Re: [PATCH] f2fs: fix UAF issue in f2fs_merge_page_bio()

[Greg KH <gregkh@linuxfoundation.org>]

On Fri, Jul 24, 2026 at 09:46:39AM +0800, Jiucheng Xu wrote:
> 
> 
> On 7/21/2026 9:04 PM, Greg KH wrote:
> > [ EXTERNAL EMAIL ]
> > 
> > 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.
> > Hi Greg,
> 
> Could I ask for your advice? When submitting patches to different branches,
> how do I mark each commit to specify the target branch it applies to?

The simplest way, and what I would strongly recommend, is to put the
version in the subject line, like this series did:
	https://lore.kernel.org/r/20260724012519.3833356-1-sashal@kernel.org

Look in the email archives for this list for thousands of other examples
of this happening :)

Also, please read the stable-kernel-rules document which explains that
you do have to list the kernel version a patch is to be applied to.  If
you haven't read that already, there's probably other things you missed
as part of this process also.

thanks,

greg k-h