[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z-H7sxU0WoeOpcef@google.com>
Date: Tue, 25 Mar 2025 00:41:23 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: syzbot <syzbot+799a2d4576c454ac2693@...kaller.appspotmail.com>
Cc: arve@...roid.com, brauner@...nel.org, gregkh@...uxfoundation.org,
joel@...lfernandes.org, linux-kernel@...r.kernel.org,
maco@...roid.com, surenb@...gle.com,
syzkaller-bugs@...glegroups.com, tkjos@...roid.com
Subject: Re: [syzbot] [kernel?] possible deadlock in binder_alloc_free_page
On Sat, Jan 11, 2025 at 02:30:22AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 7b4b9bf203da Add linux-next specific files for 20250107
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17d02dc4580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=63fa2c9d5e12faef
> dashboard link: https://syzkaller.appspot.com/bug?extid=799a2d4576c454ac2693
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10302dc4580000
This was fixed by a new version of commit e8f32ff00a66 ("mm: replace
vm_lock and detached flag with a reference count"), making this report
now obsolete.
#syz invalid
Powered by blists - more mailing lists