public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: James Smart <james.smart@broadcom.com>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
	Hannes Reinecke <hare@suse.de>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	Daniel Wagner <dwagner@suse.de>
Subject: [PATCH v4 00/12] enable nvmet-fc for blktests
Date: Tue, 30 Jan 2024 10:49:26 +0100	[thread overview]
Message-ID: <20240130094938.1575-1-dwagner@suse.de> (raw)

The first version which allows to run blktests in loop without crashing or
hanging forever somewhere. The missing fix was the argument swap patch
for list_add_tail, which ensured no response gets dropped on tbe floor.

Note, this runs with the udev auto connect rule running in the background which
injects a lot of additional noise to the test. For example blktests will warn
about 'device not removed', which is correct but this device was not created by
the test, it was created by the udev rule. nvme/003 fails because it disconnects
two devices instead the exptected one.

These are things we have to address in blktests though. So hopefully with these
patches we are getting close to run blktests on a regular basis.

changes:
v4:
 - dropped patches which got applied
 - dropped 'nvmet-fc: free hostport after release reference to tgtport'
 - reworked commit message of 'nvmet-fc: untangle cross refcounting objects'
   and renamed it to 'nvmet-fc: defer cleanup using RCU properly'
 - added 'nvmet-fcloop: swap the list_add_tail arguments'
   and 'nvmet-fc: use RCU list iterator for assoc_list'
 - added RBs
 
v3:
 - collected all patches into one series
 - updated ref counting in nvmet-fc

v2:
  - added RBs
  - added new patches
  - https://lore.kernel.org/linux-nvme/20230620133711.22840-1-dwagner@suse.de/
  
v1:
  - https://lore.kernel.org/linux-nvme/20230615094356.14878-1-dwagner@suse.de/ 


*** BLURB HERE ***

Daniel Wagner (12):
  nvme-fc: do not wait in vain when unloading module
  nvmet-fcloop: swap the list_add_tail arguments
  nvmet-fc: release reference on target port
  nvmet-fc: defer cleanup using RCU properly
  nvmet-fc: free queue and assoc directly
  nvmet-fc: hold reference on hostport match
  nvmet-fc: remove null hostport pointer check
  nvmet-fc: do not tack refs on tgtports from assoc
  nvmet-fc: abort command when there is no binding
  nvmet-fc: avoid deadlock on delete association path
  nvmet-fc: take ref count on tgtport before delete assoc
  nvmet-fc: use RCU list iterator for assoc_list

 drivers/nvme/host/fc.c       |  47 ++---------
 drivers/nvme/target/fc.c     | 156 +++++++++++++++++++----------------
 drivers/nvme/target/fcloop.c |   6 +-
 3 files changed, 93 insertions(+), 116 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-01-30  9:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  9:49 Daniel Wagner [this message]
2024-01-30  9:49 ` [PATCH v4 01/12] nvme-fc: do not wait in vain when unloading module Daniel Wagner
2024-01-30  9:49 ` [PATCH v4 02/12] nvmet-fcloop: swap the list_add_tail arguments Daniel Wagner
2024-01-31  6:26   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 03/12] nvmet-fc: release reference on target port Daniel Wagner
2024-01-31  6:26   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 04/12] nvmet-fc: defer cleanup using RCU properly Daniel Wagner
2024-01-31  6:26   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 05/12] nvmet-fc: free queue and assoc directly Daniel Wagner
2024-01-31  6:27   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 06/12] nvmet-fc: hold reference on hostport match Daniel Wagner
2024-01-31  6:27   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 07/12] nvmet-fc: remove null hostport pointer check Daniel Wagner
2024-01-31  6:27   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 08/12] nvmet-fc: do not tack refs on tgtports from assoc Daniel Wagner
2024-01-31  6:28   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 09/12] nvmet-fc: abort command when there is no binding Daniel Wagner
2024-01-31  6:28   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 10/12] nvmet-fc: avoid deadlock on delete association path Daniel Wagner
2024-01-31  6:28   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 11/12] nvmet-fc: take ref count on tgtport before delete assoc Daniel Wagner
2024-01-31  6:28   ` Christoph Hellwig
2024-01-30  9:49 ` [PATCH v4 12/12] nvmet-fc: use RCU list iterator for assoc_list Daniel Wagner
2024-01-31  6:29   ` Christoph Hellwig

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=20240130094938.1575-1-dwagner@suse.de \
    --to=dwagner@suse.de \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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