From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] streq()
Date: Tue, 24 Sep 2002 16:04:33 +1000 [thread overview]
Message-ID: <20020924061722.688A32C0A6@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 24 Sep 2002 07:40:26 +0200." <Pine.LNX.4.44.0209240731060.8824-100000@localhost.localdomain>
In message <Pine.LNX.4.44.0209240731060.8824-100000@localhost.localdomain> you
write:
> - kmalloc(size, flags)/gfp(order, flags) argument ordering. A few months
> ago i wasted two days on such a bug - since 'size' was very small
> usually, it never showed up that the allocated buffer was short, until
> some rare load-test increased the 'size'.
>
> we should do something about these. list_add() is hard, while we could
> introduce a separate type for list heads, there are some valid uses of
> non-head list_add(). But perhaps those could be separated out.
>
> handling most of the gfp() mixups should be a bit easier, perhaps by
> detecting invalid flags in the inline section, which is optimized away at
> runtime in like 95% of the cases?
I had a gcc patch which made enum typing strict for C
(-Wstrict-enums), which was designed for the GFP_xxx case and things
like it (you make them enums). It was against 2.95.2, RSN I should
update it, and (as Tridge suggested) make it an __attribute__.
For runtime checks (which are never as good) you could change the GFP_
defined to set the high bit.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-09-24 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 4:49 Rusty Russell
2002-09-24 5:40 ` Ingo Molnar
2002-09-24 6:04 ` Rusty Russell [this message]
2002-09-24 6:24 ` David S. Miller
2002-09-24 7:28 ` Rusty Russell
2002-09-24 7:38 ` Ingo Molnar
2002-09-24 8:19 ` David S. Miller
2002-09-24 13:07 ` Denis Vlasenko
2002-09-24 17:21 ` H. Peter Anvin
2002-09-25 11:27 ` Daniel Egger
2002-09-25 11:45 ` Russell King
2002-09-25 12:38 ` Daniel Egger
2002-09-25 12:19 ` Michael Sinz
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=20020924061722.688A32C0A6@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®