netdev - Re: [PATCH rfc 0/4] Introduce a new helper for parsing ipv[4|6]:port to socket address

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <34a7fa67-2b72-aaa8-1c66-cfdd5d041124@grimberg.me>
Date:   Thu, 16 Feb 2017 20:11:27 +0200
From:   Sagi Grimberg <sagi@...mberg.me>
To:     Chuck Lever <chuck.lever@...cle.com>
Cc:     linux-nvme@...ts.infradead.org,
        List Linux RDMA Mailing <linux-rdma@...r.kernel.org>,
        target-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH rfc 0/4] Introduce a new helper for parsing ipv[4|6]:port
 to socket address


>> Yea, I wanted to get all the rpc_pton/rpc_ntop (which handle both
>> ipv4 and ipv6 with scopes) converted to use a common helper.
>
> RPC is dealing with universal addresses, which are not quite the
> same as IP presentation addresses. The port number is expressed
> as:
>
>   hi8.lo8

I noticed that, that's why there will be some processing in
sunrpc to construct a port string to a generic helper (if it chooses to
use it).

> And universal IPv6 addresses don't have a mechanism for conveying
> scope information.

I do see scope handling in rpc_pton6 code if provided...