From: Eran Mann <emann@mrv.com>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: [patch 2.4] kernel oops on VLAN removal
Date: Wed, 20 Aug 2003 15:51:51 +0300 [thread overview]
Message-ID: <3F436EE7.1030104@mrv.com> (raw)
In-Reply-To: <20030819124154.75ec0383.davem@redhat.com>
David S. Miller wrote:
> On Tue, 19 Aug 2003 18:36:37 +0300
> Eran Mann <emann@mrv.com> wrote:
>
>
>>The current code attempts to add a proc entry for each vlan device,
>>however there is no check whether this attempt succeeded. When a device
>>is unregistered it tries to remove the proc entry, if none was added
>>the oops follows...
>
>
> Patch applied to my 2.4.x tree, scheduled for 2.4.23-preX
>
> Can someone check out 2.6.x?
>
It looks the same in 2.6.0-test3. The patch applies (with small offsets)
and works (the oops is much harder to trigger in 2.6.x since
PROC_NDYNAMIC is increased to 16384, I had to reduce it to 4096 to
trigger the oops).
--
Eran Mann
Senior Software Engineer
MRV International
Tel: 972-4-9936297
Fax: 972-4-9890430
www.mrv.com
next prev parent reply other threads:[~2003-08-20 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 15:36 [patch 2.4] kernel oops on VLAN removal Eran Mann
2003-08-19 19:41 ` David S. Miller
2003-08-20 12:51 ` Eran Mann [this message]
2003-08-20 18:31 ` David S. Miller
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=3F436EE7.1030104@mrv.com \
--to=emann@mrv.com \
--cc=davem@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.