mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+8aaf2df2ef0164ffe1fb@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel] WARNING: locking bug in try_to_wake_up
Date: Tue,  1 Oct 2024 16:31:26 +0800	[thread overview]
Message-ID: <20241001083126.1792-1-hdanton@sina.com> (raw)
In-Reply-To: <66fb36b1.050a0220.aab67.003b.GAE@google.com>

On Mon, 30 Sep 2024 16:39:29 -0700
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    9852d85ec9d4 Linux 6.12-rc1
> git tree:       upstream
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13ad839f980000

#syz test

--- x/fs/btrfs/disk-io.c
+++ y/fs/btrfs/disk-io.c
@@ -4316,7 +4316,6 @@ void __cold close_ctree(struct btrfs_fs_
 		btrfs_error_commit_super(fs_info);
 
 	kthread_stop(fs_info->transaction_kthread);
-	kthread_stop(fs_info->cleaner_kthread);
 
 	ASSERT(list_empty(&fs_info->delayed_iputs));
 	set_bit(BTRFS_FS_CLOSING_DONE, &fs_info->flags);
@@ -4349,6 +4348,7 @@ void __cold close_ctree(struct btrfs_fs_
 	 */
 	invalidate_inode_pages2(fs_info->btree_inode->i_mapping);
 	btrfs_stop_all_workers(fs_info);
+	kthread_stop(fs_info->cleaner_kthread);
 
 	/* We shouldn't have any transaction open at this point */
 	warn_about_uncommitted_trans(fs_info);
--

  parent reply	other threads:[~2024-10-01  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 18:41 [syzbot] [wireguard?] " syzbot
2024-09-30 23:39 ` [syzbot] [kernel] " syzbot
2024-10-01  1:49   ` Hillf Danton
2024-10-01  2:10     ` syzbot
2024-10-01  8:31   ` Hillf Danton [this message]
2024-10-01  8:50     ` syzbot

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=20241001083126.1792-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+8aaf2df2ef0164ffe1fb@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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®