From: Carlos Llamas <cmllamas@google.com>
To: syzbot <syzbot+799a2d4576c454ac2693@syzkaller.appspotmail.com>
Cc: arve@android.com, brauner@kernel.org, gregkh@linuxfoundation.org,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
maco@android.com, surenb@google.com,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] [kernel?] possible deadlock in binder_alloc_free_page
Date: Tue, 25 Mar 2025 00:41:23 +0000 [thread overview]
Message-ID: <Z-H7sxU0WoeOpcef@google.com> (raw)
In-Reply-To: <6782483e.050a0220.216c54.001d.GAE@google.com>
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
prev parent reply other threads:[~2025-03-25 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 10:30 [syzbot] [kernel?] possible deadlock in binder_alloc_free_page syzbot
2025-01-11 13:15 ` Hillf Danton
2025-01-11 13:32 ` syzbot
2025-01-12 0:11 ` Hillf Danton
2025-01-12 0:33 ` syzbot
2025-01-12 1:48 ` Hillf Danton
2025-01-12 2:06 ` syzbot
2025-02-19 18:35 ` Carlos Llamas
2025-02-19 18:41 ` Suren Baghdasaryan
2025-03-25 0:41 ` 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=Z-H7sxU0WoeOpcef@google.com \
--to=cmllamas@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=syzbot+799a2d4576c454ac2693@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox