On Tue, Nov 21, 2017 at 11:26:09AM +, David Laight wrote:
> From: Chris Leech
> > Sent: 15 November 2017 00:25
> > To: David Laight
> > Cc: netdev@vger.kernel.org; contain...@lists.linux-foundation.org
> > Subject: Re: [PATCH 0/9] use network namespace for iSCSI con
David Laight writes:
> To make matters even more annoying the functions for holding and
> releasing a namespace are GPL_ONLY :-(
I am going to pick on this by itself for a moment without mentioning
anything else, so as hopefully not to derail what otherwise sounds
like a good technical conversat
From: Chris Leech
> Sent: 15 November 2017 00:25
> To: David Laight
> Cc: netdev@vger.kernel.org; contain...@lists.linux-foundation.org
> Subject: Re: [PATCH 0/9] use network namespace for iSCSI control interfaces
>
> On Wed, Nov 08, 2017 at 10:31:04AM +, David Laight wrot
On Wed, Nov 08, 2017 at 10:31:04AM +, David Laight wrote:
> From: Chris Leech
> > Sent: 07 November 2017 22:45
> >
> > I've posted these changes to allow iSCSI management within a container
> > using a network namespace to the SCSI and Open-iSCSI lists, but seeing
> > as it's not really SCSI/b
From: Chris Leech
> Sent: 07 November 2017 22:45
>
> I've posted these changes to allow iSCSI management within a container
> using a network namespace to the SCSI and Open-iSCSI lists, but seeing
> as it's not really SCSI/block related I'm casting a wider net looking
> for reviews.
I didn't spot
Hello,
I've posted these changes to allow iSCSI management within a container
using a network namespace to the SCSI and Open-iSCSI lists, but seeing
as it's not really SCSI/block related I'm casting a wider net looking
for reviews.
These patches apply network namespace to the iSCSI netlink family