From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Daeho Jeong <daeho43@gmail.com>
Cc: daehojeong@google.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
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: Fri, 21 Aug 2026 15:50:08 +0000 [thread overview]
Message-ID: <178732740863.1339488.18145676709503198602.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821141742.2678300-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 21 Aug 2026 07:17:42 -0700 you 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix error handling on device alias check in rename and unlink
https://git.kernel.org/jaegeuk/f2fs/c/27d0e27c096d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
christophe.jaillet@wanadoo.fr, 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 15:50:08 +0000 [thread overview]
Message-ID: <178732740863.1339488.18145676709503198602.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821141742.2678300-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 21 Aug 2026 07:17:42 -0700 you 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix error handling on device alias check in rename and unlink
https://git.kernel.org/jaegeuk/f2fs/c/27d0e27c096d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-21 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 14:17 [f2fs-dev] [PATCH] f2fs: fix error handling on device alias check in rename and unlink Daeho Jeong
2026-08-21 14:17 ` Daeho Jeong
2026-08-21 15:26 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-08-21 15:26 ` Jaegeuk Kim
2026-08-21 23:48 ` Chao Yu via Linux-f2fs-devel
2026-08-21 23:48 ` Chao Yu
2026-08-22 0:12 ` Jaegeuk Kim via Linux-f2fs-devel
2026-08-22 0:12 ` Jaegeuk Kim
2026-08-22 7:10 ` Chao Yu via Linux-f2fs-devel
2026-08-22 7:10 ` Chao Yu
2026-08-21 15:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
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 ` Chao Yu via Linux-f2fs-devel
2026-08-21 1:31 ` Chao Yu
2026-08-21 8:21 ` Christophe JAILLET via Linux-f2fs-devel
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=178732740863.1339488.18145676709503198602.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=christophe.jaillet@wanadoo.fr \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 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.