From: Karsten Keil <kkeil@suse.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: oops in old isdn4linux and 2.6.2-rc3 (was in -rc2 too)
Date: Tue, 10 Feb 2004 12:45:21 +0100 [thread overview]
Message-ID: <20040210114521.GA21900@pingi3.kke.suse.de> (raw)
In-Reply-To: <1076408351.11882.101.camel@imladris.demon.co.uk>
On Tue, Feb 10, 2004 at 10:19:11AM +0000, David Woodhouse wrote:
> On Tue, 2004-02-10 at 03:51 +0100, Karsten Keil wrote:
> > Your analyse is correct, but the error is, that
> > ll_writewakeup is called with the lock.
> > Upper layers should not be called in this path.
>
> That's an evidently sensible answer, yes -- but it looks like it's
> always been like this, and fixing it really wasn't not a task I
> particularly wanted to undertake at 2am this morning... I think I might
> leave that to you :)
I don't want give you the impression of a "evidently sensible answer",
(maybe ist was also a little bit late or early ... :-)
I only want to point out that here is a deeper design flaw in this code
and it is here for a long time, but the old none spinlock code
with a big CLI (bad,bad,bad) make it working well enough. During
porting I saw this problem, but forget to mark it for fixing later.
These things (missing separation of layers) was one reason for me to
begin a new driver from scratch some time ago (mISDN).
--
Karsten Keil
SuSE Labs
ISDN development
prev parent reply other threads:[~2004-02-10 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 13:02 Todor Todorov
2004-02-02 19:51 ` Karsten Keil
2004-02-02 22:00 ` Marcel Holtmann
2004-02-03 7:48 ` Karsten Keil
2004-02-05 22:59 ` Stian Jordet
2004-02-04 7:38 ` 2.6.2-rc3 with isdn patch + devfs doesn't compile Adrian Bunk
2004-02-04 9:39 ` Karsten Keil
2004-02-09 12:13 ` oops in old isdn4linux and 2.6.2-rc3 (was in -rc2 too) David Woodhouse
2004-02-10 1:53 ` David Woodhouse
2004-02-10 2:51 ` Karsten Keil
2004-02-10 10:19 ` David Woodhouse
2004-02-10 11:45 ` Karsten Keil [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=20040210114521.GA21900@pingi3.kke.suse.de \
--to=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®