From: syzbot <syzbot+9fc4dac4775d07bcfe34@syzkaller.appspotmail.com>
To: lizhi.xu@windriver.com
Cc: lizhi.xu@windriver.com, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [bcachefs?] KASAN: slab-use-after-free Read in bch2_reconstruct_alloc
Date: Wed, 23 Oct 2024 18:09:28 -0700 [thread overview]
Message-ID: <67199e48.050a0220.10f4f4.01d5.GAE@google.com> (raw)
In-Reply-To: <20241024010924.908879-1-lizhi.xu@windriver.com>
>
> #syz test: upstream
want either no args or 2 args (repo, branch), got 5
>
> diff --git a/fs/bcachefs/recovery.c b/fs/bcachefs/recovery.c
> index 55e1504a8130..717c1a80de20 100644
> --- a/fs/bcachefs/recovery.c
> +++ b/fs/bcachefs/recovery.c
> @@ -95,9 +95,9 @@ static void bch2_reconstruct_alloc(struct bch_fs *c)
> c->sb.compat &= ~(1ULL << BCH_COMPAT_alloc_info);
>
> bch2_write_super(c);
> - mutex_unlock(&c->sb_lock);
>
> c->opts.recovery_passes |= bch2_recovery_passes_from_stable(le64_to_cpu(ext->recovery_passes_required[0]));
> + mutex_unlock(&c->sb_lock);
>
>
> bch2_shoot_down_journal_keys(c, BTREE_ID_alloc,
next parent reply other threads:[~2024-10-24 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241024010924.908879-1-lizhi.xu@windriver.com>
2024-10-24 1:09 ` syzbot [this message]
2024-10-26 4:19 [PATCH] bcachefs: Retrieve ext again after sb is reallocated Lizhi Xu
2024-10-26 4:21 ` [syzbot] [bcachefs?] KASAN: slab-use-after-free Read in bch2_reconstruct_alloc syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 4:19 [syzbot] [btrfs?] general protection fault in btrfs_search_slot Qu Wenruo
2024-10-25 4:38 ` [syzbot] [bcachefs?] KASAN: slab-use-after-free Read in bch2_reconstruct_alloc Lizhi Xu
2024-10-25 4:44 ` Qu Wenruo
[not found] <20241024064539.2963555-1-lizhi.xu@windriver.com>
2024-10-24 7:49 ` syzbot
[not found] <20241024011358.918019-1-lizhi.xu@windriver.com>
2024-10-24 1:33 ` syzbot
2024-10-23 14:27 syzbot
2024-10-25 10:02 ` Lizhi Xu
2024-10-25 10:31 ` 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=67199e48.050a0220.10f4f4.01d5.GAE@google.com \
--to=syzbot+9fc4dac4775d07bcfe34@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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