From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Kalle Valo <kvalo@codeaurora.org>,
kbuild-all@01.org,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
linux-wireless@vger.kernel.org
Subject: Re: [wireless-drivers-next:master 54/55] drivers/net/wireless/quantenna/qtnfmac/cfg80211.c:679:10-19: ERROR: vif is NULL but dereferenced. (fwd)
Date: Fri, 15 Jun 2018 13:03:22 +0300 [thread overview]
Message-ID: <20180615100321.5qivnu7ksfklazhs@bars> (raw)
In-Reply-To: <alpine.DEB.2.20.1806151005520.3279@hadrien>
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
parent reply other threads:[~2018-06-15 10:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.DEB.2.20.1806151005520.3279@hadrien>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180615100321.5qivnu7ksfklazhs@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=julia.lawall@lip6.fr \
--cc=kbuild-all@01.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox