Re: nfsrdma broken on 2.6.34-rc1?

[Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>]

On Mon, Mar 29, 2010 at 02:51:46PM -0500, Steve Wise wrote:

>> Yeah, exactly, it is very complex and there is a real need for
>> things pretending to be IP to capture all this subtlety. The details
>> can't just be skipped over, people will notice :(
>>
>> Though, I'm also not entirely certain that NFS-RDMA is right to bind
>> to both AFs, generally speaking on Linux for a multi-protocol app you
>> only want to bind to v6 addresses.. Or is it using IPV6_V6ONLY or alike?

> This issue is really not in the NFS-RDMA code.  the nfsd code is doing  
> the binding.  See commit:
>
> 37498292aa97658a5d0a9bb84699ce8c1016bb74
> Author: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> Date:   Tue Jan 26 14:04:22 2010 -0500
>
>    NFSD: Create PF_INET6 listener in write_ports

Sure.. but it relies on the behavior of svcsock.c which does this:

        if (family == PF_INET6)
                kernel_setsockopt(sock, SOL_IPV6, IPV6_V6ONLY,
                                        (char *)&val, sizeof(val));

And the NFS-RDMA has no equivalent. Having the common code explicitly
rely on IPV6_V6ONLY is quite troublesome when you can't implement it
:)

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html