linux-kernel - Re: [GIT PULL] ib_srpt: Initial SRP Target merge for v3.2-rc1

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] [day] [month] [year] [list]

Message-ID: <1320610245.10690.10.camel@haakon2.linux-iscsi.org>
Date:	Sun, 06 Nov 2011 12:10:45 -0800
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Bart Van Assche <bvanassche@....org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	target-devel <target-devel@...r.kernel.org>,
	linux-rdma <linux-rdma@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Roland Dreier <roland@...estorage.com>,
	Christoph Hellwig <hch@....de>
Subject: Re: [GIT PULL] ib_srpt: Initial SRP Target merge for v3.2-rc1

On Sun, 2011-11-06 at 18:42 +0100, Bart Van Assche wrote:
> On Sun, Nov 6, 2011 at 2:20 PM, Bart Van Assche <bvanassche@....org> wrote:
> > On Sun, Nov 6, 2011 at 11:09 AM, Nicholas A. Bellinger
> > <nab@...ux-iscsi.org> wrote:
> >> We have also discussed srpt_service_guid a bit before, which you
> >> indicated needed to stay in current code as global scope, and presumably
> >> should not change value after loading.  Looking at the actual usage, one
> >> post merge improvement we can consider is seeing if it's possible to
> >> move ib_cm_listen() out of srpt_add_one() and have it driven instead by
> >> configfs context in order to optionally set srpt_service_guid on a per
> >> target endpoint basis to get us some more flexibility.
> >
> > ib_sprt defines a single I/O controller profile and hence there should
> > be exactly one GUID associated with it.
> 
> (replying to my own e-mail)
> 
> Note: I'm not sure anyone is using the srpt_service_guid kernel module
> parameter. One possible approach is to leave out that kernel module
> parameter for the initial merge. If later on anyone asks for restoring
> that functionality we can evaluate at that time what would be the best
> way to restore it.
> 

Well, when this was discussed this before we concluded (via your input)
that this should stay in place for the initial merge.

So it's a bit late to drop this now, as the PULL request has gone out to
Linus, and has been acked by Roland.  But if you think it should
removed, I'm happy to drop it in the first set of post-merge
target-pending rc-fixes.

Thanks,

--nab

--
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/