[PATCH v2] nvme: consider also host_iface when checking ip options

[Daniel Wagner]

On Fri, Jul 22, 2022 at 05:55:40PM +0800, Chao Leng wrote:
> We should add the N:1 related controller management first, and then add
> the host_iface cheching. Thus it might be better.

I am not following you here. What do you mean with controller
management?

I've tested this patch against our nvmet backend. This allows additional
connections. E.g. the host has following setup:

 eth0: 192.168.154.50/24
 eth1: 192.168.154.214/24

and the target:

 br0: 192.168.19.54/24

With this change we can do this here:

nvme connect -t tcp -n nvmet-test -a 192.168.19.54 -s 4420 -f eth0
nvme connect -t tcp -n nvmet-test -a 192.168.19.54 -s 4420 -f eth1

What's wrong with it?