From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Hao Sun <sunhao.th@gmail.com>, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>,
Josef Bacik <josef@toxicpanda.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: INFO: task hung in btrfs_search_slot
Date: Fri, 29 Oct 2021 15:33:26 +0200 [thread overview]
Message-ID: <20211029133326.GB20319@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H58SZtvEFn5zRMoMy2iJQsvAvqNEqwmvyhQuh33_H0inQ@mail.gmail.com>
On Wed, Oct 27, 2021 at 04:34:37PM +0100, Filipe Manana wrote:
> On Wed, Oct 27, 2021 at 2:08 PM Hao Sun <sunhao.th@gmail.com> wrote:
> >
> > Hello,
> >
> > When using Healer to fuzz the latest Linux kernel, the following crash
> > was triggered.
>
> This is the same deadlock you reported 3 weeks ago here:
>
> https://lore.kernel.org/linux-btrfs/CACkBjsax51i4mu6C0C3vJqQN3NR_iVuucoeG3U1HXjrgzn5FFQ@mail.gmail.com/
>
> There's a fix in the integration branch (David's misc-next branch),
> but it's not yet in any released kernel and not in Linus' tree as
> well:
>
> https://lore.kernel.org/linux-btrfs/cover.1634115580.git.fdmanana@suse.com/
It'll go to 5.15 pull and the fix is tagged for 5.14 stable so it'll be
in some release in the 5.15-rc1 timeframe.
next prev parent reply other threads:[~2021-10-29 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 1:13 INFO: task hung in btrfs_search_slot Hao Sun
2021-10-27 15:34 ` Filipe Manana
2021-10-29 13:33 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 9:16 Hao Sun
2021-10-06 10:32 ` Filipe Manana
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=20211029133326.GB20319@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=sunhao.th@gmail.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;
as well as URLs for NNTP newsgroup(s).