From: Lee Duncan <lduncan@suse.com>
To: Lee Duncan <leeman.duncan@gmail.com>,
linux-scsi@vger.kernel.org, open-iscsi@googlegroups.com,
netdev@vger.kernel.org
Subject: Re: [RFC 0/9] Make iscsid-kernel communications namespace-aware (resent)
Date: Wed, 8 Feb 2023 11:23:07 -0800 [thread overview]
Message-ID: <f911472c-c4a1-27ee-8671-037f330096f0@suse.com> (raw)
In-Reply-To: <cover.1675876731.git.lduncan@suse.com>
[Resent to include all mailing lists]
I wanted to mention some issues I've discovered as part of testing this:
- Currently, only some sysfs entries are going to be different
per namespace
- This means that the Configuration and Initiator Name are going to
be common to all running daemons (this is /etc/iscsi)
- This also means that the Node database (and discovery DB,
and interface DB) are common to all running daemons
I'm really not sure all running daemons should have the same initiator
name. If we think of them as separate initiators, then this seems wrong.
Sharing the Node database may not be a good idea, either. This assumes
that nodes discovered (and saved) from one namespace can actually be
reached from other namespaces, but this may not be true. Having the Node
DB and initiatorname shared means the different iscsid instances must
cooperate with each other, else their requests can collide. Also, I can
imagine situations where different daemons may want to set different
configuration values. Currently they cannot.
On 2/8/23 09:40, Lee Duncan wrote:
> From: Lee Duncan <lduncan@suse.com>
>
> This is a request for comment on a set of patches that
> modify the kernel iSCSI initiator communications so that
> they are namespace-aware. The goal is to allow multiple
> iSCSI daemon (iscsid) to run at once as long as they
> are in separate namespaces, and so that iscsid can
> run in containers.
>
> Comments and suggestions are more than welcome. I do not
> expect that this code is production-ready yet, and
> networking isn't my strongest suit (yet).
>
> These patches were originally posted in 2015 by Chris
> Leech. There were some issues at the time about how
> to handle namespaces going away. I hope to address
> any issues raised with this patchset and then
> to merge these changes upstream to address working
> in working in containers.
>
> My contribution thus far has been to update these patches
> to work with the current upstream kernel.
>
> Chris Leech/Lee Duncan (9):
> iscsi: create per-net iscsi netlink kernel sockets
> iscsi: associate endpoints with a host
> iscsi: sysfs filtering by network namespace
> iscsi: make all iSCSI netlink multicast namespace aware
> iscsi: set netns for iscsi_tcp hosts
> iscsi: check net namespace for all iscsi lookup
> iscsi: convert flashnode devices from bus to class
> iscsi: rename iscsi_bus_flash_* to iscsi_flash_*
> iscsi: filter flashnode sysfs by net namespace
>
> drivers/infiniband/ulp/iser/iscsi_iser.c | 7 +-
> drivers/scsi/be2iscsi/be_iscsi.c | 6 +-
> drivers/scsi/bnx2i/bnx2i_iscsi.c | 6 +-
> drivers/scsi/cxgbi/libcxgbi.c | 6 +-
> drivers/scsi/iscsi_tcp.c | 7 +
> drivers/scsi/qedi/qedi_iscsi.c | 6 +-
> drivers/scsi/qla4xxx/ql4_os.c | 64 +--
> drivers/scsi/scsi_transport_iscsi.c | 625 ++++++++++++++++-------
> include/scsi/scsi_transport_iscsi.h | 63 ++-
> 9 files changed, 537 insertions(+), 253 deletions(-)
>
next prev parent reply other threads:[~2023-02-08 19:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 17:40 [RFC 0/9] Make iscsid-kernel communications namespace-aware Lee Duncan
2023-02-08 17:40 ` [RFC PATCH 1/9] iscsi: create per-net iscsi netlink kernel sockets Lee Duncan
2023-03-14 16:21 ` Hannes Reinecke
2023-02-08 17:40 ` [RFC PATCH 2/9] iscsi: associate endpoints with a host Lee Duncan
2023-03-14 16:23 ` Hannes Reinecke
2023-03-17 21:42 ` Lee Duncan
2023-04-12 2:31 ` Chris Leech
2023-04-20 16:42 ` Chris Leech
2023-02-08 17:40 ` [RFC PATCH 3/9] iscsi: sysfs filtering by network namespace Lee Duncan
2023-03-14 16:24 ` Hannes Reinecke
2023-02-08 17:40 ` [RFC PATCH 4/9] iscsi: make all iSCSI netlink multicast namespace aware Lee Duncan
2023-03-14 16:27 ` Hannes Reinecke
2023-04-10 19:10 ` Chris Leech
2023-04-11 6:22 ` Hannes Reinecke
2023-04-10 19:10 ` [PATCH 10/11] iscsi: make session and connection lists per-net Chris Leech
2023-04-11 6:17 ` Hannes Reinecke
2023-04-10 19:10 ` [PATCH 11/11] iscsi: force destroy sesions when a network namespace exits Chris Leech
2023-04-11 6:21 ` Hannes Reinecke
2023-04-11 18:19 ` Chris Leech
2023-04-12 6:02 ` Hannes Reinecke
2023-02-08 17:40 ` [RFC PATCH 5/9] iscsi: set netns for iscsi_tcp hosts Lee Duncan
2023-03-14 16:29 ` Hannes Reinecke
2023-04-11 0:21 ` Chris Leech
2023-04-11 6:58 ` Hannes Reinecke
2023-04-11 18:03 ` Chris Leech
2023-02-08 17:40 ` [RFC PATCH 6/9] iscsi: check net namespace for all iscsi lookup Lee Duncan
2023-03-14 17:44 ` Hannes Reinecke
2023-02-08 17:40 ` [RFC PATCH 7/9] iscsi: convert flashnode devices from bus to class Lee Duncan
2023-03-14 17:45 ` Hannes Reinecke
2023-02-08 17:40 ` [RFC PATCH 8/9] iscsi: rename iscsi_bus_flash_* to iscsi_flash_* Lee Duncan
2023-03-14 17:46 ` Hannes Reinecke
2023-02-08 17:40 ` [RFC PATCH 9/9] iscsi: filter flashnode sysfs by net namespace Lee Duncan
2023-03-14 17:47 ` Hannes Reinecke
2023-02-08 19:23 ` Lee Duncan [this message]
2023-03-14 16:20 ` [RFC 0/9] Make iscsid-kernel communications namespace-aware Hannes Reinecke
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=f911472c-c4a1-27ee-8671-037f330096f0@suse.com \
--to=lduncan@suse.com \
--cc=leeman.duncan@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=open-iscsi@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).