From: syzbot <syzbot+48011b86c8ea329af1b9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hch@lst.de, jack@suse.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [udf?] KASAN: null-ptr-deref Read in filemap_fault
Date: Wed, 03 May 2023 02:23:19 -0700 [thread overview]
Message-ID: <0000000000004a34a305fac69bcb@google.com> (raw)
In-Reply-To: <00000000000090900c05fa656913@google.com>
syzbot has bisected this issue to:
commit 66dabbb65d673aef40dd17bf62c042be8f6d4a4b
Author: Christoph Hellwig <hch@lst.de>
Date: Tue Mar 7 14:34:10 2023 +0000
mm: return an ERR_PTR from __filemap_get_folio
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15220608280000
start commit: 865fdb08197e Merge tag 'input-for-v6.4-rc0' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17220608280000
console output: https://syzkaller.appspot.com/x/log.txt?x=13220608280000
kernel config: https://syzkaller.appspot.com/x/.config?x=d1c8518c09009bad
dashboard link: https://syzkaller.appspot.com/bug?extid=48011b86c8ea329af1b9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137594c4280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10cfd602280000
Reported-by: syzbot+48011b86c8ea329af1b9@syzkaller.appspotmail.com
Fixes: 66dabbb65d67 ("mm: return an ERR_PTR from __filemap_get_folio")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-05-03 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 13:25 [syzbot] [mm?] [net?] KASAN: null-ptr-deref Read in filemap_fault syzbot
2023-05-02 20:54 ` [syzbot] [mm?] [udf?] " syzbot
2023-05-03 9:23 ` syzbot [this message]
2023-05-03 12:23 ` Jan Kara
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=0000000000004a34a305fac69bcb@google.com \
--to=syzbot+48011b86c8ea329af1b9@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--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.