From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: bugs@lists.linux.dev
Subject: Re: Kernel panic on adding vCPU to guest in Linux 6.9-rc2
Date: Wed, 10 Apr 2024 16:15:13 +0000 [thread overview]
Message-ID: <20240410-b218698c3-17ea12e474b7@bugzilla.kernel.org> (raw)
In-Reply-To: <20240410-b218698c0-cb3e9db062a2@bugzilla.kernel.org>
regressions writes via Kernel.org Bugzilla:
Like fixed in rc4, see https://lore.kernel.org/all/87bk6h49tq.ffs@tglx/
Side note: Artem reassigned this to Virtualization, I don't think that was wise, but whatever, I don't care bout bugzilla.
View: https://bugzilla.kernel.org/show_bug.cgi?id=218698#c3
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next prev parent reply other threads:[~2024-04-10 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 16:15 Kernel panic on adding vCPU to guest in Linux 6.9-rc2 Kernel.org Bugbot
2024-04-10 16:15 ` Kernel.org Bugbot
2024-04-10 16:15 ` Kernel.org Bugbot
2024-04-10 16:15 ` Kernel.org Bugbot [this message]
2024-04-10 16:15 ` Kernel.org Bugbot
2024-04-10 19:50 ` Kernel.org Bugbot
2024-04-17 7:25 ` Kernel.org Bugbot
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=20240410-b218698c3-17ea12e474b7@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
/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).