From: Michael Buesch <mb@bu3sch.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: i4ldeveloper@listserv.isdn4linux.de,
Carsten Paeth <calle@calle.de>,
Karsten Keil <isdn@linux-pingi.de>,
Karsten Keil <keil@b1-systems.de>,
Armin Schindler <armin@melware.de>,
isdn4linux@listserv.isdn4linux.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] isdn/capi: fix up CAPI subsystem workaround locking a bit
Date: Tue, 6 Oct 2009 23:01:22 +0200 [thread overview]
Message-ID: <200910062301.24572.mb@bu3sch.de> (raw)
In-Reply-To: <4ACB83F7.9040500@imap.cc>
On Tuesday 06 October 2009 19:52:55 Tilman Schmidt wrote:
> > Yeah, this sledgehammer lock did fix the crash while leaving the old non-list-head
> > queue in place (it should still be there today).
>
> That is not the case. In mainline, your second patch was applied on
> top of the first one, so there is now struct list_head ackqueue and
> spinlock_t ackqlock as well as static DEFINE_SPINLOCK(workaround_lock).
Ok, that's fine, too.
It's just that the ackqlock wasn't enough to fix it, as I said. It just shrinks the window.
> > I still have the device somewhere. If you want to have it, I can blow off the
> > dust and send it to you. If you don't want it, I'll throw it away soon.
> > I'd really like to send it to you to get rid of it. ;)
>
> Feel free to do so. I'll send you my snailmail address by PM. I'm
> making no promises about when I might get around to actually testing
> it, though.
Thanks, I'll get it to the post office by the end of the week.
> >> Can anyone shed some light on
> >> what that device is doing differently from other ISDN cards?
> >
> > Well, it's a combined ISDN/DSL card, but I never used the ISDN part. So the crash
> > happened while transferring data over the DSL link.
>
> DSL over CAPI? Strange.
Yeah, dunno. They did it that way... Pretty weird.
> > The vendor driver is closed source with an open wrapper (like nvidia). It's a pretty
> > crappy unmaintained piece of software, but it ran stable with some patches applied
> > to the driver and the workaround-lock patch to the capi stack.
>
> O dear. I wonder what I'll find.
ftp://ftp.avm.de/cardware/fritzcrd.dsl/linux/suse.93/fcdsl-suse93-3.11-07.tar.gz
This is the driver that I used. It needs some modification to compile on a recent kernel.
Unfortunately I don't have the patch anymore. But it was rather trivial. It renamed some functions,
because they clashed with others and did some other things I don't remember.
Remember to get a bucket before looking at the code, because you will need it. ;)
--
Greetings, Michael.
prev parent reply other threads:[~2009-10-06 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 12:06 [PATCH RFC] isdn/capi: fix up CAPI subsystem workaround locking a bit Tilman Schmidt
2009-10-03 18:26 ` Michael Buesch
2009-10-03 18:35 ` Michael Buesch
[not found] ` <200910032035.21884.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2009-10-05 11:42 ` Tilman Schmidt
2009-10-05 21:24 ` Michael Buesch
2009-10-06 17:52 ` Tilman Schmidt
2009-10-06 21:01 ` Michael Buesch [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=200910062301.24572.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=armin@melware.de \
--cc=calle@calle.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=keil@b1-systems.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tilman@imap.cc \
/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).