All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9c28ada89c468ad30713@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] WARNING in futex_pivot_pending
Date: Sat, 15 Aug 2026 19:50:02 -0700	[thread overview]
Message-ID: <6a81255a.dbb3a75c.20434b.0027.GAE@google.com> (raw)
In-Reply-To: <tencent_D1C625FE0D8092505DCBDDE3993DCFFE0D07@qq.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+9c28ada89c468ad30713@syzkaller.appspotmail.com
Tested-by: syzbot+9c28ada89c468ad30713@syzkaller.appspotmail.com

Tested on:

commit:         21d6ac05 Merge branch 'for-next/core' into for-kernelci
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=11b2c6c6580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=95ac36a2cf7bfd28
dashboard link: https://syzkaller.appspot.com/bug?extid=9c28ada89c468ad30713
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1585e949580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2026-08-16  2:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 14:36 [syzbot] [kernel?] WARNING in futex_pivot_pending syzbot
2026-08-16  2:25 ` Edward Adam Davis
2026-08-16  2:50   ` syzbot [this message]
2026-08-17  4:48 ` Edward Adam Davis
2026-08-17  5:18   ` syzbot
2026-08-17  5:33 ` [PATCH] futex: Temporarily set the task state to running for pivot pending Edward Adam Davis

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=6a81255a.dbb3a75c.20434b.0027.GAE@google.com \
    --to=syzbot+9c28ada89c468ad30713@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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.