From: Kevin Wolf <kwolf@redhat.com>
To: Hanna Czenczek <hreitz@redhat.com>
Cc: qemu-block@nongnu.org, qinwang@redhat.com, bmarzins@redhat.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH for-10.2] file-posix: Handle suspended dm-multipath better for SG_IO
Date: Thu, 4 Dec 2025 11:44:08 +0100 [thread overview]
Message-ID: <aTFl-MGoI9asqwkX@redhat.com> (raw)
In-Reply-To: <1c7784d0-8952-4b4f-9a5e-923bdaef9f2f@redhat.com>
Am 03.12.2025 um 18:27 hat Hanna Czenczek geschrieben:
> On 28.11.25 23:14, Kevin Wolf wrote:
> > When introducing DM_MPATH_PROBE_PATHS, we already anticipated that
> > dm-multipath devices might be suspended for a short time when the DM
> > tables are reloaded and that they return -EAGAIN in this case. The
> > behaviour promised in the comment wasn't actually implemented, though:
> > We don't get SG_IO_MAX_RETRIES in practice, because after the first
> > 1ms sleep, DM_MPATH_PROBE_PATHS is called and if that still fails with
> > -EAGAIN, we error out immediately without any retry.
>
> How so? `hdev_co_ioctl_sgio_retry()` is what issues `DM_MPATH_PROBE_PATHS`,
> and if it gets `-EAGAIN` it will return `true`, requesting a retry.
Oops... You're right. I somehow ended up testing the old state with a
commit that isn't exactly the same as what went into master and it
didn't have the -EAGAIN special case yet. So this is just me running and
looking at the wrong version of the code.
Unfortunately, it's too late to fix the commit message now. But then,
it's only a random comment about the previous state and doesn't really
make a difference for this patch.
Kevin
prev parent reply other threads:[~2025-12-04 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 22:14 [PATCH for-10.2] file-posix: Handle suspended dm-multipath better for SG_IO Kevin Wolf
2025-12-03 17:27 ` Hanna Czenczek
2025-12-04 10:44 ` Kevin Wolf [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=aTFl-MGoI9asqwkX@redhat.com \
--to=kwolf@redhat.com \
--cc=bmarzins@redhat.com \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qinwang@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 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).