public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Linux: Implement opensock using Netlink sockets
Date: Mon, 18 Jun 2018 16:47:00 -0000	[thread overview]
Message-ID: <1529340418.2289.267.camel@codethink.co.uk> (raw)
In-Reply-To: <20180618105015.5E8B340292859@oldenburg.str.redhat.com>

On Mon, 2018-06-18 at 12:50 +0200, Florian Weimer wrote:
> inet/tst-inet6_scopeid_pton uses __opensock indirectly, to call ioctl
> with SIOCGIFINDEX, and it still works after this change.
> 
> 2018-06-18  Florian Weimer  <fweimer@redhat.com>
> 
> 	* sysdeps/unix/sysv/linux/opensock.c (__opensock): Unconditionally
> 	return a Netlink socket.
> 	* sysdeps/unix/sysv/linux/s390/opensock.c: Remove file.
[...]

I agree that we can assume the kernel implements AF_NETLINK, but the
available socket address families might be restricted by a security
policy (e.g. systemd's RestrictAddressFamilies property).  I'm not sure
whether it's safe to assume that they will always allow AF_NETLINK.

Ben.

-- 
Ben Hutchings, Software Developer                         Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom

  parent reply	other threads:[~2018-06-18 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 10:50 Florian Weimer
2018-06-18 13:57 ` Adhemerval Zanella
2018-06-18 14:25   ` Florian Weimer
2018-06-18 17:09     ` Adhemerval Zanella
2018-06-18 17:11       ` Florian Weimer
2018-06-18 17:17         ` Adhemerval Zanella
2018-06-18 17:28           ` Florian Weimer
2018-06-18 16:47 ` Ben Hutchings [this message]
2018-06-18 17:13   ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1529340418.2289.267.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).