[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46a53498-6c20-48fd-b090-02163baefddd@web.de>
Date: Mon, 24 Mar 2025 08:33:39 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Dan Carpenter <dan.carpenter@...aro.org>, Qasim Ijaz
<qasdev00@...il.com>, linux-wireless@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org
Cc: LKML <linux-kernel@...r.kernel.org>,
Angelo Gioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Bo Jiao <bo.jiao@...iatek.com>, Felix Fietkau <nbd@....name>,
James Dutton <james.dutton@...il.com>,
Johannes Berg <johannes@...solutions.net>,
Jonas Gorski <jonas.gorski@...il.com>, Lorenzo Bianconi
<lorenzo@...nel.org>, Matthias Brugger <matthias.bgg@...il.com>,
Peter Chiu <chui-hao.chiu@...iatek.com>, Ryder Lee <ryder.lee@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>, Shayne Chen <shayne.chen@...iatek.com>
Subject: Re: wifi: mt76: mt7996: avoid potential null deref in
mt7996_get_et_stats()
> Also the "phy" point will never be NULL so the check should be removed.
How many tools can help to determine such a software aspect with inter-procedural analyses?
Regards,
Markus
Powered by blists - more mailing lists