All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, nilay@linux.ibm.com,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 1/2] nvme-multipath: fix leak on try_module_get failure
Date: Thu, 26 Feb 2026 16:35:18 +0100	[thread overview]
Message-ID: <20260226153518.GA31615@lst.de> (raw)
In-Reply-To: <20260225202109.447144-1-kbusch@meta.com>

On Wed, Feb 25, 2026 at 12:21:08PM -0800, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> We need to fall back to the synchronous removal if we can't get a
> reference on the module needed for the deferred removal.

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

But this should probably have a Fixes tag?



  parent reply	other threads:[~2026-02-26 15:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 20:21 [PATCH 1/2] nvme-multipath: fix leak on try_module_get failure Keith Busch
2026-02-25 20:21 ` [PATCH 2/2] nvme: fix unmatched id's under delayed path deletion Keith Busch
2026-02-25 20:34   ` Keith Busch
2026-02-26  7:04   ` Nilay Shroff
2026-02-26 15:37   ` Christoph Hellwig
2026-02-26 16:51     ` Keith Busch
2026-02-26 18:31       ` Nilay Shroff
2026-02-26 18:35         ` Keith Busch
2026-02-27 13:53           ` Christoph Hellwig
2026-02-26  6:35 ` [PATCH 1/2] nvme-multipath: fix leak on try_module_get failure Nilay Shroff
2026-02-26  8:31 ` John Garry
2026-02-26 15:35 ` Christoph Hellwig [this message]
2026-04-15  9:26 ` John Garry
2026-04-15 14:23   ` Keith Busch
2026-04-15 15:13     ` John Garry

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=20260226153518.GA31615@lst.de \
    --to=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.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.