mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nikola Z. Ivanov" <zlatistiv@gmail.com>
To: shaggy@kernel.org, dmantipov@yandex.ru, quic_zhonhan@quicinc.com,
	eadavis@qq.com, jfs-discussion@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org,
	"Nikola Z. Ivanov" <zlatistiv@gmail.com>,
	syzbot+d569e274f46ca86f78fa@syzkaller.appspotmail.com
Subject: [PATCH] jfs: Check for discrepancies between iag and inomap iagctl
Date: Fri,  2 Jan 2026 20:48:49 +0200	[thread overview]
Message-ID: <20260102184849.1932768-1-zlatistiv@gmail.com> (raw)

syzbot reports "VFS: Busy inodes after unmount" which is caused
by a deadlock in the jfsCommit thread, in a call to diFree.

The filesystem from the syz repro can be used to reproduce the
deadlock by mounting it, deleting a file and running "sync" or
unmounting the filesystem. Running "fsck" on the filesystem
image seemingly fixes the inconsistency and we no longer deadlock.

This happens because the IAG that contains the inode we are
freeing is head of the free list, but also holds nfreeinos = 0,
which will lead to a deadlock when we try to add it as head
of the free list, since it already is head of the list.

Fix this by adding a check for the discrepancy before
reading more metapages that could potentially match with "mp".
Do the same for the extent free list as it may lead to a
similar deadlock.

Reported-by: syzbot+d569e274f46ca86f78fa@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=d569e274f46ca86f78fa
Signed-off-by: Nikola Z. Ivanov <zlatistiv@gmail.com>
---
 fs/jfs/jfs_imap.c | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/fs/jfs/jfs_imap.c b/fs/jfs/jfs_imap.c
index ecb8e05b8b84..fd9f9babaf46 100644
--- a/fs/jfs/jfs_imap.c
+++ b/fs/jfs/jfs_imap.c
@@ -902,6 +902,25 @@ int diFree(struct inode *ip)
 	}
 	iagp = (struct iag *) mp->data;
 
+	/* We will deadlock if due to inconsistency
+	 * the iag has no free inodes/extents but is
+	 * head of the respective free list
+	 */
+	if (iagp->nfreeinos == 0 && imap->im_agctl[agno].inofree == iagno) {
+		IREAD_UNLOCK(ipimap);
+		AG_UNLOCK(imap, agno);
+		release_metapage(mp);
+		jfs_error(ip->i_sb, "nfreeinos = 0, but iag is head of freelist\n");
+		return -EIO;
+	}
+	if (iagp->nfreeexts == 0 && imap->im_agctl[agno].extfree == iagno) {
+		IREAD_UNLOCK(ipimap);
+		AG_UNLOCK(imap, agno);
+		release_metapage(mp);
+		jfs_error(ip->i_sb, "nfreeexts = 0, but iag is head of freelist\n");
+		return -EIO;
+	}
+
 	/* get the inode number and extent number of the inode within
 	 * the iag and the inode number within the extent.
 	 */
-- 
2.51.0


             reply	other threads:[~2026-01-02 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 18:48 Nikola Z. Ivanov [this message]
2026-02-08  8:20 ` Nikola Z. Ivanov

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=20260102184849.1932768-1-zlatistiv@gmail.com \
    --to=zlatistiv@gmail.com \
    --cc=dmantipov@yandex.ru \
    --cc=eadavis@qq.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_zhonhan@quicinc.com \
    --cc=shaggy@kernel.org \
    --cc=syzbot+d569e274f46ca86f78fa@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

all inboxes | Powered by JetHome®