From: Benjamin Marzinski <bmarzins@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
dm-devel@lists.linux.dev, Kevin Wolf <kwolf@redhat.com>,
Hanna Czenczek <hreitz@redhat.com>,
Martin Wilck <martin.wilck@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] dm-mpath: Don't grab work_mutex while probing paths
Date: Fri, 16 May 2025 15:16:12 -0400 [thread overview]
Message-ID: <aCeO_NeVLIrM0R-4@redhat.com> (raw)
In-Reply-To: <a6bbd5ee-492e-7a19-d884-52485e412a63@redhat.com>
On Fri, May 16, 2025 at 01:35:39PM +0200, Mikulas Patocka wrote:
>
>
> On Thu, 15 May 2025, Benjamin Marzinski wrote:
>
> > @@ -2077,35 +2095,55 @@ static int probe_path(struct pgpath *pgpath)
> > static int probe_active_paths(struct multipath *m)
> > {
> > struct pgpath *pgpath;
> > - struct priority_group *pg;
> > + struct priority_group *pg = NULL;
> > unsigned long flags;
> > int r = 0;
> >
> > - mutex_lock(&m->work_mutex);
> > -
> > spin_lock_irqsave(&m->lock, flags);
>
> Hi
>
> I suggest replacing spin_lock_irqsave/spin_unlock_irqrestore with
> spin_lock_irq/spin_unlock_irq here and in some other places where it is
> known that interrupts are enabled (for example __map_bio,
> process_queued_bios, multipath_ctr, flush_multipath_work,
> multipath_resume, multipath_status, multipath_prepare_ioctl, ...).
>
> I accepted this patch, so you can send the spinlock changes in a follow-up
> patch.
Sure. I can do that.
-Ben
>
> Mikulas
next prev parent reply other threads:[~2025-05-16 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 1:55 [PATCH] dm-mpath: Don't grab work_mutex while probing paths Benjamin Marzinski
2025-05-16 11:35 ` Mikulas Patocka
2025-05-16 19:16 ` Benjamin Marzinski [this message]
2025-05-19 13:50 ` [PATCH] dm mpath: replace spin_lock_irqsave with spin_lock_irq Mikulas Patocka
2025-05-20 3:56 ` Benjamin Marzinski
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=aCeO_NeVLIrM0R-4@redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=martin.wilck@suse.com \
--cc=mpatocka@redhat.com \
--cc=pbonzini@redhat.com \
--cc=snitzer@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.