linux-kernel - Re: Potential race in irq_chip_set

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: <alpine.LFD.2.00.1009241040420.2416@localhost6.localdomain6>
Date:	Fri, 24 Sep 2010 10:45:09 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Potential race in irq_chip_set_defaults()?

Jeremy

On Thu, 23 Sep 2010, Jeremy Fitzhardinge wrote:

>  irq_chip_set_defaults() modifies the irq_chip structure in-place when
> setting up an irq.  If that happens on multiple CPUs at once then it
> could leave the irq_chip structure in an inconsistent state.
> 
> Is there anything preventing that case from happening?  There's no
> locking, and as far as I know there's no rule forbidding concurrent
> calls to set_irq_chip()/irq_chip_set_defaults().

that's true. Never thought about that. Will have a look.

Thanks,

	tglx

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