From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-kernel@vger.kernel.org,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: linux-fsdevel@vger.kernel.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: Re: Commit 'iomap: add support for dma aligned direct-io' causes qemu/KVM boot failures #forregzbot
Date: Fri, 4 Nov 2022 12:59:49 +0100 [thread overview]
Message-ID: <db612736-1704-e2c0-0223-675f8ffacc76@leemhuis.info> (raw)
In-Reply-To: <99249078-2026-c76c-87eb-8e3ac5dde73d@leemhuis.info>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 30.09.22 13:52, Thorsten Leemhuis wrote:
>
> Hi, this is your Linux kernel regression tracker. This might be a Qemu
> bug, but it's exposed by kernel change, so I at least want to have it in
> the tracking. I'll simply remove it in a few weeks, if it turns out that
> nobody except Maxim hits this.
There was one more report:
https://lore.kernel.org/all/20221020031725.7d01051a@xps.demsh.org/
But that's it so far. I'll put this to rest for now:
#regzbot monitor:
https://lore.kernel.org/all/20221020031725.7d01051a@xps.demsh.org/
#regzbot invalid: a kernel change exposed a bug in qemu that maybe still
needs to be fixed, *if* more people run into this
prev parent reply other threads:[~2022-11-04 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 15:41 Commit 'iomap: add support for dma aligned direct-io' causes qemu/KVM boot failures Maxim Levitsky
2022-09-29 15:48 ` Keith Busch
2022-09-29 16:16 ` Maxim Levitsky
2022-09-29 16:37 ` Keith Busch
2022-09-29 16:39 ` Christoph Hellwig
2022-09-29 17:35 ` Paolo Bonzini
2022-10-02 8:59 ` Maxim Levitsky
2022-10-02 13:56 ` Keith Busch
2022-10-03 7:06 ` Maxim Levitsky
2022-09-30 11:52 ` Thorsten Leemhuis
2022-11-04 11:59 ` 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=db612736-1704-e2c0-0223-675f8ffacc76@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=regressions@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).