linux-kernel - Re: why usr/include/linux/if

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

Message-Id: <1232463242.3088.16.camel@localhost.localdomain>
Date:	Tue, 20 Jan 2009 20:24:02 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	mike.mclagan@...ux.org
Cc:	Ingo Molnar <mingo@...e.hu>, Sam Ravnborg <sam@...nborg.org>,
	netdev@...r.kernel.org, davem@...emloft.net,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: why usr/include/linux/if_frad.h is required

CC: LKML

On Tue, 2009-01-20 at 20:23 +0530, Jaswinder Singh Rajput wrote:
> For if_frad.h I am getting two warnings with 'make headers_check':
>   usr/include/linux/if_frad.h:29: leaks CONFIG_DLCI to userspace where it is not valid
>   usr/include/linux/if_frad.h:129: leaks CONFIG_DLCI to userspace where it is not valid
> 
> Almost all if_frad.h is covered with #if defined(CONFIG_DLCI) || defined(CONFIG_DLCI_MODULE) 
> 
> If I remove this portion so only this what we get in userspace:
> 
> #ifndef _FRAD_H_
> #define _FRAD_H_
> 
> #include <linux/if.h>
> 
> #endif
> 
> So I am surprising what is the point of this ? 
> 
> Can I change its name to is_fraud ;-)
> 
> --
> JSR

--
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/