linux-kernel - Re: tipc_config.h requires linux/string.h, which does not exist in exported headers

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: <20071030.150537.240140474.davem@davemloft.net>
Date:	Tue, 30 Oct 2007 15:05:37 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sam@...nborg.org
Cc:	raa.lkml@...il.com, linux-kernel@...r.kernel.org,
	per.liden@...csson.com, allan.stephens@...driver.com
Subject: Re: tipc_config.h requires linux/string.h, which does not exist in
 exported headers

From: David Miller <davem@...emloft.net>
Date: Tue, 30 Oct 2007 14:59:26 -0700 (PDT)

> I think the thing to do is just __KERNEL__ protect the
> <linux/string.h> include and require userspace to
> include <string.h> itself when using these headers.
> 
> That's what I'm testing right now.
> 
> I'm pretty sure those inlines are indeed used by userspace.

Actually, I'm tempted to put <string.h> in the ifndef __KERNEL__
block of that header.

That's ugly.

An alternative is to add linux/string.h to unifdef-y and have it
include <string.h> when !__KERNEL__ in order to handle cases like
this.

Sam, what do you think of that idea?
-
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/