From: Christoph Hellwig <hch@lst.de>
To: Qing Zhang <diasyzhangqing@gmail.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmet: protect nvmet_ports_list with nvmet_config_sem
Date: Wed, 28 Oct 2026 15:46:15 +0100 [thread overview]
Message-ID: <20261028144615.GA14239@lst.de> (raw)
In-Reply-To: <179275538809.275862.8334230595898232727@tencent.com>
Btw, I had some old patches here:
https://git.infradead.org/?p=users/hch/misc.git;a=shortlog;h=refs/heads/cap-analysis
to add clang lock context analysis (still called capability analysis
back then to nvmet) to annotate and verify the locking scheme. It
would be great if someone could take on that work.
prev parent reply other threads:[~2026-10-28 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 11:36 [PATCH] nvmet: protect nvmet_ports_list with nvmet_config_sem Qing Zhang
2026-10-23 12:16 ` Maurizio Lombardi
2026-10-23 22:47 ` Keith Busch
2026-10-28 14:46 ` Christoph Hellwig [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=20261028144615.GA14239@lst.de \
--to=hch@lst.de \
--cc=diasyzhangqing@gmail.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox