From: Carlos Llamas <cmllamas@google.com>
To: syzbot <syzbot+c3763f82ee2ceaf93340@syzkaller.appspotmail.com>
Cc: arve@android.com, brauner@kernel.org, gregkh@linuxfoundation.org,
joelagnelf@nvidia.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, maco@android.com,
sfr@canb.auug.org.au, surenb@google.com,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] [kernel?] linux-next test error: KASAN: slab-use-after-free Write in binderfs_evict_inode
Date: Sat, 17 May 2025 17:16:19 +0000 [thread overview]
Message-ID: <aCjEY1X85xUne3Ix@google.com> (raw)
In-Reply-To: <6827b414.a70a0220.38f255.0008.GAE@google.com>
On Fri, May 16, 2025 at 02:54:28PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8566fc3b9653 Add linux-next specific files for 20250516
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10b776f4580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=aa3444b6d01e5afb
> dashboard link: https://syzkaller.appspot.com/bug?extid=c3763f82ee2ceaf93340
> compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/ac394ca3c315/disk-8566fc3b.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/170dd88bde87/vmlinux-8566fc3b.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c097fa83c7d7/bzImage-8566fc3b.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+c3763f82ee2ceaf93340@syzkaller.appspotmail.com
>
#syz dup: upstream test error: KASAN: slab-use-after-free Write in binderfs_evict_inode
This is a dup for which Dmitry had sent out a fix for. However, Greg was
never cc'ed so the patch was left in limbo. v2 sent here:
https://lore.kernel.org/all/20250517170957.1317876-1-cmllamas@google.com/
prev parent reply other threads:[~2025-05-17 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 21:54 [syzbot] [kernel?] linux-next test error: KASAN: slab-use-after-free Write in binderfs_evict_inode syzbot
2025-05-17 17:16 ` Carlos Llamas [this message]
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=aCjEY1X85xUne3Ix@google.com \
--to=cmllamas@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maco@android.com \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--cc=syzbot+c3763f82ee2ceaf93340@syzkaller.appspotmail.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 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.