From: Dan Carpenter <dan.carpenter@oracle.com>
To: Pkshih <pkshih@realtek.com>
Cc: Colin King <colin.king@canonical.com>,
Kalle Valo <kvalo@codeaurora.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] rtw89: Fix potential dereference of the null pointer sta
Date: Wed, 3 Nov 2021 13:21:29 +0300 [thread overview]
Message-ID: <20211103102128.GL2794@kadam> (raw)
In-Reply-To: <c3de973999ea40cf967ffefe0ee56ed4@realtek.com>
On Wed, Nov 03, 2021 at 12:36:17AM +0000, Pkshih wrote:
> > > > diff --git a/drivers/net/wireless/realtek/rtw89/core.c
> > > > b/drivers/net/wireless/realtek/rtw89/core.c
> > > > index 06fb6e5b1b37..26f52a25f545 100644
> > > > --- a/drivers/net/wireless/realtek/rtw89/core.c
> > > > +++ b/drivers/net/wireless/realtek/rtw89/core.c
> > > > @@ -1534,9 +1534,14 @@ static bool rtw89_core_txq_agg_wait(struct rtw89_dev *rtwdev,
> > > > {
> > > > struct rtw89_txq *rtwtxq = (struct rtw89_txq *)txq->drv_priv;
> > > > struct ieee80211_sta *sta = txq->sta;
> > > > - struct rtw89_sta *rtwsta = (struct rtw89_sta *)sta->drv_priv;
> > >
> > > 'sta->drv_priv' is only a pointer, we don't really dereference the
> > > data right here, so I think this is safe. More, compiler can optimize
> > > this instruction that reorder it to the place just right before using.
> > > So, it seems like a false alarm.
> >
> > The warning is about "sta" not "sta->priv". It's not a false positive.
> >
> > I have heard discussions about compilers trying to work around these
> > bugs by re-ordering the code. Is that an option in GCC? It's not
> > something we should rely on, but I'm just curious if it exists in
> > released versions.
> >
>
> I say GCC does "reorder" the code, because the object codes of following
> two codes are identical with default or -Os ccflags.
Huh... That's cool. GCC doesn't re-order it for me, but I'm on GCC 8
so maybe it will work when I get to a more modern version.
regards,
dan carpenter
next prev parent reply other threads:[~2021-11-03 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 15:45 [PATCH][next] rtw89: Fix potential dereference of the null pointer sta Colin King
2021-10-18 3:35 ` Pkshih
2021-10-18 12:11 ` Kalle Valo
2021-10-19 1:11 ` Pkshih
2021-10-20 8:36 ` Kalle Valo
2021-10-21 5:46 ` Pkshih
2021-10-21 8:48 ` Kalle Valo
2021-11-02 13:14 ` Dan Carpenter
2021-11-03 0:36 ` Pkshih
2021-11-03 10:21 ` Dan Carpenter [this message]
2021-11-04 1:38 ` Pkshih
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=20211103102128.GL2794@kadam \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).