From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Chris Wright <chrisw@osdl.org>
Cc: davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH 6/8] Use SLAB_PANIC when creating critical slab cache
Date: Sun, 14 Nov 2004 18:27:49 -0200 [thread overview]
Message-ID: <4197BFC5.5080800@conectiva.com.br> (raw)
In-Reply-To: <20041114122400.D2357@build.pdx.osdl.net>
Chris,
I think somebody proposed this in the past and it was refused
because we better get rid of the panics and return an error, propagate
it and refuse to load the module, better have the machine still alive
but without networking than panic it.
- Arnaldo
Chris Wright wrote:
> Use SLAB_PANIC when creating a critical slab cache.
>
> Signed-off-by: Chris Wright <chrisw@osdl.org>
>
> ===== net/ipv6/ip6_fib.c 1.33 vs edited =====
> --- 1.33/net/ipv6/ip6_fib.c 2004-11-09 22:57:03 -08:00
> +++ edited/net/ipv6/ip6_fib.c 2004-11-14 11:56:01 -08:00
> @@ -1242,10 +1242,8 @@ void __init fib6_init(void)
> {
> fib6_node_kmem = kmem_cache_create("fib6_nodes",
> sizeof(struct fib6_node),
> - 0, SLAB_HWCACHE_ALIGN,
> + 0, SLAB_HWCACHE_ALIGN|SLAB_PANIC,
> NULL, NULL);
> - if (!fib6_node_kmem)
> - panic("cannot create fib6_nodes cache");
> }
>
> void __exit fib6_gc_cleanup(void)
>
>
next prev parent reply other threads:[~2004-11-14 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 20:18 [PATCH 0/8] Use SLAB_PANIC when creating critical slab cache Chris Wright
2004-11-14 20:20 ` [PATCH 1/8] " Chris Wright
2004-11-14 20:20 ` [PATCH 2/8] " Chris Wright
2004-11-14 20:21 ` [PATCH 3/8] " Chris Wright
2004-11-14 20:22 ` [PATCH 4/8] " Chris Wright
2004-11-14 20:23 ` [PATCH 5/8] " Chris Wright
2004-11-14 20:24 ` [PATCH 6/8] " Chris Wright
2004-11-14 20:27 ` Arnaldo Carvalho de Melo [this message]
2004-11-14 22:51 ` Chris Wright
2004-11-14 23:51 ` Arnaldo Carvalho de Melo
2004-11-14 20:24 ` [PATCH 7/8] " Chris Wright
2004-11-14 20:25 ` [PATCH 8/8] " Chris Wright
2004-11-14 23:11 ` [PATCH 0/8] " Christoph Hellwig
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=4197BFC5.5080800@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=chrisw@osdl.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).