linux-kernel - Re: [PATCH] mISDN GIT: hfcpci cleanup failure on IRQ weirdness

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090602154442.GA10941@rhlx01.hs-esslingen.de>
Date:	Tue, 2 Jun 2009 17:44:42 +0200
From:	Andreas Mohr <andi@...as.de>
To:	Karsten Keil <isdn@...ux-pingi.de>
Cc:	Andreas Mohr <andi@...as.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mISDN GIT: hfcpci cleanup failure on IRQ weirdness

Hi,

On Tue, Jun 02, 2009 at 04:53:35PM +0200, Karsten Keil wrote:
> Yes from mISDN side, but I do not see what inside hisax prevent mISDN from
> getting IRQs after hisax was unloaded. And it works here on my test setup, I 
> can load mISDN without an error, after unloading hisax.

Mayyybe it's due to using kernel hisax with non-kernel (GIT) mISDN?

> > misdn_log still acts weird, though...
> >
> What does be weird here ?

See first mail.

> > BTW, could isdnlog be adapted to support mISDN relatively easily?
> > (since adding CAPI support would take longer I guess)
> 
> isdnlog (beside that the isdnlog code is ugly enough) should be not a big 
> issue, mISDN supports logging in parallel to the normal work, look at the
> tools/loghex.c  code how to create a logging socket.
> It should make things easier as with HiSax, since it will get the data as 
> binary and not as hexdump.

Of course one could get "something" out of a socket-based log sink,
but that "something" would likely be much less than the caller-resolving,
application-spawning stuff that isdnlog does - at least initially.


BTW, I'm migrating towards ISDN via KabelBW modem.

Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/