linux-kernel - Re: [RFC v2 05/21] tcm: Add ConfigFS subsystem backstore infrastructure

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: <20101006155833G.fujita.tomonori@lab.ntt.co.jp>
Date:	Wed, 6 Oct 2010 16:09:26 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	nab@...ux-iscsi.org
Cc:	fujita.tomonori@....ntt.co.jp, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org, michaelc@...wisc.edu, hch@....de,
	hare@...e.de, James.Bottomley@...e.de, axboe@...nel.dk,
	bharrosh@...asas.com
Subject: Re: [RFC v2 05/21] tcm: Add ConfigFS subsystem backstore
	infrastructure

On Tue, 05 Oct 2010 21:30:42 -0700
"Nicholas A. Bellinger" <nab@...ux-iscsi.org> wrote:

> I have been thinking about something similar that is needed for the WIP
> TCM HW target mode drivers when a:
> 
> 	mkdir -p /sys/kernel/config/target/$TCM_MOD/$LPORT_WWPN/tpgt_1
> 
> happens the WWPN is coming from HW.  This currently looks like something
> along the lines of the following for tcm_lpfc:
> 
> http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.git;a=blob;f=drivers/target/tcm_lpfc/tcm_lpfc_configfs.c;hb=tcm_lpfc#l227

The above link doesn't work for me so I'm not sure.

But I guess that you are talking about the problem that
tcm_lpfc_make_lport() can accept proper hardware port addresses. We
are on the same page if so.


> The main issue here is that the user still needs to know the $LPORT_WWPN
> before hand (either from looking at a sticker on the card, or via
> another method) in order to preform the initial TFO->fabric_make_wwn()
> -> $TCM_MOD_make_wwn() operation.  So what we need is a configfs attrib
> at the top level TCM fabric group in order to see a list of the
> available hardware ports from the specific $TCM_MOD.  What I was
> thinking for TCM HW fabric module ports would be to have something like:
> 
> 	/sys/kernel/config/target/$TCM_MOD/hw_ports
> 
> that would walk the struct pci_dev looking for fabric module specific HW
> target mode capabilities.  I assume this is what you had in mind for
> drivers/scsi/ibmvscsi as well, yes..?

Doesn't sound so.

I want the driver to create necessary target directories in
/sys/kernel/config/target/ibmvscsit/ automatically.


And 'hw_ports' looks unnecessary because fc drivers already provide
such information under /sys/class/, I think.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/