linux-kernel - Re: linux-headers-5.2 and proper use of SIOCGSTAMP

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: <87wogca86l.fsf@mid.deneb.enyo.de>
Date:   Sat, 20 Jul 2019 20:10:26 +0200
From:   Florian Weimer <fw@...eb.enyo.de>
To:     Sergei Trofimovich <slyfox@...too.org>
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        libc-alpha@...rceware.org, Arnd Bergmann <arnd@...db.de>,
        "David S. Miller" <davem@...emloft.net>, mtk.manpages@...il.com,
        linux-man@...r.kernel.org
Subject: Re: linux-headers-5.2 and proper use of SIOCGSTAMP

* Sergei Trofimovich:

> Should #include <linux/sockios.h> always be included by user app?
> Or should glibc tweak it's definition of '#include <sys/socket.h>'
> to make it available on both old and new version of linux headers?

What is the reason for dropping SIOCGSTAMP from <asm/socket.h>?

If we know that, it will be much easier to decide what to do about
<sys/socket.h>.