From: Johannes Berg <johannes@sipsolutions.net>
To: 冯嘉仪 <23210240148@m.fudan.edu.cn>
Cc: davem <davem@davemloft.net>, edumazet <edumazet@google.com>,
kuba <kuba@kernel.org>, pabeni <pabeni@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Potential Null Pointer Dereference in ieee80211_process_neg_ttlm_req Function
Date: Mon, 16 Feb 2026 10:53:43 +0100 [thread overview]
Message-ID: <e7365fadbb7c30690b8be0e6c1fed5ab00eaa9b6.camel@sipsolutions.net> (raw)
In-Reply-To: <tencent_50235033396E84610251D7C1@qq.com>
Hi,
> Our team recently developed a null-pointer-dereference (NPD) vulnerability detection tool
OK, so you decided to write a new tool. Good for you, but keep in mind
that you need to compete with very well-known tools already.
> After manual review,
(and you have:)
> BUILD_BUG_ON(ARRAY_SIZE(direction) != ARRAY_SIZE(elems->ttlm));
So you're either lying, or decided to task someone with this who doesn't
understand C; even state-of-the art LLMs would do better. State of the
art tools (LLMs and not LLMs like coverity) will also give you a
scenario of how the purported bug can actually happen.
I get that you need human feedback to improve your system, but you've
also apparently decided that it's too expensive / too much work / too
hard to really do this review, and you want the Linux community to do it
for you instead. That's cheaper, yay!
But it doesn't work that way. You're not entitled to free feedback for
your under development tool.
Please stop doing this.
johannes
prev parent reply other threads:[~2026-02-16 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 13:02 [BUG] Potential Null Pointer Dereference in ieee80211_process_neg_ttlm_req Function 冯嘉仪
2026-02-16 9:53 ` Johannes Berg [this message]
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=e7365fadbb7c30690b8be0e6c1fed5ab00eaa9b6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=23210240148@m.fudan.edu.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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