From: Benjamin Marzinski <bmarzins@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>, Mike Snitzer <snitzer@kernel.org>
Cc: dm-devel@lists.linux.dev
Subject: Re: [PATCH 0/2] dm: mpath dm_get_device fix
Date: Mon, 10 Jun 2024 14:12:18 -0400 [thread overview]
Message-ID: <ZmdCAlEPN8Lmd5XQ@redhat.com> (raw)
In-Reply-To: <20240517004129.139615-1-bmarzins@redhat.com>
On Thu, May 16, 2024 at 08:41:27PM -0400, Benjamin Marzinski wrote:
ping.
> dm-mpath shouldn't be calling dm_get_device() in multipath_message().
> If you run:
>
> # dmsetup message <mpath_dev> 0 "fail_path <device_not_in_multipath>"
>
> the dm_get_device() call in multipath_message() will add that incorrect
> device to the devices list, fail to find a matching pgpath, and then
> remove it. multipath shouldn't be messing with the devices table
> outside of its constructor and destructor.
>
> To fix it, this patchset factors out a helper function from
> dm_get_device() to turn the device path string into a dev_t.
> multipath_message() calls that helper function and uses the dev_t to
> find the correct pgpath instead.
>
> Benjamin Marzinski (2):
> dm: factor out helper function from dm_get_device
> dm mpath: don't call dm_get_device in multipath_message
>
> drivers/md/dm-mpath.c | 11 ++++-------
> drivers/md/dm-table.c | 33 ++++++++++++++++++++++++---------
> include/linux/device-mapper.h | 5 +++++
> 3 files changed, 33 insertions(+), 16 deletions(-)
>
> --
> 2.45.0
>
next prev parent reply other threads:[~2024-06-10 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 0:41 [PATCH 0/2] dm: mpath dm_get_device fix Benjamin Marzinski
2024-05-17 0:41 ` [PATCH 1/2] dm: factor out helper function from dm_get_device Benjamin Marzinski
2024-05-17 0:41 ` [PATCH 2/2] dm mpath: don't call dm_get_device in multipath_message Benjamin Marzinski
2024-06-10 18:12 ` Benjamin Marzinski [this message]
2024-07-04 15:06 ` [PATCH 0/2] dm: mpath dm_get_device fix Mikulas Patocka
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=ZmdCAlEPN8Lmd5XQ@redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
/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.