From: Ojaswin Mujoo <ojaswin@linux.ibm.com>
To: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Disha Goel <disgoel@linux.ibm.com>
Subject: [PATCH 1/1] quota: flush quota_release_work upon quota writeback
Date: Sat, 16 Nov 2024 00:04:49 +0530 [thread overview]
Message-ID: <20241115183449.2058590-2-ojaswin@linux.ibm.com> (raw)
In-Reply-To: <20241115183449.2058590-1-ojaswin@linux.ibm.com>
One of the paths quota writeback is called from is:
freeze_super()
sync_filesystem()
ext4_sync_fs()
dquot_writeback_dquots()
Since we currently don't always flush the quota_release_work queue in
this path, we can end up with the following race:
1. dquot are added to releasing_dquots list during regular operations.
2. FS freeze starts, however, this does not flush the quota_release_work queue.
3. Freeze completes.
4. Kernel eventually tries to flush the workqueue while FS is frozen which
hits a WARN_ON since transaction gets started during frozen state:
ext4_journal_check_start+0x28/0x110 [ext4] (unreliable)
__ext4_journal_start_sb+0x64/0x1c0 [ext4]
ext4_release_dquot+0x90/0x1d0 [ext4]
quota_release_workfn+0x43c/0x4d0
Which is the following line:
WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);
Which ultimately results in generic/390 failing due to dmesg
noise. This was detected on powerpc machine 15 cores.
To avoid this, make sure to flush the workqueue during
dquot_writeback_dquots() so we dont have any pending workitems after
freeze.
Reported-by: Disha Goel <disgoel@linux.ibm.com>
Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
---
fs/quota/dquot.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/quota/dquot.c b/fs/quota/dquot.c
index 3dd8d6f27725..2782cfc8c302 100644
--- a/fs/quota/dquot.c
+++ b/fs/quota/dquot.c
@@ -729,6 +729,8 @@ int dquot_writeback_dquots(struct super_block *sb, int type)
sb->dq_op->write_info(sb, cnt);
dqstats_inc(DQST_SYNCS);
+ flush_delayed_work("a_release_work);
+
return ret;
}
EXPORT_SYMBOL(dquot_writeback_dquots);
--
2.43.5
next prev parent reply other threads:[~2024-11-15 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 18:34 [PATCH 0/1] Fix generic/390 failure due to quota release after freeze Ojaswin Mujoo
2024-11-15 18:34 ` Ojaswin Mujoo [this message]
2024-11-15 20:50 ` [PATCH 1/1] quota: flush quota_release_work upon quota writeback Ritesh Harjani
2024-11-16 17:59 ` Ojaswin Mujoo
2024-11-18 1:29 ` Baokun Li
2024-11-18 12:53 ` Jan Kara
2024-11-19 6:29 ` Baokun Li
2024-11-18 13:15 ` Jan Kara
2024-11-19 5:42 ` Ojaswin Mujoo
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=20241115183449.2058590-2-ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=disgoel@linux.ibm.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
/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