Re: [PATCH 1/2] wimax: i2400m - prevent a possible kernel bug due to missing... | netdev

[PATCH 1/2] wimax: i2400m - prevent a possible kernel bug due to missing fw_name string · Phil Sutter <hidden> · 2012-03-26
[PATCH 2/2] wimax: i2400m-usb - use a private struct ethtool_ops · Phil Sutter <hidden> · 2012-03-26
Re: [PATCH 2/2] wimax: i2400m-usb - use a private struct ethtool_ops · David Miller <davem@davemloft.net> · 2012-03-28
Re: [PATCH 1/2] wimax: i2400m - prevent a possible kernel bug due to missing fw_name string · Ben Hutchings <hidden> · 2012-03-26
[PATCHv2 1/2] wimax: i2400m - prevent a possible kernel bug due to missing fw_name string · Phil Sutter <hidden> · 2012-03-26
[PATCHv2 2/2] wimax: i2400m-usb - use a private struct ethtool_ops · Phil Sutter <hidden> · 2012-03-26
Re: [PATCH 1/2] wimax: i2400m - prevent a possible kernel bug due to missing fw_name string · David Miller <davem@davemloft.net> · 2012-03-28

Re: [PATCH 1/2] wimax: i2400m - prevent a possible kernel bug due to missing fw_name string

From: David Miller <davem@davemloft.net>
Date: 2012-03-28 02:30:32

From: Phil Sutter <redacted>
Date: Mon, 26 Mar 2012 13:23:55 +0200

This happened on a machine with a custom hotplug script calling nameif,
probably due to slow firmware loading. At the time nameif uses ethtool
to gather interface information, i2400m->fw_name is zero and so a null
pointer dereference occurs from within i2400m_get_drvinfo().

Signed-off-by: Phil Sutter <redacted>

Applied.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help