The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix error handling on device alias check in rename and unlink
Date: Fri, 21 Aug 2026 09:31:23 +0800	[thread overview]
Message-ID: <574ad500-a254-4430-925b-c1f8275d0a42@kernel.org> (raw)
In-Reply-To: <20260821011812.2938998-1-daeho43@gmail.com>

On 8/21/26 09:18, 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
> Signed-off-by: Daeho Jeong <daehojeong@google.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2026-08-21  1:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  1:18 [PATCH] f2fs: fix error handling on device alias check in rename and unlink Daeho Jeong
2026-08-21  1:31 ` Chao Yu [this message]
2026-08-21  8:21 ` Christophe JAILLET
  -- strict thread matches above, loose matches on Subject: below --
2026-08-21 14:17 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
2026-08-22  7:10       ` Chao Yu
2026-08-21 15:50 ` patchwork-bot+f2fs

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=574ad500-a254-4430-925b-c1f8275d0a42@kernel.org \
    --to=chao@kernel.org \
    --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