From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
syzbot <syzbot+26860029a4d562566231@syzkaller.appspotmail.com>
Subject: Re: [syzbot] [btrfs?] KASAN: slab-use-after-free Read in btrfs_open_devices
Date: Tue, 8 Aug 2023 19:22:19 +0200 [thread overview]
Message-ID: <20230808172219.GA17612@lst.de> (raw)
In-Reply-To: <20230808-wohnsiedlung-exerzierplatz-02b1257b97a2@brauner>
On Tue, Aug 08, 2023 at 06:35:04PM +0200, Christian Brauner wrote:
> On Tue, Aug 08, 2023 at 06:01:41PM +0200, Christoph Hellwig wrote:
> > Yes, probably. The lifetimes looked fishy to me to start with, but
> > this might have made things worse.
>
> It looks like we should be able to just drop that patch.
> Ok, are you fixing this or should I drop this patch?
I plan to fix it, but you can drop it for. If we want to go on top
drop get_super like the preview series I sent you we'll eventually need
something like this patch back, though.
next prev parent reply other threads:[~2023-08-08 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 20:51 [syzbot] [btrfs?] KASAN: slab-use-after-free Read in btrfs_open_devices syzbot
2023-08-08 3:24 ` syzbot
2023-08-08 15:50 ` Christian Brauner
2023-08-08 16:01 ` Christoph Hellwig
2023-08-08 16:35 ` Christian Brauner
2023-08-08 17:22 ` Christoph Hellwig [this message]
2023-08-08 17:38 ` David Sterba
[not found] <20230808140807.1967-1-hdanton@sina.com>
2023-08-08 14:30 ` syzbot
[not found] <20230808232313.2035-1-hdanton@sina.com>
2023-08-08 23:38 ` syzbot
[not found] <20230809110318.2110-1-hdanton@sina.com>
2023-08-09 14:22 ` syzbot
[not found] <20230810104550.2217-1-hdanton@sina.com>
2023-08-10 11:05 ` syzbot
[not found] <20230810124552.2335-1-hdanton@sina.com>
2023-08-10 13:05 ` syzbot
[not found] <20230810141207.2398-1-hdanton@sina.com>
2023-08-10 15:03 ` 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=20230808172219.GA17612@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+26860029a4d562566231@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