linux-kernel - Fwd: show_interrupts() after free

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

Message-ID: <51BACCCC.2000107@huawei.com>
Date:	Fri, 14 Jun 2013 09:57:00 +0200
From:	Mario Smarduch <mario.smarduch@...wei.com>
To:	<linux-kernel@...r.kernel.org>
Subject: Fwd: show_interrupts() after free_irq issue 3.10-rc4?

I've been working with device passthrough & irq
on armv7 after disassociating the device from guest
free_irq() is executed on host. Display of /proc/interrupts
still shows the IRQ info with no irq name associated,
and there is no irq_action associated with the IRQ.
'show_interrupts()' in 'kernel/irq/proc.c' displays
info on the IRQ due to prior stats accumulated.
Few other arch specific ones only on irq_action.

Is there some specific reason for that? To me it
appears misleading to display dormant IRQ info. 
For the end user - use case like above or unloading
driver and seeing the irq show up is confusing as well.
Also not sure what you gain by displaying old IRQ info.

Please cc on responses.

<Sorry for the double copy misspelled mailing list>

- Mario

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