From: Tilman Schmidt <tilman@imap.cc>
To: Michael Buesch <mb@bu3sch.de>
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: Mon, 05 Oct 2009 13:42:29 +0200 [thread overview]
Message-ID: <4AC9DBA5.1090701@imap.cc> (raw)
In-Reply-To: <200910032035.21884.mb@bu3sch.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 2009-10-03 20:35:19 +0200, Michael Buesch wrote:
>> I remember that handle_minor_send() and/or handle_minor_recv() showed up
>> in the crash backtraces. So if you move them out of the critical
>> section, you can as well remove the lock completely.
>
> here's my original mail:
> http://lkml.indiana.edu/hypermail/linux/kernel/0605.0/0455.html
>
> Note the patch in that mail does _not_ fix the issue, as it turned out later.
> Then I did the workaround-lock patch, which _did_ fix it.
Thanks for the info. So do I understand correctly that after:
commit 6aa65472d18703064898eefb5eb58f7ecd0d8912
Author: Michael Buesch <mb@bu3sch.de>
Date: Mon Jun 26 00:25:30 2006 -0700
[PATCH] CAPI crash / race condition
you were actually still seeing LIST_POISON2 Oopses in
capiminor_del_ack(), but after:
commit 053b47ff249b9e0a634dae807f81465205e7c228
Author: Michael Buesch <mb@bu3sch.de>
Date: Mon Feb 12 00:53:26 2007 -0800
[PATCH] Workaround CAPI subsystem locking issue
they were gone? That's interesting. I'll try to wrap my mind around
this. capiminor_del_ack() isn't that big, after all.
It's unfortunate that these crashes only seem to occur with one specific
device (FritzCard DSL) which I don't have. Can anyone shed some light on
what that device is doing differently from other ISDN cards?
Thanks,
Tilman
- --
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKydulQ3+did9BuFsRAsYVAJ9e5azOPmNycMHZM6onfsDIY21a5wCffNh5
14WY2tYjla7wmmVgCHe+qDo=
=BgmY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-10-05 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 12:06 Tilman Schmidt
2009-10-03 18:26 ` Michael Buesch
2009-10-03 18:35 ` Michael Buesch
2009-10-05 11:42 ` Tilman Schmidt [this message]
2009-10-05 21:24 ` Michael Buesch
2009-10-06 17:52 ` Tilman Schmidt
2009-10-06 21:01 ` Michael Buesch
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=4AC9DBA5.1090701@imap.cc \
--to=tilman@imap.cc \
--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=mb@bu3sch.de \
--cc=netdev@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
Powered by JetHome