kev_vendor_code_find() call causes kernel panic...
kev_vendor_code_find() call causes kernel panic...
- Subject: kev_vendor_code_find() call causes kernel panic...
- From: "Alexander Klyuev" <email@hidden>
- Date: Fri, 13 Aug 2010 17:38:20 -0400
Hi All,
I already wrote about this issue: kev_vendor_code_find() call
causes kernel panic when network stack is not entirely up
(net_str_id_lock object is still uninitialized (NULL).
Here is simplified call sequence:
--------------------------------------
kev_vendor_code_find(...)
net_str_id_find_internal(...)
lck_mtx_lock(net_str_id_lock) <= where net_str_id_lock value is NULL.
... kernel panic
-------------------------------------
However IMHO such a function MUST NEVER cause kernel crash
whenever it is called because it's possible to check whether
a pointer argument ("net_str_id_lock" in this case) is NULL before call to
lck_mtx_lock()
and return an error code not causing kernel panic. So that is definitely a
bug.
Am I missing something?
Thanks for further responses.
Best,
- Alexander.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden