All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <mwilck@suse.com>
Cc: Brian Bunker <brian@purestorage.com>,
	Hannes Reinecke <hare@suse.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	dm-devel@lists.linux.dev
Subject: Re: udev / multipath-tools: WWID determination with SG_IO vs. sysfs
Date: Fri, 13 Nov 2026 11:44:34 -0500	[thread overview]
Message-ID: <avc-ctvpTR9COos5@redhat.com> (raw)
In-Reply-To: <b087c205fa86ccda6743ebcdafb7e5340234a4af.camel@suse.com>

On Thu, Nov 12, 2026 at 09:47:54PM +0100, Martin Wilck wrote:
> On Thu, 2026-11-12 at 14:58 -0500, Benjamin Marzinski wrote:
> > On Thu, Nov 12, 2026 at 08:00:58PM +0100, Martin Wilck wrote:
> > 
> >  
> > > Brian's patch would add more such ioctls and thus increase the
> > > likelihood of observing a stall. To be observed.
> > > 
> > 
> > This is true, and unlike the existing recheck_wwids use and the
> > prioritizer, it won't be called right after the path checker
> > determined
> > a path to be up. We do also do SG_IO ioctls in pathinfo when DI_IOCTL
> > is
> > set (when we're adding a path, reconfiguring multipath, or
> > initializing
> > a partial path). In that case we do check if the path is up according
> > to
> > sysfs first, but we don't call the checker.
> 
> So, would you prefer making it conditional on something else but
> "recheck_wwid"?

Since recheck_wwid is set, we could just limit this new
check_path_wwid_change() check in ev_add_path() to paths that are up.
uev_add_path() will run the path checker before we get here. If the path
isn't up, recheck_wwid guarantees that we will do the check when the
path is up.

That should make this no more risky than the existing recheck_wwid
calls.

-Ben
 
> Martin
> 
> -- 
> Dr. Martin Wilck <mwilck@suse.com>
> SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg,
> Germany
> Geschäftsführer: Stefan Gaiser, Jochen Jaser, Abhinav Puri (HRB
> 36809,AG Nürnberg)


  reply	other threads:[~2026-11-13 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 18:55 [PATCH v3 0/1] multipathd: check re-added paths' WWIDs against sysfs Brian Bunker
2026-11-09 18:55 ` [PATCH v3 1/1] " Brian Bunker
2026-11-09 22:24   ` Benjamin Marzinski
2026-11-10 22:21 ` [PATCH v3 0/1] " Martin Wilck
2026-11-11 17:42   ` Brian Bunker
2026-11-11 19:35     ` Martin Wilck
2026-11-11 23:05       ` Brian Bunker
2026-11-12 19:00         ` udev / multipath-tools: WWID determination with SG_IO vs. sysfs Martin Wilck
2026-11-12 19:58           ` Benjamin Marzinski
2026-11-12 20:47             ` Martin Wilck
2026-11-13 16:44               ` Benjamin Marzinski [this message]
2026-11-13 19:43           ` Brian Bunker
2026-11-13 22:26             ` Martin Wilck

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=avc-ctvpTR9COos5@redhat.com \
    --to=bmarzins@redhat.com \
    --cc=brian@purestorage.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=hare@suse.com \
    --cc=mwilck@suse.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.