The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Daeho Jeong <daeho43@gmail.com>,
	Daeho Jeong <daehojeong@google.com>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	kernel-team@android.com, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix error handling on device alias check in rename and unlink
Date: Sat, 22 Aug 2026 00:12:20 +0000	[thread overview]
Message-ID: <aojpZFWIYAQ5Y-2W@google.com> (raw)
In-Reply-To: <b04fad97-89ea-43fc-a3b0-951c78838bcb@kernel.org>

On 08/22, Chao Yu wrote:
> On 8/21/26 23:26, Jaegeuk Kim via Linux-f2fs-devel wrote:
> > On 08/21, Daeho Jeong wrote:
> > > From: Daeho Jeong <daehojeong@google.com>
> > > 
> > > In f2fs_rename() and f2fs_unlink(), directly returning -EPERM when
> > > encountering a device aliasing file bypasses the cleanup path.
> > > 
> > > Fix this by setting err to -EPERM and jumping to the proper cleanup
> > > labels (out_dir and out) instead of returning immediately.
> > > 
> > > Fixes: a737e409a3d6 ("f2fs: support dynamic reserve/release for device aliasing")
> > > Cc: stable@kernel.org
> > 
> > Applied without Fixes and stable, since the original patch has not been
> > upstreamed.
> 
> Jaegeuk, if we don't plan to merge them, we'd better keep the Fixes and stable
> line, otherwise, once the two patches be upstreamed, we may missed to backport
> the fix one due to the missing lines?

My concern is the never existing hash in upstream. And, I don't think this will
go into any LTS.

> 
> Thanks,
> 
> > 
> > > Reported-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> > > Signed-off-by: Daeho Jeong <daehojeong@google.com>
> > > Reviewed-by: Chao Yu <chao@kernel.org>
> > > ---
> > >   fs/f2fs/namei.c | 12 ++++++++----
> > >   1 file changed, 8 insertions(+), 4 deletions(-)
> > > 
> > > diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
> > > index 784f636244e1..b9b15c5d28de 100644
> > > --- a/fs/f2fs/namei.c
> > > +++ b/fs/f2fs/namei.c
> > > @@ -571,8 +571,10 @@ static int f2fs_unlink(struct inode *dir, struct dentry *dentry)
> > >   	trace_f2fs_unlink_enter(dir, dentry);
> > > -	if (IS_DEVICE_ALIASING(inode))
> > > -		return -EPERM;
> > > +	if (IS_DEVICE_ALIASING(inode)) {
> > > +		err = -EPERM;
> > > +		goto out;
> > > +	}
> > >   	if (unlikely(f2fs_cp_error(sbi))) {
> > >   		err = -EIO;
> > > @@ -1025,8 +1027,10 @@ static int f2fs_rename(struct mnt_idmap *idmap, struct inode *old_dir,
> > >   	}
> > >   	if (new_inode) {
> > > -		if (IS_DEVICE_ALIASING(new_inode))
> > > -			return -EPERM;
> > > +		if (IS_DEVICE_ALIASING(new_inode)) {
> > > +			err = -EPERM;
> > > +			goto out_dir;
> > > +		}
> > >   		err = -ENOTEMPTY;
> > >   		if (old_is_dir && !f2fs_empty_dir(new_inode))
> > > -- 
> > > 2.55.0.766.g2966f0265a-goog
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Linux-f2fs-devel mailing list
> > > Linux-f2fs-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> > 
> > 
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> 

  reply	other threads:[~2026-08-22  0:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 14:17 [PATCH] f2fs: fix error handling on device alias check in rename and unlink Daeho Jeong
2026-08-21 15:26 ` [f2fs-dev] " Jaegeuk Kim
2026-08-21 23:48   ` Chao Yu
2026-08-22  0:12     ` Jaegeuk Kim [this message]
2026-08-22  7:10       ` Chao Yu
2026-08-21 15:50 ` patchwork-bot+f2fs
  -- strict thread matches above, loose matches on Subject: below --
2026-08-21  1:18 Daeho Jeong
2026-08-21  1:31 ` [f2fs-dev] " Chao Yu

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=aojpZFWIYAQ5Y-2W@google.com \
    --to=jaegeuk@kernel.org \
    --cc=chao@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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