linux-kernel - Re: [PATCH] block/cpqarray.c: remove IRQF

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: <20150302135657.e8a3dfa54fae3d15f658b3b5@linux-foundation.org>
Date:	Mon, 2 Mar 2015 13:56:57 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Valentin Rothberg <Valentin.Rothberg@...6.fr>
Cc:	iss_storagedev@...com, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] block/cpqarray.c: remove IRQF_DISABLED flag

On Fri, 27 Feb 2015 13:32:55 +0100 Valentin Rothberg <Valentin.Rothberg@...6.fr> wrote:

> The IRQF_DISABLED is a NOOP and scheduled to be removed.  According to
> Ingo Molnar (e58aa3d2d0cc01ad8d6f7f640a0670433f794922) running IRQ
> handlers with interrupts enabled can cause stack overflows when the
> interrupt line of the issuing device is still active.
> 

I suggest you prepare a patch which removes IRQF_DISABLED entirely. 
Several drivers still use it and it is possible that they have been
buggy for some time, so we should be careful to cc the relevant
maintainers (they probably don't exist) so they can check out what's
going on in their code.

--
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/