From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to use bio_in_atomic() in f2fs_write_end_io()
Date: Tue, 13 Oct 2026 22:30:12 +0000 [thread overview]
Message-ID: <179193061226.1493834.2807763265154203620.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261010065546.1762091-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 10 Oct 2026 14:55:45 +0800 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> f2fs_write_end_io() uses in_atomic() to decide whether a write bio which
> exceeds max_atc_write_bio_size or max_atc_write_bio_entry_cnt should be
> completed in sbi->wq rather than in the current context.
>
> However, in_atomic() is not meant to be used outside core kernel code
> (checkpatch.pl warns about it), as it only looks at preempt_count(): it
> misses irqs-disabled and RCU read-side critical sections, and on kernels
> without CONFIG_PREEMPT_COUNT it cannot see spinlock-held sections at all.
> In those contexts, a large write bio will still be completed inline,
> which defeats the purpose of the above knobs.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to use bio_in_atomic() in f2fs_write_end_io()
https://git.kernel.org/jaegeuk/f2fs/c/e4582e5f3b43
- [f2fs-dev,2/2] f2fs: fix to use bio_in_atomic() in f2fs_read_end_io()
https://git.kernel.org/jaegeuk/f2fs/c/a605d5d71a6d
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
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 6:55 [f2fs-dev] [PATCH 1/2] f2fs: fix to use bio_in_atomic() in f2fs_write_end_io() Chao Yu via Linux-f2fs-devel
2026-10-10 6:55 ` [f2fs-dev] [PATCH 2/2] f2fs: fix to use bio_in_atomic() in f2fs_read_end_io() Chao Yu via Linux-f2fs-devel
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
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=179193061226.1493834.2807763265154203620.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--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.