I managed to fix the iSER endpoint issue by making endpoints created
without a host valid again. Once I had iSER working, I went ahead and
made it network namespace aware as well.
Only tested with software roce (rxe) against the kernel target.
I think the net_exit code might need to do a bit
On Wed, Feb 08, 2023 at 09:40:50AM -0800, Lee Duncan wrote:
> Right now the iscsi_endpoint is only linked to a connection once that
> connection has been established. For net namespace filtering of the
> sysfs objects, associate an endpoint with the host that it was
> allocated for when it is
On Tue, Mar 14, 2023 at 05:23:26PM +0100, Hannes Reinecke wrote:
> On 2/8/23 18:40, Lee Duncan wrote:
> > From: Lee Duncan
> > @@ -230,6 +230,7 @@ iscsi_create_endpoint(int dd_size)
> > ep->id = id;
> > ep->dev.class = _endpoint_class;
> > + ep->dev.parent = >shost_gendev;
> >
On Mar 14, 2023, at 9:23 AM, Hannes Reinecke wrote:
>
> On 2/8/23 18:40, Lee Duncan wrote:
>> From: Lee Duncan
>> Right now the iscsi_endpoint is only linked to a connection once that
>> connection has been established. For net namespace filtering of the
>> sysfs objects, associate an endpoint
On 2/8/23 18:40, Lee Duncan wrote:
From: Lee Duncan
Right now the iscsi_endpoint is only linked to a connection once that
connection has been established. For net namespace filtering of the
sysfs objects, associate an endpoint with the host that it was
allocated for when it is created.
From: Lee Duncan
Right now the iscsi_endpoint is only linked to a connection once that
connection has been established. For net namespace filtering of the
sysfs objects, associate an endpoint with the host that it was
allocated for when it is created.
Signed-off-by: Chris Leech
Signed-off-by:
