From: Eric Biggers <ebiggers@kernel.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, hreitz@redhat.com, qemu-block@nongnu.org,
nsoffer@redhat.com
Subject: Re: [PATCH 1/2] file-posix: fix Linux alignment probing when EIO is returned
Date: Thu, 3 Nov 2022 16:54:09 +0000 [thread overview]
Message-ID: <Y2PyMb4UluN6+ONg@gmail.com> (raw)
In-Reply-To: <Y2PrpOCjKsZ+rywG@gmail.com>
On Thu, Nov 03, 2022 at 04:26:14PM +0000, Eric Biggers wrote:
> > In other words, STATX_DIOALIGN is unusable from the start because we
> > don't know whether the information it returns is actually correct? :-/
>
> That's a silly point of view. STATX_DIOALIGN has only been in a released kernel
> for a few weeks (v6.0), the bug is only in one edge case, and it will get fixed
> quickly and backported to v6.0.y where users of 6.0 will get it.
Actually, scratch that. STATX_DIOALIGN is in 6.1, not 6.0. So it hasn't even
been released yet. Upstream is currently on v6.1-rc3.
So thank you for reporting (or for not reporting?) this. We'll make sure it
gets fixed before release :-)
- Eric
next prev parent reply other threads:[~2022-11-03 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 19:00 [PATCH 0/2] file-posix: alignment probing improvements Stefan Hajnoczi
2022-11-01 19:00 ` [PATCH 1/2] file-posix: fix Linux alignment probing when EIO is returned Stefan Hajnoczi
2022-11-02 2:27 ` Eric Biggers
2022-11-02 2:49 ` Eric Biggers
2022-11-02 18:50 ` Stefan Hajnoczi
2022-11-03 9:52 ` Kevin Wolf
2022-11-03 13:57 ` Stefan Hajnoczi
2022-11-03 16:26 ` Eric Biggers
2022-11-03 16:54 ` Eric Biggers [this message]
2022-11-03 17:54 ` Stefan Hajnoczi
2022-11-01 19:00 ` [PATCH 2/2] file-posix: add statx(STATX_DIOALIGN) support Stefan Hajnoczi
2022-11-02 3:32 ` Eric Biggers
2022-11-02 18:53 ` Stefan Hajnoczi
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=Y2PyMb4UluN6+ONg@gmail.com \
--to=ebiggers@kernel.org \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.