From: Bernd Petrovitsch <bernd@firmix.at>
To: "Paweł Sikora" <pluto@pld-linux.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, linux-kernel@vger.kernel.org
Subject: Re: [oops] lib/vsprintf.c
Date: Tue, 02 Nov 2004 19:46:16 +0100 [thread overview]
Message-ID: <1099421176.10957.3.camel@tara.firmix.at> (raw)
In-Reply-To: <200411021934.38802.pluto@pld-linux.org>
On Tue, 2004-11-02 at 19:34 +0100, Paweł Sikora wrote:
> On Tuesday 02 of November 2004 08:03, you wrote:
> > >static int km_init_module(void)
> > >{
> > > printk(KERN_DEBUG "%s init\n", 1.4);
> > > return 0;
> > >}
> >
> > You do know that %s does not mix with 1.4?
>
> Yes, I known. I did it intentionally.
"Doctor, it hurts when I do that."
"Then do not do it."
> IMHO kernel should be more resistant to accidental programmers errors.
What for? Simply fix them immediately.
> Be secure, trust no one ;)
ACK. Therefore the kernel oopses, rendering the machine useless for the
moment and forces the programmer to look for the bug.
> ... and catch bugs with http://netlab.ru.is/exception/KernelExceptions.pdf
What should happen afterwards?
Write a line to syslog which is probably ignored anyway?
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2004-11-02 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 6:19 Paweł Sikora
2004-11-02 6:27 ` Nick Piggin
2004-11-02 7:35 ` Pawel Sikora
2004-11-02 9:08 ` Bernd Petrovitsch
2004-11-02 7:03 ` Jan Engelhardt
2004-11-02 18:34 ` Paweł Sikora
2004-11-02 18:38 ` Jan Engelhardt
2004-11-02 19:06 ` Randy.Dunlap
2004-11-02 18:46 ` Bernd Petrovitsch [this message]
2004-11-02 18:59 ` Jan Engelhardt
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=1099421176.10957.3.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@pld-linux.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
all inboxes | Powered by JetHome®