linux-kernel - Re: [GIT PULL-v2] iscsi-target merge for v3.1-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]

Date:	Sat, 30 Jul 2011 11:30:30 +0200
From:	Bart Van Assche <bvanassche@....org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	James Bottomley <James.Bottomley@...senpartnership.com>
Cc:	linux-scsi <linux-scsi@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL-v2] iscsi-target merge for v3.1-rc1

On Wed, Jul 27, 2011 at 4:13 AM, Nicholas A. Bellinger
<nab@...ux-iscsi.org> wrote:
> Here is an updated pull request for an initial v3.1-rc1 merge of
> iscsi_target including the updates to address some recent build breakage
> with iscsi_proto.h in linux-next, and minor build warnings on 32-bit.

Hi Linus, Andrew and James,

There is a tradition in the Linux kernel community of only accepting
kernel code upstream after all major outstanding issues have been
resolved. Something that I consider as a major outstanding issue and
that does not only affect the iSCSI target code but also the target
core is that support for hot-pluggable HCAs is missing. This is
something I have reported more than once in the past -- see e.g.
http://www.spinics.net/lists/linux-scsi/msg50248.html. As far as I
know nobody is working on this. So I'm wondering whether that has
perhaps been overlooked when the iSCSI target code was pulled ?

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