netdev - Re: [PATCH 1/3] net: introduce SO

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANq1E4R9NHQJuhwyj_gat05dPPjpzEdmth46RU8n23ozXzmhzw@mail.gmail.com>
Date:   Thu, 10 Jan 2019 17:50:29 +0100
From:   David Herrmann <dh.herrmann@...il.com>
To:     David Ahern <dsahern@...il.com>,
        Roopa Prabhu <roopa@...ulusnetworks.com>
Cc:     netdev <netdev@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Tom Gundersen <teg@...m.no>
Subject: Re: [PATCH 1/3] net: introduce SO_BINDTOIF sockopt

Hi

On Thu, Jan 10, 2019 at 5:38 PM David Ahern <dsahern@...il.com> wrote:
>
> On 1/10/19 7:25 AM, David Herrmann wrote:
> > This introduces a new generic SOL_SOCKET-level socket option called
> > SO_BINDTOIF. It behaves similar to SO_BINDTODEVICE, but takes a network
> > interface index as argument, rather than the network interface name.
>
> SO_BINDTOIF is not very descriptive related to SO_BINDTODEVICE.
>
> SO_BINDTOINDEX, SO_BINDTODEVINDEX or SO_BINDTODEVIDX would be clearer
> about this option versus SO_BINDTODEVICE.

I am open for these suggestions. I don't particularly have any
preference on the names, but I agree that BINDTOIF is not very easy to
read. For v2 I will pick SO_BINDTOIFINDEX (as suggested by Roopa),
unless there are any objections.

Thanks!
David