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,
Baokun Li <libaokun1@huawei.com>, Jan Kara <jack@suse.cz>
Subject: [PATCH v2 2/2] ext4: protect ext4_release_dquot against freezing
Date: Thu, 21 Nov 2024 18:08:55 +0530 [thread overview]
Message-ID: <20241121123855.645335-3-ojaswin@linux.ibm.com> (raw)
In-Reply-To: <20241121123855.645335-1-ojaswin@linux.ibm.com>
Protect ext4_release_dquot against freezing so that we
don't try to start a transaction when FS is frozen, leading
to warnings.
Further, avoid taking the freeze protection if a transaction
is already running so that we don't need end up in a deadlock
as described in
46e294efc355 ext4: fix deadlock with fs freezing and EA inodes
Suggested-by: Jan Kara <jack@suse.cz>
Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
---
fs/ext4/super.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 16a4ce704460..f7437a592359 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -6887,12 +6887,25 @@ static int ext4_release_dquot(struct dquot *dquot)
{
int ret, err;
handle_t *handle;
+ bool freeze_protected = false;
+
+ /*
+ * Trying to sb_start_intwrite() in a running transaction
+ * can result in a deadlock. Further, running transactions
+ * are already protected from freezing.
+ */
+ if (!ext4_journal_current_handle()) {
+ sb_start_intwrite(dquot->dq_sb);
+ freeze_protected = true;
+ }
handle = ext4_journal_start(dquot_to_inode(dquot), EXT4_HT_QUOTA,
EXT4_QUOTA_DEL_BLOCKS(dquot->dq_sb));
if (IS_ERR(handle)) {
/* Release dquot anyway to avoid endless cycle in dqput() */
dquot_release(dquot);
+ if (freeze_protected)
+ sb_end_intwrite(dquot->dq_sb);
return PTR_ERR(handle);
}
ret = dquot_release(dquot);
@@ -6903,6 +6916,10 @@ static int ext4_release_dquot(struct dquot *dquot)
err = ext4_journal_stop(handle);
if (!ret)
ret = err;
+
+ if (freeze_protected)
+ sb_end_intwrite(dquot->dq_sb);
+
return ret;
}
--
2.43.5
next prev parent reply other threads:[~2024-11-21 12:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 12:38 [PATCH v2 0/2] Fix generic/390 failure due to quota release after freeze Ojaswin Mujoo
2024-11-21 12:38 ` [PATCH v2 1/2] quota: flush quota_release_work upon quota writeback Ojaswin Mujoo
2024-11-26 8:47 ` Jan Kara
2024-11-26 14:28 ` Baokun Li
2024-11-29 8:00 ` Disha Goel
2024-11-21 12:38 ` Ojaswin Mujoo [this message]
2024-11-22 5:25 ` [PATCH v2 2/2] ext4: protect ext4_release_dquot against freezing kernel test robot
2024-11-22 6:07 ` kernel test robot
2024-11-26 9:04 ` Jan Kara
2024-11-26 12:41 ` Ojaswin Mujoo
2024-11-26 14:49 ` Baokun Li
2024-11-27 6:01 ` Ojaswin Mujoo
2024-12-03 8:29 ` Baokun Li
2024-12-16 9:11 ` Ojaswin Mujoo
2024-11-28 4:58 ` Ritesh Harjani
2024-11-28 12:01 ` Jan Kara
2025-03-06 6:30 ` Ojaswin Mujoo
2025-03-06 15:59 ` Theodore Ts'o
2024-11-21 12:48 ` [PATCH v2 0/2] Fix generic/390 failure due to quota release after freeze 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=20241121123855.645335-3-ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.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