Hello Julia, > This report is a bit old, so perahsp the problem is already addressed. In > any case, the goto out on line 658 will lead to a null pointer > dereference. > > julia Thanks for the issue report ! We have already received similar issue report together with the fix for it. Fix has not yet been applied to wireless-drivers-next/master. But, according to Kalle, it will be queued for 4.18. By the way, the previous issue report was based on Coverity analysis. Could you please clarify what kind of tool was used by kbuild robot for analysis ? I couldn't figure this out from your logs. Regards, Sergey
