From: Mohammed Anees <pvmohammedanees2003@gmail.com>
To: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Mohammed Anees <pvmohammedanees2003@gmail.com>,
syzbot+18a87160c7d64ba2e2f6@syzkaller.appspotmail.com
Subject: [PATCH 1/2] ocfs2: Fix deadlock in ocfs2_read_virt_blocks
Date: Wed, 18 Sep 2024 17:20:25 +0000 [thread overview]
Message-ID: <20240918172026.2532-2-pvmohammedanees2003@gmail.com> (raw)
In-Reply-To: <20240918172026.2532-1-pvmohammedanees2003@gmail.com>
syzbot has found a kernel BUG in ocfs2_write_cluster_by_desc,
while the next patch in the series resolves this, another
bug has been detected due to a potential deadlock [1].
The scenario is depicted here,
CPU0 CPU1
lock(&ocfs2_file_ip_alloc_sem_key);
lock(&osb->system_file_mutex);
lock(&ocfs2_file_ip_alloc_sem_key);
lock(&osb->system_file_mutex);
The function calls which could lead to this are:
CPU0
ocfs2_write_begin - lock(&ocfs2_file_ip_alloc_sem_key);
.
.
.
ocfs2_get_system_file_inode - lock(&osb->system_file_mutex);
CPU1 -
ocfs2_get_system_file_inode - lock(&osb->system_file_mutex);
.
.
.
ocfs2_read_virt_blocks - lock(&ocfs2_file_ip_alloc_sem_key);
This issue can be resolved by making the down_read -> down_read_try
in the ocfs2_read_virt_blocks.
[1] https://syzkaller.appspot.com/bug?extid=18a87160c7d64ba2e2f6
Reported-and-tested-by: syzbot+18a87160c7d64ba2e2f6@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=18a87160c7d64ba2e2f6
Signed-off-by: Mohammed Anees <pvmohammedanees2003@gmail.com>
---
fs/ocfs2/extent_map.c | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/fs/ocfs2/extent_map.c b/fs/ocfs2/extent_map.c
index 70a768b62..f83d0a3b6 100644
--- a/fs/ocfs2/extent_map.c
+++ b/fs/ocfs2/extent_map.c
@@ -12,6 +12,7 @@
#include <linux/slab.h>
#include <linux/types.h>
#include <linux/fiemap.h>
+#include <linux/delay.h>
#include <cluster/masklog.h>
@@ -961,6 +962,8 @@ int ocfs2_read_virt_blocks(struct inode *inode, u64 v_block, int nr,
int rc = 0;
u64 p_block, p_count;
int i, count, done = 0;
+ int retries, max_retries = 5;
+ int retry_delay_ms = 30;
trace_ocfs2_read_virt_blocks(
inode, (unsigned long long)v_block, nr, bhs, flags,
@@ -973,7 +976,18 @@ int ocfs2_read_virt_blocks(struct inode *inode, u64 v_block, int nr,
}
while (done < nr) {
- down_read(&OCFS2_I(inode)->ip_alloc_sem);
+ retries = 0;
+ while (retries < max_retries) {
+ if (down_read_trylock(&OCFS2_I(inode)->ip_alloc_sem))
+ break; // Lock acquired
+ msleep(retry_delay_ms);
+ retries++;
+ }
+ if (retries == max_retries) {
+ rc = -EAGAIN;
+ mlog(ML_ERROR, "Cannot acquire lock\n");
+ break;
+ }
rc = ocfs2_extent_map_get_blocks(inode, v_block + done,
&p_block, &p_count, NULL);
up_read(&OCFS2_I(inode)->ip_alloc_sem);
--
2.46.0
next prev parent reply other threads:[~2024-09-18 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 17:20 [PATCH 0/2] ocfs2: Fix deadlock in extent_map and handle zero Mohammed Anees
2024-09-18 17:20 ` Mohammed Anees [this message]
2024-09-19 8:13 ` [PATCH 1/2] ocfs2: Fix deadlock in ocfs2_read_virt_blocks heming.zhao
2024-09-21 14:22 ` Mohammed Anees
2024-09-18 17:20 ` [PATCH 2/2] osfs2: Fix kernel BUG in ocfs2_write_cluster Mohammed Anees
2024-09-19 7:44 ` heming.zhao
2024-09-21 17:30 ` Mohammed Anees
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=20240918172026.2532-2-pvmohammedanees2003@gmail.com \
--to=pvmohammedanees2003@gmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+18a87160c7d64ba2e2f6@syzkaller.appspotmail.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