linux-kernel - Re: [-mm patch] make types.h usable for non-gcc C parsers

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: <8bd0f97a0708281042w6d7e57abm179337b01c254afb@mail.gmail.com>
Date:	Tue, 28 Aug 2007 13:42:32 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	"Adrian Bunk" <bunk@...sta.de>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Adrian Bunk" <bunk@...nel.org>,
	"Gabriel C" <nix.or.die@...glemail.com>,
	linux-kernel@...r.kernel.org, "Olaf Hering" <olh@...e.de>,
	netdev@...r.kernel.org
Subject: Re: [-mm patch] make types.h usable for non-gcc C parsers

On 8/28/07, Sam Ravnborg <sam@...nborg.org> wrote:
> > > But I'd like a better description, please.  Which "non-gcc parser" are we
> > > talking about here?  Something under ./scripts/.  Well, please identify it,
> > > and describe what the problem is, and how the proposed patch will address
> > > it.
> > >...
> >
> > It's about parsers like the Sun C compiler and the C parser shipped
> > with genksyms.
>
> So it is about two bugs.
> 1) kbuild (genksyms) fails to generate CRC for some symbols
> 2) allow userspace to parse the header
>
> As for 2 we already use sed to remove a lot of stuff in our headers
> so why do we use another approach here?

the sed removes things permanently and is designed for scrubbing
things that are kernel-only ... in this case, these typedefs are not
kernel only, but exposed conditionally when the compiler/standard
allows for it
-mike
-
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/