From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: gorcunov@gmail.com, geert@linux-m68k.org, zippel@linux-m68k.org,
schwab@suse.de, linux-kernel@vger.kernel.org,
linux-m68k@vger.kernel.org
Subject: Re: [PATCH] init - fix building bug and potential buffer overflow
Date: Thu, 15 May 2008 14:45:54 -0700 [thread overview]
Message-ID: <20080515144554.7b759b3c.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0805151406030.3019@woody.linux-foundation.org>
On Thu, 15 May 2008 14:15:38 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Thu, 15 May 2008, Andrew Morton wrote:
> >
> > (yeah, I normally parenthesise sizeof too, but this provided 80-col
> > salvation)
>
> Why?
this, basically:
> init/main.c | 78 +++++++++++++++++++++++++++++++----------------------------
> 1 files changed, 41 insertions(+), 37 deletions(-)
the dont-mix-bugfixes-and-cleanups mantra.
The patch looks good to me and compiles cleanly on various architectures.
> Talking about cleanups, why the *hell* does print_fn_descriptor_symbol()
> take an "unsigned long", when every single user would want to give it a
> pointer?
Yes, we make that mistake fairly regularly (looks at timer_list.data).
We start out not being sure whether most callers will pass in a ulong
or a pointer and guess wrongly.
> Would somebody please want to move that cast into the macro (or better
> yet, make it an inline function that takes a 'void *'), and remove all the
> casts from the callers?
Would be nice.
next prev parent reply other threads:[~2008-05-15 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 15:44 [PATCH] init - fix building bug and potential buffer overflow Cyrill Gorcunov
2008-05-15 17:58 ` Andrew Morton
2008-05-15 18:05 ` Cyrill Gorcunov
2008-05-15 19:47 ` Geert Uytterhoeven
2008-05-15 20:22 ` Cyrill Gorcunov
2008-05-15 20:49 ` Andrew Morton
2008-05-15 21:15 ` Linus Torvalds
2008-05-15 21:45 ` Andrew Morton [this message]
2008-05-15 23:41 ` [PATCH] Add a void * alternative to print_fn_descriptor_symbol() Abhijit Menon-Sen
2008-05-16 1:47 ` [PATCH] init - fix building bug and potential buffer overflow Linus Torvalds
2008-05-15 22:44 ` Rene Herman
2008-05-16 3:29 ` Cyrill Gorcunov
2008-05-16 4:17 ` Cyrill Gorcunov
2008-05-16 7:00 ` Geert Uytterhoeven
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=20080515144554.7b759b3c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox