From: Andrew Morton <akpm@osdl.org>
To: Davi Arnaut <davi.lkml@gmail.com>
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org,
manfred@colorfullife.com
Subject: Re: kernel BUG at mm/slab.c:1488! (2.6.13.2)
Date: Fri, 28 Oct 2005 03:55:37 -0700 [thread overview]
Message-ID: <20051028035537.1e5e1d2c.akpm@osdl.org> (raw)
In-Reply-To: <750c918d0510280336g67344787r66a9aba4753e22cb@mail.gmail.com>
Davi Arnaut <davi.lkml@gmail.com> wrote:
>
> How about really fixing kmem_cache_* to use the proper return conventions ?
> In this case it should have returned ERR_PTR(-EEXIST);
A NULL return on failure is fine - what would we do with the additional
info anyway? Not anything which justifies updating the >200 callsites, I
suspect.
next prev parent reply other threads:[~2005-10-28 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 3:32 kernel BUG at mm/slab.c:1488! (2.6.13.2) Davi Arnaut
2005-10-28 4:53 ` Andrew Morton
2005-10-28 10:36 ` Davi Arnaut
2005-10-28 10:55 ` Andrew Morton [this message]
2005-10-29 11:37 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2005-10-27 20:55 Ben Greear
2005-10-27 21:37 ` Nate Diller
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=20051028035537.1e5e1d2c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davi.lkml@gmail.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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