linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: syzbot <syzbot+629c4f1a4cefe03f8985@syzkaller.appspotmail.com>
Cc: dhowells@redhat.com, jack@suse.cz, linux-afs@lists.infradead.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	marc.dionne@auristor.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [afs?] KASAN: slab-use-after-free Read in afs_dynroot_test_super
Date: Mon, 4 Sep 2023 10:07:02 +0200	[thread overview]
Message-ID: <20230904-sichel-elend-554e68a96d93@brauner> (raw)
In-Reply-To: <0000000000003849fc0604607941@google.com>

On Sat, Sep 02, 2023 at 06:44:17AM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    1c59d383390f Merge tag 'linux-kselftest-nolibc-6.6-rc1' of..
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=13f80797a80000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=4940ad7c14cda5c7
> dashboard link: https://syzkaller.appspot.com/bug?extid=629c4f1a4cefe03f8985
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=115b0c70680000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=170267b7a80000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/b6c588f544ac/disk-1c59d383.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/bab40745ca7b/vmlinux-1c59d383.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/9a8f42a5537c/bzImage-1c59d383.xz

#syz fix: super: ensure valid info

      reply	other threads:[~2023-09-04  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-02 13:44 [syzbot] [afs?] KASAN: slab-use-after-free Read in afs_dynroot_test_super syzbot
2023-09-04  8:07 ` Christian Brauner [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=20230904-sichel-elend-554e68a96d93@brauner \
    --to=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=syzbot+629c4f1a4cefe03f8985@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;
as well as URLs for NNTP newsgroup(s).