From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, jack@suse.cz, linux-kernel@vger.kernel.org,
willy@infradead.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: quota: do not use GFP_NOFS in f2fs_quota_read()
Date: Tue, 14 Jul 2026 03:00:05 +0000 [thread overview]
Message-ID: <178399800589.2939750.3339446022508241105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707113934.3003158-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 7 Jul 2026 19:39:33 +0800 you wrote:
> Commit 02117b8ae9c0 ("f2fs: Set GF_NOFS in read_cache_page_gfp while doing
> f2fs_quota_read") adds GFP_NOFS in f2fs_quota_read() to avoid below deadlock:
>
> - do_sys_open
> - vfs_open
> - dquot_file_open
> - dquot_initialize
> - dqget
> - dquot_acquire
> : locks &dqopt->dqio_mutex (VFS Quota Mutex)
> - qtree_read_dquot
> - f2fs_quota_read
> - read_mapping_page (GFP_KERNEL / allows GFP_FS)
> - __alloc_pages_nodemask
> - try_to_free_pages (Direct Reclaim)
> - prune_icache_sb
> - evict
> - f2fs_evict_inode
> - dquot_drop
> - dqput
> - dquot_commit
> : tries to lock &dqopt->dqio_mutex again
> ==> DEADLOCK (waiting for itself)
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: quota: do not use GFP_NOFS in f2fs_quota_read()
https://git.kernel.org/jaegeuk/f2fs/c/9f3a37815818
- [f2fs-dev,v2,2/2] f2fs: drop FGP_NOFS in f2fs_write_begin()
https://git.kernel.org/jaegeuk/f2fs/c/6e7205a702e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-14 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 11:39 Chao Yu
2026-07-07 11:39 ` [PATCH v2 2/2] f2fs: drop FGP_NOFS in f2fs_write_begin() Chao Yu
2026-07-08 16:01 ` [PATCH v2 1/2] f2fs: quota: do not use GFP_NOFS in f2fs_quota_read() Jan Kara
2026-07-14 3:00 ` patchwork-bot+f2fs [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=178399800589.2939750.3339446022508241105.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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