From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, thomas.schlichter@web.de
Subject: Re: Fw: Oops in register_proc_table (2.6.1-mm4)
Date: Mon, 19 Jan 2004 21:18:00 -0800 [thread overview]
Message-ID: <20040119211800.582e4c3a.davem@redhat.com> (raw)
In-Reply-To: <20040117173202.76119237.akpm@osdl.org>
On Sat, 17 Jan 2004 17:32:02 -0800
Andrew Morton <akpm@osdl.org> wrote:
> It seems that ipv6 is registering something under /proc/net/ipv6/route
> which has a bad ctl_table.procname. I don't know what it is - the ipv6
> sysctl code overpowered my attention span.
I believe the patches posted by Krishna and Yoshfuji today should
cure this. I've integrated those into my tree and will push to
Linus in a bit.
prev parent reply other threads:[~2004-01-20 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 18:47 Fw: Oops in register_proc_table (2.6.1-mm4) Andrew Morton
2004-01-16 19:23 ` Andrew Morton
2004-01-16 23:40 ` Thomas Schlichter
2004-01-17 2:21 ` Andrew Morton
2004-01-18 1:32 ` Andrew Morton
2004-01-20 5:18 ` David S. Miller [this message]
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=20040119211800.582e4c3a.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
--cc=thomas.schlichter@web.de \
/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).