From: Christoph Hellwig <hch@infradead.org>
To: Bernd Schubert <bernd-schubert@web.de>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 2.6.7: sk98lin unload oops
Date: Sun, 4 Jul 2004 23:04:46 +0100 [thread overview]
Message-ID: <20040704220446.GA9010@infradead.org> (raw)
In-Reply-To: <200407050001.46489.bernd-schubert@web.de>
On Mon, Jul 05, 2004 at 12:01:35AM +0200, Bernd Schubert wrote:
> [from your other mail]
> > the previous one) makes it work unless you change the interface name
> > manually, but as Linux explicitly allows that the interface is
> > fundamentally broken and probably should just go away.
>
> Unfortunality we rename all interfaces using ifrename to make sure that the
> interface names won't change with different kernel versions (we have this
> problem when we switch between 2.4. and 2.6.). So it is normal that the oops
> occurs on unloading the modules?
Well, the problem is that someone smoked bad crack when designing the sk98lin
procfs interface ;-) We should probably just kill it and find a better way
to export the information if nessecary. I'll take a look at that.
> Btw, on 22th June I got another skge.c patch from Herbert Xu to fix another
> oops:
>
> http://lkml.org/lkml/2004/6/22/44
>
> This patch applies fine on top of your new versions (with 400 lines offset),
> maybe this patch should also be included into the current BK tree?
Jeff already merged that patch.
prev parent reply other threads:[~2004-07-04 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200407041342.18821.bernd-schubert@web.de>
[not found] ` <20040704151509.GA5100@infradead.org>
2004-07-04 15:23 ` 2.6.7: sk98lin unload oops Christoph Hellwig
2004-07-07 20:50 ` Denis Vlasenko
[not found] ` <200407042028.59047.bernd-schubert@web.de>
2004-07-04 18:44 ` Christoph Hellwig
2004-07-04 22:01 ` Bernd Schubert
2004-07-04 22:04 ` Christoph Hellwig [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=20040704220446.GA9010@infradead.org \
--to=hch@infradead.org \
--cc=bernd-schubert@web.de \
--cc=linux-kernel@vger.kernel.org \
--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).