From: syzbot <syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.com>
To: 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 09:32:04 -0800 [thread overview]
Message-ID: <67290514.050a0220.2edce.14f7.GAE@google.com> (raw)
In-Reply-To: <zgopoeun6qh6olzr7rogagibyhpdr4n42cakznftggwq6dwss2@4lyki4vw2dkr>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.com
Tested-by: syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.com
Tested on:
commit: 0012ab09 fs/proc: fix compile warning about variable '..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/ mm-hotfixes-unstable
console output: https://syzkaller.appspot.com/x/log.txt?x=11a42740580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4340261e4e9f37fc
dashboard link: https://syzkaller.appspot.com/bug?extid=dee8aa54cb2f5a150f9e
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-11-04 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 16:33 [syzbot] [kernel?] kernel BUG in binder_alloc_deferred_release (2) syzbot
2024-10-29 11:20 ` Hillf Danton
2024-10-29 12:01 ` syzbot
2024-11-04 16:21 ` syzbot
2024-11-04 16:26 ` Liam R. Howlett
2024-11-04 17:32 ` syzbot [this message]
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=67290514.050a0220.2edce.14f7.GAE@google.com \
--to=syzbot+dee8aa54cb2f5a150f9e@syzkaller.appspotmail.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=liam.howlett@oracle.com \
--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