From: Martin Wilck <martin.wilck@suse.com>
To: Benjamin Marzinski <bmarzins@redhat.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 0/2] libmpathpersist: reserve and release fixes
Date: Wed, 11 Jun 2025 22:12:25 +0200 [thread overview]
Message-ID: <b32c2ff2aee026821dacd01fd845ecdad662152d.camel@suse.com> (raw)
In-Reply-To: <20250604033504.2121566-1-bmarzins@redhat.com>
On Tue, 2025-06-03 at 23:35 -0400, Benjamin Marzinski wrote:
> These are two patches libmpathpersist patches. The first deals with a
> possible race condition where mpath_prout_common() can fail because a
> path went down after libmpathpersist checked its status but before it
> handled the prout command. Previously libmpathpersist wouldn't fail
> without ever trying another path in these cases. The second patch
> keeps libmpathpersit from being able to remove a reservation that
> is held by a different key than the releasing device.
>
> Benjamin Marzinski (2):
> libmpathpersist: retry commands on other paths in
> mpath_prout_common
> libmpathpersist: check released key against the reservation key
>
> libmpathpersist/mpath_persist.h | 3 +++
> libmpathpersist/mpath_persist_int.c | 20 ++++++++++++++++----
> libmpathpersist/mpath_pr_ioctl.c | 24 +++++++++++++-----------
> 3 files changed, 32 insertions(+), 15 deletions(-)
For the series:
Reviewed-by: Martin Wilck <mwilck@suse.com>
prev parent reply other threads:[~2025-06-11 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 3:35 [PATCH 0/2] libmpathpersist: reserve and release fixes Benjamin Marzinski
2025-06-04 3:35 ` [PATCH 1/2] libmpathpersist: retry commands on other paths in mpath_prout_common Benjamin Marzinski
2025-06-04 3:35 ` [PATCH 2/2] libmpathpersist: check released key against the reservation key Benjamin Marzinski
2025-06-11 20:12 ` Martin Wilck [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=b32c2ff2aee026821dacd01fd845ecdad662152d.camel@suse.com \
--to=martin.wilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@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 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.