linux-kernel - Re: [PATCH] [ISDN] Fix random hard freeze with AVM c4 card

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] [day] [month] [year] [list]

Message-Id: <20071017142556.0fda897f.akpm@linux-foundation.org>
Date:	Wed, 17 Oct 2007 14:25:56 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Karsten Keil <kkeil@...e.de>
Cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	isdn4linux@...tserv.isdn4linux.de, stable@...nel.org
Subject: Re: [PATCH] [ISDN] Fix random hard freeze with AVM c4 card

On Wed, 17 Oct 2007 13:07:44 +0200
Karsten Keil <kkeil@...e.de> wrote:

> The patch
> - Includes the call to capilib_data_b3_req in the spinlock. This routine
>   in turn calls the offending mq_enqueue routine that triggered the
>   freeze if not locked.  This should also fix other indicators of
>   incosistent capilib_msgidqueue list, that trigger messages like:
>   Oct  5 03:05:57 BERL0 kernel: kcapi: msgid 3019 ncci 0x30301 not on queue
>   that we saw several times a day (usually several in a row).
> - Fixes all occurrences of c4_dispatch_tx to be called with active
>   spinlock, there were some instances where no lock was active. Mostly
>   these are in very infrequently called routines, so the additional
>   performance penalty is minimal.

I've tagged this patch and "[ISDN] fix random freezes with AVM B1 drivers"
as suitable for backporting into 2.6.23.x.  Please let me know if that was
not appropriate.
-
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/