From: Daniel Phillips <phillips@innominate.de>
To: Gregory Maxwell <greg@linuxpower.cx>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at slab.c:1542!(2.4.1-pre9)
Date: Wed, 24 Jan 2001 15:32:07 +0100 [thread overview]
Message-ID: <3A6EE767.9BD35AC9@innominate.de> (raw)
In-Reply-To: <3A6C5058.C5AA7681@zaralinux.com> <3A6CB620.469A15A9@Home.net> <3A6ED16E.E8343678@innominate.de> <20010124082929.A1970@xi.linuxpower.cx>
Gregory Maxwell wrote:
>
> On Wed, Jan 24, 2001 at 01:58:22PM +0100, Daniel Phillips wrote:
> > > This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
> > > extention. This has been discussed on the Xpert XFree86 mailing list. There
> > > is a fix in the works (depends on the TrueType fonts your using).
> >
> > A BUG is a BUG:
> >
> > > > kernel BUG at slab.c:1542!
> >
> > The kernel should never oops, no matter what user space does to it.
>
> The kernel appears to run fine with this bug() removed.
I don't know much about the history of this bug but it's quite clear
it's deliberately inserted:
void * kmalloc (size_t size, int flags)
<if allocation succeeds, exit>
BUG(); // too big size
return NULL;
It says "kernel allocation will *never* fail, and if you try to kmalloc
something too large, that's a bug too" - not a reason to try again. I'd
check with Linus before solving the problem that way ;-)
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 15:23 kernel BUG at slab.c:1542! (2.4.1-pre9) Jorge Nerin
2001-01-22 22:37 ` kernel BUG at slab.c:1542!(2.4.1-pre9) Shawn Starr
2001-01-23 3:02 ` David Ford
2001-01-24 12:58 ` Daniel Phillips
2001-01-24 13:29 ` Gregory Maxwell
2001-01-24 14:32 ` Daniel Phillips [this message]
2001-01-24 15:45 ` Andrew Morton
2001-01-25 1:18 ` Alan Cox
2001-01-24 18:05 ` Tim Fletcher
2001-01-24 17:50 ` Shawn Starr
2001-01-24 18:05 ` Tim Fletcher
2001-01-25 11:49 ` Russell King
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=3A6EE767.9BD35AC9@innominate.de \
--to=phillips@innominate.de \
--cc=greg@linuxpower.cx \
--cc=linux-kernel@vger.kernel.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