All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8996d8f176cf946ef641@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [bcachefs?] INFO: task hung in bch2_fs_read_only_work
Date: Mon, 01 Jul 2024 01:45:45 -0700	[thread overview]
Message-ID: <000000000000850b95061c2b9fc0@google.com> (raw)
In-Reply-To: <000000000000e9b6ff0618356b26@google.com>

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

***

Subject: Re: [syzbot] [bcachefs?] INFO: task hung in bch2_fs_read_only_work
Author: lizhi.xu@windriver.com

#syz test: upstream f06ce441457d

when hit -BCH_ERR_fsck_errors_not_fixed in journal_entry_err, it will make
journal_entry_btree_keys_validate output too many same error log, and it will block
bch2_fs_start to release state_lock

diff --git a/fs/bcachefs/journal_io.c b/fs/bcachefs/journal_io.c
index 492426c8d869..67c3f09162e4 100644
--- a/fs/bcachefs/journal_io.c
+++ b/fs/bcachefs/journal_io.c
@@ -415,6 +415,8 @@ static int journal_entry_btree_keys_validate(struct bch_fs *c,
 					       flags|BCH_VALIDATE_journal);
 		if (ret == FSCK_DELETED_KEY)
 			continue;
+		else if (ret == -BCH_ERR_fsck_errors_not_fixed)
+			break;
 
 		k = bkey_next(k);
 	}

      parent reply	other threads:[~2024-07-01  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 22:46 [syzbot] [bcachefs?] INFO: task hung in bch2_fs_read_only_work syzbot
2024-06-04  3:28 ` syzbot
2024-06-30  9:24   ` Hillf Danton
2024-06-30 10:37     ` syzbot
2024-06-30 11:39   ` Hillf Danton
2024-06-30 12:37     ` syzbot
2024-07-01 14:36   ` [PATCH] bcachefs: fix " Lizhi Xu
2024-07-05  1:18     ` Kent Overstreet
2024-06-04 11:26 ` [syzbot] [bcachefs?] INFO: task " syzbot
2024-07-01  8:45 ` 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=000000000000850b95061c2b9fc0@google.com \
    --to=syzbot+8996d8f176cf946ef641@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.