On Mon, 28 Mar 2011 01:30:03 -0700 "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: > 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@xxxxxxxxxxxxxxx> 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. The deamon can read configfs files and build the payloads. > This interface also really needs to be 64-bit kernel / 32-bit user safe > as well. I'm sure that we (kernel developers) are good enough to handle it nicely. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
