linux-kernel - Re: MSI entry unlinked before arch_teardown_msi

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: <m1irdoo8n6.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 26 Feb 2007 15:29:17 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	David Miller <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: MSI entry unlinked before arch_teardown_msi_irq().

David Miller <davem@...emloft.net> writes:

> From: ebiederm@...ssion.com (Eric W. Biederman)
> Date: Sun, 25 Feb 2007 17:14:43 -0700
>
>> David Miller <davem@...emloft.net> writes:
>> 
>> > From: ebiederm@...ssion.com (Eric W. Biederman)
>> > Date: Sun, 25 Feb 2007 02:08:07 -0700
>> >
>> >> If that isn't the issue holler and I will look into it a little more.
>> >
>> > Talking in code is always more effective :-)
>> >
>> > This patch fixes the OOPS I was talking about:
>> 
>> Ok.  That is clearly reasonable.  Why do you need to traverse
>> the list here?  I just want to understand the requirements.
>
> The real problem turned out to be my using get_irq_data() instead
> of get_irq_msi() :-)
>
> Sorry for the noise.

No problem I helped cause the confusion...

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