All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a1a3cefd6148c781117c@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, luto@kernel.org, mst@redhat.com,
	 peterz@infradead.org, seanjc@google.com,
	syzkaller-bugs@googlegroups.com,  tglx@linutronix.de
Subject: Re: [syzbot] [kernel?] WARNING in __vhost_task_wake
Date: Thu, 18 Sep 2025 08:52:05 -0700	[thread overview]
Message-ID: <68cc2aa5.a00a0220.37dadf.0001.GAE@google.com> (raw)
In-Reply-To: <aMwdsFGkM-tMjHwc@google.com>

Hello,

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

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

Tested on:

commit:         ae2d2000 Add linux-next specific files for 20250917
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1070cf62580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d737cfaddae0058c
dashboard link: https://syzkaller.appspot.com/bug?extid=a1a3cefd6148c781117c
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14bca534580000

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

      parent reply	other threads:[~2025-09-18 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 17:14 [syzbot] [kernel?] WARNING in __vhost_task_wake syzbot
2025-09-18  1:46 ` syzbot
2025-09-18 14:56   ` Sean Christopherson
2025-09-18 15:02     ` Michael S. Tsirkin
2025-09-18 15:52     ` syzbot [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=68cc2aa5.a00a0220.37dadf.0001.GAE@google.com \
    --to=syzbot+a1a3cefd6148c781117c@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mst@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    /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.