All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+70f57d8a3ae84934c003@syzkaller.appspotmail.com>
To: jasowang@redhat.com, linux-kernel@vger.kernel.org,
	 michael.christie@oracle.com, mst@redhat.com, osalvador@suse.de,
	 pbonzini@redhat.com, stefanha@redhat.com,
	syzkaller-bugs@googlegroups.com,  virtualization@lists.linux.dev,
	xuanzhuo@linux.alibaba.com
Subject: Re: [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok
Date: Wed, 20 Mar 2024 13:08:02 -0700	[thread overview]
Message-ID: <000000000000e4b57b06141d250c@google.com> (raw)
In-Reply-To: <20240320113002.GA1178948@fedora>

Hello,

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

Reported-and-tested-by: syzbot+70f57d8a3ae84934c003@syzkaller.appspotmail.com

Tested on:

commit:         4bedfb31 mm,page_owner: maintain own list of stack_rec..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=527195e149aa3091
dashboard link: https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-03-20 20:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  7:32 [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok syzbot
2024-03-19  7:40 ` Michael S. Tsirkin
2024-03-19 17:19   ` Stefan Hajnoczi
2024-03-19 17:47     ` Michael S. Tsirkin
2024-03-19 20:51     ` Mike Christie
2024-03-20 11:30       ` Stefan Hajnoczi
2024-03-20 20:08         ` syzbot [this message]
2024-03-21 12:07           ` Stefan Hajnoczi
2024-03-21 15:52             ` syzbot
2024-03-21 17:13               ` Stefan Hajnoczi
2024-03-19 18:59   ` Stefan Hajnoczi
2024-03-20  6:12     ` syzbot
2024-03-26 11:14 ` Tetsuo Handa
2024-04-20  9:22   ` Tetsuo Handa

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=000000000000e4b57b06141d250c@google.com \
    --to=syzbot+70f57d8a3ae84934c003@syzkaller.appspotmail.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.christie@oracle.com \
    --cc=mst@redhat.com \
    --cc=osalvador@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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.