public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
	Roland Dreier <roland@purestorage.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 08/13] iscsi-target: Add CHAP Authentication support	using libcrypto
Date: Mon, 25 Jul 2011 12:31:18 -0700	[thread overview]
Message-ID: <4E2DC486.8080701@redhat.com> (raw)
In-Reply-To: <1311482486.31450.408.camel@haakon2.linux-iscsi.org>

On 07/23/2011 09:41 PM, Nicholas A. Bellinger wrote:
> While I apperciate Mike's input here, I'll leave the final word to Andy
> and Christoph who have been primarly driving iscsi-target v4.1
> development and are the guys who have their fingers deepest in the code.

I appreciate that, but hch and I have been working on cleaning up the
main datapath; I personally haven't needed to familiarize myself with
the auth code at all so far. That said, I happen to think you are
correct, and am in favor of accepting the code as is, with in-kernel
auth. I wasn't 100% sure from reading Mike's response but it sounded
like he was saying he'd be ok with in-kernel auth since it would make
handling hw iscsi targets easier.

(BTW I think the arguments about backwards compatibility with existing
rtslib or pre-kernel-acceptance versions are not persuasive and a
distraction from the real technical discussion. Linux has a very strong
stable-user-api tenet, but we should commit to support stable APIs that
are reviewed and accepted in the kernel, and not be limited by
compatibility with prior out-of-kernel versions.)

> But all that said, there is still one person who has the real final word
> here, and he's made it clear how he feels about this type of kernel/user
> split.

Well that's great and all - I would just emphasize we're all going to be
working on this code cooperatively for a long time to come. More time
spent discussing technical issues to where we can all reach a grumbling
consensus will ultimately bear more fruit than appeals to the Hierarchy.

Regards -- Andy

  parent reply	other threads:[~2011-07-25 19:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23  8:45 [PATCH 00/13] iscsi-target: Merge candidate for v3.1-rc1 Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 01/13] iscsi: Resolve iscsi_proto.h naming conflicts with drivers/target/iscsi Nicholas A. Bellinger
2011-07-23 13:34   ` Jesper Juhl
2011-07-23 21:23     ` Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 02/13] iscsi: Add Serial Number Arithmetic LT and GT into iscsi_proto.h Nicholas A. Bellinger
2011-07-23 14:25   ` Jesper Juhl
2011-07-23 21:29     ` Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 03/13] iscsi-target: Add iSCSI fabric support for target v4.1 Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 04/13] iscsi-target: Add target core v4.1 compatible ConfigFS control plane Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 05/13] iscsi-target: Add ConfigFS fabric dependent statistics Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 06/13] iscsi-target: Add TPG and device backend logic Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 07/13] iscsi-target: Add iSCSI Login Negotiation + Parameter logic Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 08/13] iscsi-target: Add CHAP Authentication support using libcrypto Nicholas A. Bellinger
2011-07-23 16:39   ` James Bottomley
2011-07-23 17:51     ` Linus Torvalds
2011-07-23 18:17       ` James Bottomley
2011-07-23 21:17         ` Nicholas A. Bellinger
2011-07-24  3:08           ` Mike Christie
2011-07-24  4:59             ` Nicholas A. Bellinger
     [not found]             ` <CAJAFBLCXQLvyLKR5ZD_foaPqU5X6VJfLQX_VAKeaWpDLLfPWnA@mail.gmail.com>
2011-07-24 16:32               ` Alex Couvrard
2011-07-24  3:52           ` James Bottomley
2011-07-24  4:41             ` Nicholas A. Bellinger
2011-07-24  5:50               ` James Bottomley
2011-07-24  7:52                 ` Nicholas A. Bellinger
2011-07-25 19:31               ` Andy Grover [this message]
2011-07-25 20:42                 ` Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 09/13] iscsi-target: Add Sequence/PDU list + DataIN response logic Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 10/13] iscsi-target: Add iSCSI Error Recovery Hierarchy support Nicholas A. Bellinger
2011-07-28 11:42   ` Fubo Chen
2011-07-28 20:30     ` Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 11/13] iscsi-target: Add support for task management operations Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 12/13] iscsi-target: Add misc utility logic Nicholas A. Bellinger
2011-07-28 11:30   ` Fubo Chen
2011-07-28 20:19     ` Nicholas A. Bellinger
2011-07-23  8:45 ` [PATCH 13/13] iscsi-target: Add Makefile/Kconfig and update TCM top level 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=4E2DC486.8080701@redhat.com \
    --to=agrover@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=roland@purestorage.com \
    --cc=target-devel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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