netdev - Re: [PATCH] devlink: fix libc and kernel headers collision

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: <20190603055841.GA2202@nanopsycho>
Date:   Mon, 3 Jun 2019 07:58:41 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Baruch Siach <baruch@...s.co.il>
Cc:     Stephen Hemminger <stephen@...workplumber.org>,
        netdev@...r.kernel.org, Aya Levin <ayal@...lanox.com>,
        Moshe Shemesh <moshe@...lanox.com>
Subject: Re: [PATCH] devlink: fix libc and kernel headers collision

Thu, May 30, 2019 at 05:32:27PM CEST, baruch@...s.co.il wrote:
>Since commit 2f1242efe9d ("devlink: Add devlink health show command") we
>use the sys/sysinfo.h header for the sysinfo(2) system call. But since
>iproute2 carries a local version of the kernel struct sysinfo, this
>causes a collision with libc that do not rely on kernel defined sysinfo
>like musl libc:
>
>In file included from devlink.c:25:0:
>.../sysroot/usr/include/sys/sysinfo.h:10:8: error: redefinition of 'struct sysinfo'
> struct sysinfo {
>        ^~~~~~~
>In file included from ../include/uapi/linux/kernel.h:5:0,
>                 from ../include/uapi/linux/netlink.h:5,
>                 from ../include/uapi/linux/genetlink.h:6,
>                 from devlink.c:21:
>../include/uapi/linux/sysinfo.h:8:8: note: originally defined here
> struct sysinfo {
>		^~~~~~~
>
>Rely on the kernel header alone to avoid kernel and userspace headers
>collision of definitions.
>
>Cc: Aya Levin <ayal@...lanox.com>
>Cc: Moshe Shemesh <moshe@...lanox.com>
>Signed-off-by: Baruch Siach <baruch@...s.co.il>

Acked-by: Jiri Pirko <jiri@...lanox.com>