linux-kernel - [PATCH 0/1] rtnetlink/netdevice include triggers userspace compiler errors

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

Message-Id: <1289836919-19153-1-git-send-email-apw@canonical.com>
Date:	Mon, 15 Nov 2010 16:01:58 +0000
From:	Andy Whitcroft <apw@...onical.com>
To:	"David S. Miller\"" <davem@...emloft.net>,
	Eric Dumazet <eric.dumazet@...il.com>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andy Whitcroft <apw@...onical.com>,
	Tim Gardner <tim.gardner@...onical.com>
Subject: [PATCH 0/1] rtnetlink/netdevice include triggers userspace compiler errors

We have seen a number of reports of userspace applications (including
eglibc) which fail to compile when trying to use linux/rtnetlink.h.
It appears that a new helper function has necessitated the inclusion of
linux/netdevice.h which in turn causes a collision with userspace headers
from libc, with net/if.h.

It appears that this header is not required for the userspace exported
components of rtnetlink.h.  Following this email is a patch to pull this
include down in the the kernel specific section of this header.  It seems
to both fix this issue for userspace and still compiles correctly for
kernel use.

Against v2.6.37-rc1.

-apw

Andy Whitcroft (1):
  net: rtnetlink.h -- only include linux/netdevice.h when used by the
    kernel

 include/linux/rtnetlink.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/