From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Wenjie Qi <qwjhust@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, qiwenjie@xiaomi.com,
jaegeuk@kernel.org, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: return symlink writeback errors
Date: Wed, 12 Aug 2026 20:30:05 +0000 [thread overview]
Message-ID: <178656660539.2090005.2292921508148782354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260810133832.3530016-1-qiwenjie@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 10 Aug 2026 21:38:32 +0800 you wrote:
> F2FS writes long symlink data with page_symlink() and then flushes the
> symlink mapping to reduce the chance of exposing a broken symlink.
>
> That flush result is currently ignored. If the writeback fails, symlink()
> still returns success even though the symlink is not durable and the same
> operation can already surface -EIO through syncfs().
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: return symlink writeback errors
https://git.kernel.org/jaegeuk/f2fs/c/5d6f08574082
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: Wenjie Qi <qwjhust@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, stable@kernel.org,
qiwenjie@xiaomi.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: return symlink writeback errors
Date: Wed, 12 Aug 2026 20:30:05 +0000 [thread overview]
Message-ID: <178656660539.2090005.2292921508148782354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260810133832.3530016-1-qiwenjie@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 10 Aug 2026 21:38:32 +0800 you wrote:
> F2FS writes long symlink data with page_symlink() and then flushes the
> symlink mapping to reduce the chance of exposing a broken symlink.
>
> That flush result is currently ignored. If the writeback fails, symlink()
> still returns success even though the symlink is not durable and the same
> operation can already surface -EIO through syncfs().
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: return symlink writeback errors
https://git.kernel.org/jaegeuk/f2fs/c/5d6f08574082
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-12 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 13:38 [f2fs-dev] [PATCH v2] f2fs: return symlink writeback errors Wenjie Qi
2026-08-10 13:38 ` Wenjie Qi
2026-08-12 9:30 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-12 9:30 ` Chao Yu
2026-08-12 20:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-08-12 20:30 ` [f2fs-dev] " patchwork-bot+f2fs
2026-08-15 5:18 ` Al Viro
2026-08-15 5:18 ` [f2fs-dev] " Al Viro
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=178656660539.2090005.2292921508148782354.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=qiwenjie@xiaomi.com \
--cc=qwjhust@gmail.com \
--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.