netdev - Re: [PATCH 03/11] iscsi: sysfs filtering by network namespace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3604c700-3106-dfc6-d39b-5583775be029@oracle.com>
Date: Wed, 10 May 2023 12:50:08 -0700
From: michael.christie@...cle.com
To: Chris Leech <cleech@...hat.com>, Lee Duncan <lduncan@...e.com>,
        linux-scsi@...r.kernel.org, open-iscsi@...glegroups.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH 03/11] iscsi: sysfs filtering by network namespace

On 5/6/23 4:29 PM, Chris Leech wrote:
> +#define DECLARE_TRANSPORT_CLASS_NS(cls, nm, su, rm, cfg, ns, nslookup)	\
> +struct transport_class cls = {						\
> +	.class = {							\
> +		.name = nm,						\
> +		.ns_type = ns,						\
> +		.namespace = nslookup,					\
> +	},								\
> +	.setup = su,							\
> +	.remove = rm,							\
> +	.configure = cfg,						\
> +}

I think this would be in the transport class for others to use in the future
and or you want to name it differently so it doesn't clash with the future
transport class naming. Same as other places in the patch.