From: Greg KH <gregkh@linuxfoundation.org>
To: Aviraj CJ <acj@cisco.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xe-linux-external@cisco.com
Subject: Re: [PATCH stable v4.14 1/2] net: stmmac: use correct DMA buffer size in the RX descriptor
Date: Thu, 19 Dec 2019 16:41:43 +0100 [thread overview]
Message-ID: <20191219154143.GA1969379@kroah.com> (raw)
In-Reply-To: <20191218131720.12270-1-acj@cisco.com>
On Wed, Dec 18, 2019 at 05:17:19AM -0800, Aviraj CJ wrote:
> upstream 583e6361414903c5206258a30e5bd88cb03c0254 commit
>
> We always program the maximum DMA buffer size into the receive descriptor,
> although the allocated size may be less. E.g. with the default MTU size
> we allocate only 1536 bytes. If somebody sends us a bigger frame, then
> memory may get corrupted.
>
> Program DMA using exact buffer sizes.
>
> Signed-off-by: Aaro Koskinen <aaro.koskinen@nokia.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> [acj: backport v4.14 -stable
> - adjust context
> - skipped the section modifying non-existent functions in dwxgmac2_descs.c and
> hwif.h ]
> Signed-off-by: Aviraj CJ <acj@cisco.com>
Thanks for all of the backports, all now queued up.
greg k-h
prev parent reply other threads:[~2019-12-19 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 13:17 [PATCH stable v4.14 1/2] net: stmmac: use correct DMA buffer size in the RX descriptor Aviraj CJ
2019-12-18 13:17 ` [PATCH stable v4.14 2/2] net: stmmac: don't stop NAPI processing when dropping a packet Aviraj CJ
2019-12-19 15:41 ` Greg KH [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=20191219154143.GA1969379@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acj@cisco.com \
--cc=alexandre.torgue@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=xe-linux-external@cisco.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