All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: syzbot <syzbot+2faac0423fdc9692822b@syzkaller.appspotmail.com>,
	jack@suse.cz, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] KASAN: slab-use-after-free Read in test_bdev_super_fc
Date: Fri, 4 Aug 2023 16:49:18 +0200	[thread overview]
Message-ID: <20230804-kurvigen-uninteressant-09d451db7458@brauner> (raw)
In-Reply-To: <20230804144343.GA28230@lst.de>

On Fri, Aug 04, 2023 at 04:43:43PM +0200, Christoph Hellwig wrote:
> On Fri, Aug 04, 2023 at 04:36:49PM +0200, Christian Brauner wrote:
> > FFS
> 
> Good spot, this explains the missing dropping of s_umount.
> 
> But I don't think it's doing the right thing for MTD mount romfs,
> we'll need something like this:

I'll fold a fix into Jan's patch.

  reply	other threads:[~2023-08-04 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 22:14 [syzbot] [fs?] KASAN: slab-use-after-free Read in test_bdev_super_fc syzbot
2023-08-04 10:14 ` Christoph Hellwig
2023-08-04 13:20   ` Christian Brauner
2023-08-04 14:02     ` Christoph Hellwig
2023-08-04 14:36       ` Christian Brauner
2023-08-04 14:43         ` Christoph Hellwig
2023-08-04 14:49           ` Christian Brauner [this message]
2023-08-04 15:29             ` Christian Brauner
2023-08-05  8:57               ` Christoph Hellwig
     [not found]             ` <20230805084316.1699-1-hdanton@sina.com>
2023-08-05  8:48               ` Christoph Hellwig
     [not found] <20230804125406.1583-1-hdanton@sina.com>
2023-08-04 19:13 ` syzbot
     [not found] <20230804233428.1642-1-hdanton@sina.com>
2023-08-05  0:11 ` 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=20230804-kurvigen-uninteressant-09d451db7458@brauner \
    --to=brauner@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+2faac0423fdc9692822b@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.