All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: syzbot <syzbot+7ec4ebe875a7076ebb31@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] KASAN: use-after-free Read in ext4_find_extent (3)
Date: Wed, 28 Jun 2023 23:18:52 -0400	[thread overview]
Message-ID: <20230629031852.GH8954@mit.edu> (raw)
In-Reply-To: <000000000000c7970f05ff1ecb4d@google.com>

#syz set prio: low

On Tue, Jun 27, 2023 at 09:16:56AM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    8a28a0b6f1a1 Merge tag 'net-6.4-rc8' of git://git.kernel.o..
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=12f5b40b280000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=e74b395fe4978721
> dashboard link: https://syzkaller.appspot.com/bug?extid=7ec4ebe875a7076ebb31
> compiler:       Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15a2b5c0a80000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1181c5c0a80000

This report is via writing to the block device, while the file system
is mounted.

     	       		 	 	    - Ted

  reply	other threads:[~2023-06-29  3:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 16:16 [syzbot] [ext4?] KASAN: use-after-free Read in ext4_find_extent (3) syzbot
2023-06-29  3:18 ` Theodore Ts'o [this message]
2024-01-27  9:05 ` syzbot
2024-01-27 21:58   ` Theodore Ts'o

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=20230629031852.GH8954@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+7ec4ebe875a7076ebb31@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 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.