From: Bernd Petrovitsch <bernd@firmix.at>
To: Pawel Sikora <pluto@pld-linux.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [oops] lib/vsprintf.c
Date: Tue, 02 Nov 2004 10:08:31 +0100 [thread overview]
Message-ID: <1099386510.19137.7.camel@tara.firmix.at> (raw)
In-Reply-To: <Pine.LNX.4.60.0411020826520.12803@plus.ds14.agh.edu.pl>
On Tue, 2004-11-02 at 08:35 +0100, Pawel Sikora wrote:
> On Tue, 2 Nov 2004, Nick Piggin wrote:
> > Pawe Sikora wrote:
> >> vsprintf.c- case 's':
> >> vsprintf.c- s = va_arg(args, char *);
> >> vsprintf.c- if ((unsigned long)s < PAGE_SIZE)
> >> vsprintf.c- s = "<NULL>";
> >> vsprintf.c-
> >> vsprintf.c: OOPS! => len = strnlen(s, precision);
> >
> > But it is the kernel module that's buggy. What's the problem?
>
> I think that block similar to setjmp/longjmp should be placed
> around such dangerous places to refues future oops.
How do you want to find such bugs then?
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 9:08 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 [this message]
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
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=1099386510.19137.7.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--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®