From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
mingo@elte.hu, x86@kernel.org, sam@ravnborg.org,
jirislaby@gmail.com, gregkh@suse.de, davem@davemloft.net,
xyzzy@speakeasy.org, mchehab@infradead.org,
jens.axboe@oracle.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Avi Kivity <avi@redhat.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [GIT PULL -tip] fix 22 make headers_check - 200901
Date: Thu, 05 Feb 2009 07:17:41 -0800 [thread overview]
Message-ID: <498B0315.5080804@zytor.com> (raw)
In-Reply-To: <200902051530.25897.arnd@arndb.de>
Arnd Bergmann wrote:
> On Wednesday 04 February 2009, H. Peter Anvin wrote:
>> Actually, if anything we should move the *non* __KERNEL_STRICT_NAMES out
>> of <linux/types.h> into something else, or completely deep-six them. I
>> don't know of any libc which wants these anymore, and I think they're
>> just residual libc5 cruft.
>>
>> However, if we want <linux/extra_types.h> that's fine with me; but
>> <linux/types.h> really should be clean, which means doing what
>> __KERNEL_STRICT_NAMES does now.
>
> Right now, we have 15 exported headers [1] that use the non-strict
> posix types (pid_t, off_t, clock_t, ...) and a set of 106 (!)
> files [2] using non-strict integer types (u_int32_t, uint32_t, u32, ...),
> 76 of those alone in netfilter.
>
Geez. The integer types is just a pattern replacement, so those we can
just fix. The 15 exported headers that use other types may very well be
real bugs -- we have had a fair share of broken ioctl signatures due to
exactly this problem.
> Do you think we should fix up all of them before 2.6.29? I'm worried
> that we might introduce more regressions in the process.
> Also, should we leave netfilter alone, in order to reduce the changes?
> I'm also unsure whether a hack in headers_install would be better than
> changing the headers in the source tree.
I have been advocating for hacking headers_install for a while. That
takes care of the 106. The 15 *need* to be audited immediately, because
that is even likely to be actual manifest bugs.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-02-05 15:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 12:56 [GIT PULL -tip] fix 22 make headers_check - 200901 Jaswinder Singh Rajput
2009-01-24 13:43 ` Jaswinder Singh Rajput
2009-01-26 12:50 ` Ingo Molnar
2009-02-04 6:43 ` Herbert Xu
2009-02-04 8:04 ` Jaswinder Singh Rajput
2009-02-04 8:12 ` Avi Kivity
2009-02-04 8:13 ` Avi Kivity
2009-02-04 8:37 ` Jaswinder Singh Rajput
2009-02-04 11:55 ` Arnd Bergmann
2009-02-04 14:18 ` Ingo Molnar
2009-02-04 17:33 ` H. Peter Anvin
2009-02-05 14:30 ` Arnd Bergmann
2009-02-05 14:30 ` Arnd Bergmann
2009-02-05 15:17 ` H. Peter Anvin [this message]
2009-02-05 16:07 ` [PATCH] Make exported headers use strict posix types Arnd Bergmann
2009-02-05 17:54 ` H. Peter Anvin
2009-02-05 18:45 ` Arnd Bergmann
2009-02-05 18:45 ` Arnd Bergmann
2009-02-17 9:38 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498B0315.5080804@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=herbert@gondor.apana.org.au \
--cc=jaswinder@kernel.org \
--cc=jens.axboe@oracle.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=x86@kernel.org \
--cc=xyzzy@speakeasy.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.