All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6646318bbcf419411bc5@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Re: [syzbot] [nilfs?] INFO: task hung in find_inode (2)
Date: Sat, 15 Aug 2026 10:56:58 -0700	[thread overview]
Message-ID: <6a80a86a.dbb3a75c.20434b.0019.GAE@google.com> (raw)
In-Reply-To: <677f567c.050a0220.25a300.01ad.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Re: [syzbot] [nilfs?] INFO: task hung in find_inode (2)
Author: konishi.ryusuke@gmail.com


#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git c21bb4193868

Fix deadlock between find_inode() and nilfs_evict_inode()

diff --git a/fs/nilfs2/segment.c b/fs/nilfs2/segment.c
index 9332f5ac6083..6b2b7060f004 100644
--- a/fs/nilfs2/segment.c
+++ b/fs/nilfs2/segment.c
@@ -830,8 +830,11 @@ static void nilfs_iput_work_func(struct work_struct *work)
 	struct nilfs_sc_info *sci = container_of(work, struct nilfs_sc_info,
 						 sc_iput_work);
 	struct the_nilfs *nilfs = sci->sc_super->s_fs_info;
+	struct nilfs_transaction_info ti;
 
+	nilfs_transaction_begin(sci->sc_super, &ti, 0);
 	nilfs_dispose_list(nilfs, &sci->sc_iput_queue, 0);
+	nilfs_transaction_commit(sci->sc_super);
 }
 
 static int nilfs_test_metadata_dirty(struct the_nilfs *nilfs,
-- 
2.43.0

      reply	other threads:[~2026-08-15 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  4:54 [syzbot] [nilfs?] INFO: task hung in find_inode (2) syzbot
2026-08-15 17:56 ` syzbot [this message]

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=6a80a86a.dbb3a75c.20434b.0019.GAE@google.com \
    --to=syzbot+6646318bbcf419411bc5@syzkaller.appspotmail.com \
    --cc=linux-kernel@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.