netdev - Re: [PATCH 3/3] ehea: do not dereference possible NULL port

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: <20120418.132837.1291329834032822083.davem@davemloft.net>
Date:	Wed, 18 Apr 2012 13:28:37 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	cascardo@...ux.vnet.ibm.com
Cc:	netdev@...r.kernel.org, joe@...ches.com
Subject: Re: [PATCH 3/3] ehea: do not dereference possible NULL port

From: Thadeu Lima de Souza Cascardo <cascardo@...ux.vnet.ibm.com>
Date: Wed, 18 Apr 2012 09:42:52 -0300

> However, at first, I suspected this interrupt may have come from some
> other port from ehca, for example, considering a possible firmware bug.
> After more investigation, I found out that the real problem was some
> physical ports in some odd states, that caused the IRQs before the ports
> were enabled. Note that this is not really supposed to happen.

It doesn't matter how it happens from the hardware side.

What matters is that you should not register the IRQ handler
at all until all the datastructures are properly setup.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html