All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: virtualization@lists.linux-foundation.org
Cc: debian-kernel@lists.debian.org,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: virtio_balloon regression in 5.19-rc3 #forregzbot
Date: Mon, 15 Aug 2022 14:36:05 +0200	[thread overview]
Message-ID: <e1fda21e-70dc-d660-c044-a9e663bf3a33@leemhuis.info> (raw)
In-Reply-To: <3b17592f-4118-5022-eaea-17b9059d3f0a@leemhuis.info>

On 10.07.22 10:06, Thorsten Leemhuis wrote:
> On 04.07.22 11:40, Thorsten Leemhuis wrote:
>> TWIMC: this mail is primarily send for documentation purposes and for
>> regzbot, my Linux kernel regression tracking bot. These mails usually
>> contain '#forregzbot' in the subject, to make them easy to spot and filter.
>>
>> On 21.06.22 11:35, Thorsten Leemhuis wrote:
>>> On 20.06.22 20:49, Ben Hutchings wrote:
>>>> I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type
>>>> pc-q35-5.2.  It has a virtio balloon device defined in libvirt as:
>>>>
>>>>     <memballoon model="virtio">
>>>>       <address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/>
>>>>     </memballoon>
>>>>
>>>> but the virtio_balloon driver fails to bind to it:
>>>>
>>>>     virtio_balloon virtio4: init_vqs: add stat_vq failed
>>>>     virtio_balloon: probe of virtio4 failed with error -5
>>>>
>>> [...]
>>> #regzbot ^introduced v5.18..v5.19-rc3
>>> #regzbot ignore-activity
>>
>> #regzbot introduced 8b4ec69d7e09
>> #regzbot monitor
>> https://lore.kernel.org/all/20220622012940.21441-1-jasowang@redhat.com/
> 
> #regzbot fixed-by: 6a9720576c
> #regzbot ignore-activity

For the record: the fix was merged through a different branch and thus
got a different commit id:

#regzbot fixed-by: ebe797f25f68f28581f46a9cb9c1997ac15c39a0

      reply	other threads:[~2022-08-15 12:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 18:49 virtio_balloon regression in 5.19-rc3 Ben Hutchings
2022-06-21  9:24 ` David Hildenbrand
2022-06-21  9:34   ` Jason Wang
2022-06-21 16:10     ` Ben Hutchings
2022-06-21 16:10       ` Ben Hutchings
2022-06-24  9:14       ` Michael S. Tsirkin
2022-06-24  9:14         ` Michael S. Tsirkin
2022-06-27  2:30         ` Jason Wang
2022-06-27  2:30           ` Jason Wang
2022-06-21  9:35 ` Thorsten Leemhuis
2022-07-04  9:40   ` virtio_balloon regression in 5.19-rc3 #forregzbot Thorsten Leemhuis
2022-07-10  8:06     ` Thorsten Leemhuis
2022-08-15 12:36       ` Thorsten Leemhuis [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=e1fda21e-70dc-d660-c044-a9e663bf3a33@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=debian-kernel@lists.debian.org \
    --cc=regressions@lists.linux.dev \
    --cc=virtualization@lists.linux-foundation.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 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.