linux-kernel - Re: [RCF PATCH] genirq/debugfs: Triggering of interrupts from userspace

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: <alpine.DEB.2.20.1708161645220.1987@nanos>
Date:   Wed, 16 Aug 2017 16:50:28 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Marc Zyngier <marc.zyngier@....com>
cc:     linux-kernel@...r.kernel.org
Subject: Re: [RCF PATCH] genirq/debugfs: Triggering of interrupts from
 userspace

On Thu, 20 Jul 2017, Marc Zyngier wrote:
> When developing new (and therefore buggy) interrupt related
> code, it can sometimes be useful to inject interrupts without
> having to rely on a device to actually generate them.
> 
> This functionnality relies on the irqchip driver to expose
> a irq_set_irqchip_state(IRQCHIP_STATE_PENDING) callback.

I like that, but can we please extend that to utilize the irq resend
mechanism:

	desc = ....;

	chip_bus_lock(desc);
        raw_spin_lock_irq(&desc->lock);

	if (has_set_state(desc))
		set_state(desc);
	else
		check_irq_resend(desc);

or something to that effect?

Thanks,

	tglx