From: "Michal Koutný" <mkoutny@suse.com>
To: syzbot <syzbot+b4529efee5bf3751bc06@syzkaller.appspotmail.com>
Cc: cgroups@vger.kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: Re: [syzbot] [cgroups?] possible deadlock in try_to_wake_up (8)
Date: Mon, 16 Jun 2025 11:50:36 +0200 [thread overview]
Message-ID: <yo75qoe44ltntzu6qcyscsj2nluae52mfr52gap2uypqtpn4qk@jvfbspevdavp> (raw)
In-Reply-To: <684d16c0.050a0220.be214.02ad.GAE@google.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Fri, Jun 13, 2025 at 11:29:20PM -0700, syzbot <syzbot+b4529efee5bf3751bc06@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 39dfc971e42d arm64/ptrace: Fix stack-out-of-bounds read in..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=12fcb10c580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=941e423b930a32dc
> dashboard link: https://syzkaller.appspot.com/bug?extid=b4529efee5bf3751bc06
> compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
> userspace arch: arm64
This looks very equal to
Subject: [syzbot] [cgroups?] WARNING in NUM (2)
Message-ID: <684f296b.a00a0220.279073.0033.GAE@google.com>
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-06-16 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 6:29 [syzbot] [cgroups?] possible deadlock in try_to_wake_up (8) syzbot
2025-06-16 9:50 ` Michal Koutný [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=yo75qoe44ltntzu6qcyscsj2nluae52mfr52gap2uypqtpn4qk@jvfbspevdavp \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+b4529efee5bf3751bc06@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).