From: "lorenzo@kernel.org" <lorenzo@kernel.org>
To: "Deren Wu (武德仁)" <Deren.Wu@mediatek.com>
Cc: "Evelyn Tsai (蔡珊鈺)" <Evelyn.Tsai@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Leon Yen (顏良儒)" <Leon.Yen@mediatek.com>,
"Shayne Chen (陳軒丞)" <Shayne.Chen@mediatek.com>,
"nbd@nbd.name" <nbd@nbd.name>,
"Stella Chang (張曉佩)" <Stella.Chang@mediatek.com>,
"Sean Wang" <Sean.Wang@mediatek.com>,
"KM Lin (林昆民)" <km.lin@mediatek.com>,
"Soul Huang (黃至昶)" <Soul.Huang@mediatek.com>,
"YN Chen (陳彥寧)" <YN.Chen@mediatek.com>,
"Posh Sun (孫瑞廷)" <posh.sun@mediatek.com>,
"Eric-SY Chang (張書源)" <Eric-SY.Chang@mediatek.com>,
"CH Yeh (葉志豪)" <ch.yeh@mediatek.com>,
"Robin Chiu (邱國濱)" <robin.chiu@mediatek.com>,
"Ryder Lee" <Ryder.Lee@mediatek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host
Date: Wed, 30 Nov 2022 18:09:29 +0100 [thread overview]
Message-ID: <Y4eOSUzLAW8x802i@lore-desk> (raw)
In-Reply-To: <5b41c02ace6538122ebd656db5bec748fcd6e14e.camel@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]
> Hi Lore,
>
> On Wed, 2022-11-30 at 15:46 +0100, Lorenzo Bianconi wrote:
> > > SDIO may need addtional 512 bytes to align bus operation. If the
> > > tailroom
> > > of this skb is not big enough, we would access invalid memory
> > > region.
> > > For low level operation, take xmit_buf instead of skb to keep valid
> > > memory
> > > access in SDIO.
> > > Note: xmit_buf is big enough for single skb size
> > >
> > > Fixes: 764dee47e2c1 ("mt76: sdio: move common code in mt76_sdio
> > > module")
> > > Tested-by: YN Chen <YN.Chen@mediatek.com>
> > > Signed-off-by: Deren Wu <deren.wu@mediatek.com>
> > > ---
> > > drivers/net/wireless/mediatek/mt76/sdio_txrx.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/net/wireless/mediatek/mt76/sdio_txrx.c
> > > b/drivers/net/wireless/mediatek/mt76/sdio_txrx.c
> > > index bfc4de50a4d2..ebea5c4e8da5 100644
> > > --- a/drivers/net/wireless/mediatek/mt76/sdio_txrx.c
> > > +++ b/drivers/net/wireless/mediatek/mt76/sdio_txrx.c
> > > @@ -254,7 +254,8 @@ static int mt76s_tx_run_queue(struct mt76_dev
> > > *dev, struct mt76_queue *q)
> > >
> > > if (!test_bit(MT76_STATE_MCU_RUNNING, &dev->phy.state))
> > > {
> > > __skb_put_zero(e->skb, 4);
> > > - err = __mt76s_xmit_queue(dev, e->skb->data,
> > > + memcpy(sdio->xmit_buf, e->skb->data, e->skb-
> > > >len);
> >
> > (even if it is not critical for performance) iirc the skb from the
> > mcu is
> > always linear, I guess we can use __skb_grow() instead. What do you
> > think?
> >
> > Regards,
> > Lorenzo
> >
>
> _skb_grow() looks good for me. It's a balance solution for this case.
> If you have no concern about the patch below, I will post v2 after UT.
> :)
>
> if (!test_bit(MT76_STATE_MCU_RUNNING, &dev->phy.state)) {
> __skb_put_zero(e->skb, 4);
> + err = __skb_grow(e->skb, roundup(e->skb->len,
> + sdio->func-
> >cur_blksize));
can we merge __skb_put_zero() and __skb_grow()? Does sdio chip require the 4
last bytes to be 0?
Regards,
Lorenzo
> + if (err)
> + return err;
> err = __mt76s_xmit_queue(dev, e->skb->data,
> e->skb->len);
>
>
> Regards,
> Deren
>
> > > + err = __mt76s_xmit_queue(dev, sdio->xmit_buf,
> > > e->skb->len);
> > > if (err)
> > > return err;
> > > --
> > > 2.18.0
> > >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-30 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 13:33 [PATCH] wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host Deren Wu
2022-11-30 14:46 ` Lorenzo Bianconi
2022-11-30 15:44 ` Deren Wu (武德仁)
2022-11-30 17:09 ` lorenzo [this message]
2022-12-01 2:02 ` Deren Wu (武德仁)
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=Y4eOSUzLAW8x802i@lore-desk \
--to=lorenzo@kernel.org \
--cc=Deren.Wu@mediatek.com \
--cc=Eric-SY.Chang@mediatek.com \
--cc=Evelyn.Tsai@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Ryder.Lee@mediatek.com \
--cc=Sean.Wang@mediatek.com \
--cc=Shayne.Chen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=YN.Chen@mediatek.com \
--cc=ch.yeh@mediatek.com \
--cc=km.lin@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=posh.sun@mediatek.com \
--cc=robin.chiu@mediatek.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).