From: syzbot <syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.com>
To: Liam.Howlett@Oracle.com, akpm@linux-foundation.org,
arve@android.com, brauner@kernel.org, cmllamas@google.com,
gregkh@linuxfoundation.org, hdanton@sina.com,
joel@joelfernandes.org, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, lorenzo.stoakes@oracle.com,
maco@android.com, surenb@google.com,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] [kernel?] kernel BUG in binder_alloc_deferred_release (2)
Date: Mon, 04 Nov 2024 08:21:03 -0800 [thread overview]
Message-ID: <6728f46f.050a0220.2edce.14f6.GAE@google.com> (raw)
In-Reply-To: <671fbcd6.050a0220.21b2f.0009.GAE@google.com>
syzbot has bisected this issue to:
commit f8d112a4e657c65c888e6b8a8435ef61a66e4ab8
Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
Date: Fri Aug 30 04:00:54 2024 +0000
mm/mmap: avoid zeroing vma tree in mmap_region()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11fc46a7980000
start commit: c2ee9f594da8 KVM: selftests: Fix build on on non-x86 archi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13fc46a7980000
console output: https://syzkaller.appspot.com/x/log.txt?x=15fc46a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a34ca8ca33c0e535
dashboard link: https://syzkaller.appspot.com/bug?extid=dee8aa54cb2f5a150f9e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1484165f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=132b2ebb980000
Reported-by: syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.com
Fixes: f8d112a4e657 ("mm/mmap: avoid zeroing vma tree in mmap_region()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-04 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 16:33 syzbot
2024-10-29 11:20 ` Hillf Danton
2024-10-29 12:01 ` syzbot
2024-11-04 16:21 ` syzbot [this message]
2024-11-04 16:26 ` Liam R. Howlett
2024-11-04 17:32 ` syzbot
2024-12-13 1:55 ` 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=6728f46f.050a0220.2edce.14f6.GAE@google.com \
--to=syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkjos@android.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
all inboxes | Powered by JetHome®