More information (was Re: Event loop stall bug in hostapd-0.7.3)

Ben Greear greearb
Thu Jan 12 11:05:08 PST 2012

On 01/12/2012 10:40 AM, Bryan Phillippe wrote:
> I learned some things about this while debugging it with a non-optimized version of hostapd.  I believe that the appearance of the corrupted private data structure was due to the optimization in the debugger.  That would explain why the sendmsg() is not immediately returning with an EBADF on the monitor_sock.
> I think what's actually happening is that the sendmsg() on the monitor_sock is indeed blocking.  I guess that could be a problem in the nl80211 driver in the kernel instead of something wrong with hostapd?  I'm going to start investigating that side of it now.  If you have any advice on that, please let me know.

I think a sysrq kernel stack trace would be interesting, and should show where the
kernel is blocked.  I can see reads blocking, but it seems a bit strange that
writes should block forever...


Ben Greear <greearb at>
Candela Technologies Inc

More information about the Hostap mailing list