From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pranav Tyagi <pranav.tyagi03@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] ocfs2: fix deadlock in ocfs2_get_system_file_inode
Date: Mon, 30 Jun 2025 21:15:36 -0400 [thread overview]
Message-ID: <20250630143337-e1f4376cbeee4e8c@stable.kernel.org> (raw)
In-Reply-To: <20250630083542.10121-1-pranav.tyagi03@gmail.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 7bf1823e010e8db2fb649c790bd1b449a75f52d8
WARNING: Author mismatch between patch and upstream commit:
Backport author: Pranav Tyagi<pranav.tyagi03@gmail.com>
Commit author: Mohammed Anees<pvmohammedanees2003@gmail.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: ec3e32de2d8a)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 7bf1823e010e8 ! 1: 8b2350f85e550 ocfs2: fix deadlock in ocfs2_get_system_file_inode
@@ Metadata
## Commit message ##
ocfs2: fix deadlock in ocfs2_get_system_file_inode
+ [ Upstream commit 7bf1823e010e8db2fb649c790bd1b449a75f52d8 ]
+
syzbot has found a possible deadlock in ocfs2_get_system_file_inode [1].
The scenario is depicted here,
@@ Commit message
[1] https://syzkaller.appspot.com/bug?extid=e0055ea09f1f5e6fabdd
+ [ Backport to 5.15: context cleanly applied with no semantic changes.
+ Build-tested. ]
+
Link: https://lkml.kernel.org/r/20240924093257.7181-1-pvmohammedanees2003@gmail.com
Signed-off-by: Mohammed Anees <pvmohammedanees2003@gmail.com>
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
@@ Commit message
Cc: Jun Piao <piaojun@huawei.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+ Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
## fs/ocfs2/extent_map.c ##
@@ fs/ocfs2/extent_map.c: int ocfs2_read_virt_blocks(struct inode *inode, u64 v_block, int nr,
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-07-01 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 8:35 [PATCH 5.15.y] ocfs2: fix deadlock in ocfs2_get_system_file_inode Pranav Tyagi
2025-07-01 1:15 ` Sasha Levin [this message]
2025-07-12 13:46 ` Greg KH
2025-07-12 17:11 ` Pranav Tyagi
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=20250630143337-e1f4376cbeee4e8c@stable.kernel.org \
--to=sashal@kernel.org \
--cc=pranav.tyagi03@gmail.com \
--cc=stable@vger.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.