From: Keith Busch <kbusch@kernel.org>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me,
kch@nvidia.com, israelr@nvidia.com
Subject: Re: [PATCH 1/1] nvmet: add sanity checks when freeing subsystem
Date: Wed, 24 Sep 2025 16:14:29 -0600 [thread overview]
Message-ID: <aNRtRVvKBd3J3qF5@kbusch-mbp> (raw)
In-Reply-To: <20250924203544.11494-1-mgurtovoy@nvidia.com>
On Wed, Sep 24, 2025 at 11:35:44PM +0300, Max Gurtovoy wrote:
> Add WARN_ON_ONCE checks in nvmet_subsys_free() to ensure that the
> ctrls and hosts lists are all empty during subsystem release. This helps
> catch resource leaks.
Looks good, applied to nvme-6.18.
prev parent reply other threads:[~2025-09-24 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 20:35 [PATCH 1/1] nvmet: add sanity checks when freeing subsystem Max Gurtovoy
2025-09-24 22:14 ` Keith Busch [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=aNRtRVvKBd3J3qF5@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hch@lst.de \
--cc=israelr@nvidia.com \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
/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.