linux-kernel - Re: [PATCH] linux headers: include linux/types.h where appropriate

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: <20120223195026.GA30895@merkur.ravnborg.org>
Date:	Thu, 23 Feb 2012 20:50:26 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Dave Airlie <airlied@...ux.ie>
Cc:	Bobby Powers <bobbypowers@...il.com>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, davem@...emloft.net
Subject: Re: [PATCH] linux headers: include linux/types.h where appropriate

On Thu, Feb 23, 2012 at 07:28:10PM +0000, Dave Airlie wrote:
> 
> > This silences the related header check warnings.
> 
> please fix the bug in the correct place, the drm.h header includes 
> linux/types.h and this is one on purpose.
> 
> maybe expend some effort fixing the stupid tool to recurse like a normal 
> preprocessor would.

Before we fix the tool maybe we should agree on what the tool should check for.
One obvious thing to check is that we do not start to use user-land
types in our exported headers like uint32_t etc.
Another could be that no header file should depend oon the user to include other
header files.
Etc.

The checks we have implmented today are very conservative - but as you resist
to add a few includes in the drm/drm*.h files prevents us from hitting
zero warnings even with these conservative checks.

If we started to be more strict we would see much more warnings/errors.
But all this fuzz about a handfull of includes in the drm header files
sure scare me away from ever starting this.
I can only image the uproar some other changes may cause then.

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