linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: James.Bottomley@suse.de, linux-scsi@vger.kernel.org, hch@lst.de,
	michaelc@cs.wisc.edu, hare@suse.de, bharrosh@panasas.com
Subject: Re: [PATCH-v2 00/14] iscsi-target: iSCSI target v4.1.0-rc1 series initial merge
Date: Mon, 28 Mar 2011 01:30:03 -0700	[thread overview]
Message-ID: <1301301003.23175.122.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20110327185119V.fujita.tomonori@lab.ntt.co.jp>

On Sun, 2011-03-27 at 19:02 +0900, FUJITA Tomonori wrote:
> On Fri, 25 Mar 2011 14:14:50 -0700
> "Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:
> 
> > What I am saying is that only the optional to implement iSCSI
> > authentication *payloads* should have a request/response interface with
> > userspace daemons for those types of auth libs that we always expect to
> 
> We don't need such interface (authentication *payloads* between kernel
> and user spaces). All operations (including authentication) before
> establishing a nexus should be done in userspace.
> --

No, the interface I speak of is most definately not specific to iSCSI
authentication payloads.

What I meant here is that iscsi-target should be sending RFC-3720
optional authentication type specific key=value payloads into userspace
daemon(s) using some form of acceptable mainline kernel <-> user
interface in mainline kernel code.

This interface also really needs to be 64-bit kernel / 32-bit user safe
as well.

--nab




  reply	other threads:[~2011-03-28  8:37 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  3:06 [PATCH-v2 00/14] iscsi-target: iSCSI target v4.1.0-rc1 series initial merge Nicholas A. Bellinger
2011-03-23  3:06 ` Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 01/14] iscsi: Resolve iscsi_proto.h naming conflicts with drivers/target/iscsi Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 02/14] iscsi: Add Serial Number Arithmetic LT and GT into iscsi_proto.h Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 03/14] target: Convert REPORT_LUNs to use int_to_scsilun Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 04/14] iscsi-target: Add iSCSI fabric support for target v4 Nicholas A. Bellinger
2011-04-07  7:34   ` Mike Christie
2011-05-09 16:22     ` Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 05/14] iscsi-target: Add TCM v4 compatiable ConfigFS control plane Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 06/14] iscsi-target: Add configfs fabric dependent statistics Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 07/14] iscsi-target: Add TPG and Device logic Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 08/14] iscsi-target: Add iSCSI Login Negotiation and Parameter logic Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 09/14] iscsi-target: Add CHAP Authentication support using libcrypto Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 10/14] iscsi-target: Add Sequence/PDU list + DataIN response logic Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 11/14] iscsi-target: Add iSCSI Error Recovery Hierarchy support Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 12/14] iscsi-target: Add support for task management operations Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 13/14] iscsi-target: Add misc utility and debug logic Nicholas A. Bellinger
2011-03-23  3:06 ` [PATCH-v2 14/14] iscsi-target: Add Makefile/Kconfig and update TCM top level Nicholas A. Bellinger
2011-03-23  8:54 ` [PATCH-v2 00/14] iscsi-target: iSCSI target v4.1.0-rc1 series initial merge FUJITA Tomonori
2011-03-23 10:22   ` Nicholas A. Bellinger
2011-03-23 11:07     ` FUJITA Tomonori
2011-03-23 21:37       ` Nicholas A. Bellinger
2011-03-23 22:46         ` FUJITA Tomonori
2011-03-23 23:28           ` Nicholas A. Bellinger
2011-03-24  1:29             ` FUJITA Tomonori
2011-03-24  6:59               ` Nicholas A. Bellinger
2011-03-25  0:18                 ` James Bottomley
2011-03-25 11:31                   ` Bart Van Assche
2011-03-25 15:06                     ` James Bottomley
2011-03-25 18:44                       ` Bart Van Assche
2011-03-25 19:34                         ` James Bottomley
2011-03-25 19:49                           ` Bart Van Assche
2011-03-25 19:54                             ` James Bottomley
2011-03-25 20:05                               ` Bart Van Assche
2011-03-25 21:14                   ` Nicholas A. Bellinger
2011-03-27 10:02                     ` FUJITA Tomonori
2011-03-28  8:30                       ` Nicholas A. Bellinger [this message]
2011-03-28  8:33                         ` FUJITA Tomonori
2011-03-27 10:02                 ` FUJITA Tomonori
2011-03-28  8:53                   ` Nicholas A. Bellinger

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=1301301003.23175.122.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=bharrosh@panasas.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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).