use network namespace for iSCSI control interfaces
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest9 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | iscsi: create per-net iscsi netlink kernel socketsdrivers/ | +57 | 0 replies | |
| 2/9 | iscsi: associate endpoints with a hostdrivers/ drivers/ drivers/ +5 more | +13 | 0 replies | |
| 3/9 | iscsi: sysfs filtering by network namespacedrivers/ include/ | +112 | 0 replies | |
| 4/9 | iscsi: make all iSCSI netlink multicast namespace awaredrivers/ | +61 | 0 replies | |
| 5/9 | iscsi: set netns for iscsi_tcp hostsdrivers/ drivers/ include/ | +14 | 0 replies | |
| 6/9 | iscsi: check net namespace for all iscsi lookupsdrivers/ drivers/ drivers/ +5 more | +150 | 0 replies | |
| 7/9 | iscsi: convert flashnode devices from bus to classdrivers/ drivers/ include/ | +18 | 0 replies | |
| 8/9 | iscsi: rename iscsi_bus_flash_* to iscsi_flash_*drivers/ drivers/ include/ | +102 | 0 replies | |
| 9/9 | iscsi: filter flashnode sysfs by net namespacedrivers/ | +33 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/9] use network namespace for iSCSI control interfaces
This series of changes makes the iSCSI netlink and sysfs control interfaces filtered by network namespace. This is required to run iscsid in any network namespace other than the initial default one.
Currently the netlink communication will fail if iscsid is started in a non-default network namespace, as there is no kernel side socket. After fixing that, the rest of these changes are to filter visibility of the iSCSI transport objects by netns. This allows for multiple iscsid instances to be run, one per netns, each controlling it's own set of iSCSI sessions.
The iSCSI transport objects are filtered, but not the SCSI or block layer devices. So while iSCSI hosts and sessions become limited to a network namespace, any attached devices remain visible system wide.
This currently only supports iscsi_tcp running in a new namespace, as it creates a virtual host per session. Support could be added later to allow assignment of iSCSI HBAs to network namespace, much as is done for network interfaces.
Chris Leech (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 lookups
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 | 62 +-- drivers/scsi/scsi_transport_iscsi.c | 625 ++++++++++++++++++++++--------- include/scsi/scsi_transport_iscsi.h | 63 ++-- 9 files changed, 538 insertions(+), 250 deletions(-)
Signature · 8 lines
2.9.5 -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected] To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFF+G/[email protected] Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.