All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2751da923b5eb8307b0b@syzkaller.appspotmail.com>
To: anton@tuxera.com, brauner@kernel.org, linkinjeon@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net, linux@roeck-us.net,
	phil@philpotter.co.uk, syzkaller-bugs@googlegroups.com,
	torvalds@linux-foundation.org
Subject: Re: [syzbot] [ntfs?] KASAN: use-after-free Read in ntfs_test_inode
Date: Sun, 24 Sep 2023 18:15:29 -0700	[thread overview]
Message-ID: <000000000000a27dcc060624b16e@google.com> (raw)
In-Reply-To: <000000000000b782b505c2847180@google.com>

syzbot has bisected this issue to:

commit 78a06688a4d40d9bb6138e2b9ad3353d7bf0157a
Author: Christian Brauner <brauner@kernel.org>
Date:   Thu Sep 7 16:03:40 2023 +0000

    ntfs3: drop inode references in ntfs_put_super()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1674a5c1680000
start commit:   3aba70aed91f Merge tag 'gpio-fixes-for-v6.6-rc3' of git://..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1574a5c1680000
console output: https://syzkaller.appspot.com/x/log.txt?x=1174a5c1680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e4ca82a1bedd37e4
dashboard link: https://syzkaller.appspot.com/bug?extid=2751da923b5eb8307b0b
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=136b4412680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11aec0dc680000

Reported-by: syzbot+2751da923b5eb8307b0b@syzkaller.appspotmail.com
Fixes: 78a06688a4d4 ("ntfs3: drop inode references in ntfs_put_super()")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2023-09-25  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 10:56 [syzbot] KASAN: use-after-free Read in ntfs_test_inode syzbot
2023-09-24 16:39 ` [syzbot] [ntfs?] " syzbot
2023-09-25  1:15 ` syzbot [this message]
2023-09-25 13:14   ` Christian Brauner
2023-09-25 13:43     ` 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=000000000000a27dcc060624b16e@google.com \
    --to=syzbot+2751da923b5eb8307b0b@syzkaller.appspotmail.com \
    --cc=anton@tuxera.com \
    --cc=brauner@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=linux@roeck-us.net \
    --cc=phil@philpotter.co.uk \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    /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.