linux-kernel - Re: [PATCH] tifm: avoid inconsistent lock state

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: <63a49ef40904110839w53cde9c6k1a261effd1338942@mail.gmail.com>
Date:	Sat, 11 Apr 2009 17:39:26 +0200
From:	Alessio Igor Bogani <abogani@...ware.it>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	oakad@...oo.com, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] tifm: avoid inconsistent lock state

Dear Sir Morton,

2009/4/11 Andrew Morton <akpm@...ux-foundation.org>:
[...]
> tifm_7xx1_isr() can legitimately use spin_lock() on that lock, because
> it's running in hard IRQ context and "knows" that tifm_7xx1_isr()
> cannot be reentered on this CPU while it is running.
[...]

Thank you for reply and explanation.

Ciao,
Alessio
--
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/