From: Jason Wang <jasowang@redhat.com>
To: Yongji Xie <xieyongji@bytedance.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtualization <virtualization@lists.linux-foundation.org>,
netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio-net: Add validation for used length
Date: Wed, 26 May 2021 15:52:03 +0800 [thread overview]
Message-ID: <efb7d2e0-39b0-129d-084b-122820c93138@redhat.com> (raw)
In-Reply-To: <CACycT3s1VkvG7zr7hPciBx8KhwgtNF+CM5GeSJs2tp-2VTsWRw@mail.gmail.com>
在 2021/5/25 下午4:45, Yongji Xie 写道:
> On Tue, May 25, 2021 at 2:30 PM Jason Wang <jasowang@redhat.com> wrote:
>>
>> 在 2021/5/25 下午12:58, Xie Yongji 写道:
>>> This adds validation for used length (might come
>>> from an untrusted device) to avoid data corruption
>>> or loss.
>>>
>>> Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
>>> ---
>>> drivers/net/virtio_net.c | 22 ++++++++++++++++++++++
>>> 1 file changed, 22 insertions(+)
>>>
>>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>>> index c4711e23af88..2dcdc1a3c7e8 100644
>>> --- a/drivers/net/virtio_net.c
>>> +++ b/drivers/net/virtio_net.c
>>> @@ -668,6 +668,13 @@ static struct sk_buff *receive_small(struct net_device *dev,
>>> void *orig_data;
>>> u32 act;
>>>
>>> + if (unlikely(len > GOOD_PACKET_LEN)) {
>>> + pr_debug("%s: rx error: len %u exceeds max size %lu\n",
>>> + dev->name, len, GOOD_PACKET_LEN);
>>> + dev->stats.rx_length_errors++;
>>> + goto err_xdp;
>>> + }
>>
>> Need to count vi->hdr_len here?
>>
> We did len -= vi->hdr_len before.
Right.
>
>>> +
>>> if (unlikely(hdr->hdr.gso_type))
>>> goto err_xdp;
>>>
>>> @@ -739,6 +746,14 @@ static struct sk_buff *receive_small(struct net_device *dev,
>>> }
>>> rcu_read_unlock();
>>>
>>> + if (unlikely(len > GOOD_PACKET_LEN)) {
>>> + pr_debug("%s: rx error: len %u exceeds max size %lu\n",
>>> + dev->name, len, GOOD_PACKET_LEN);
>>> + dev->stats.rx_length_errors++;
>>> + put_page(page);
>>> + return NULL;
>>> + }
>>> +
>>> skb = build_skb(buf, buflen);
>>> if (!skb) {
>>> put_page(page);
>>> @@ -822,6 +837,13 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
>>> void *data;
>>> u32 act;
>>>
>>> + if (unlikely(len > truesize)) {
>>> + pr_debug("%s: rx error: len %u exceeds truesize %lu\n",
>>> + dev->name, len, (unsigned long)ctx);
>>> + dev->stats.rx_length_errors++;
>>> + goto err_xdp;
>>> + }
>>
>> There's a similar check after the XDP, let's simply move it here?
> Do we still need that in non-XDP cases?
I meant we check once for both XDP and non-XDP if we do it before if
(xdp_prog)
>
>> And do we need similar check in receive_big()?
>>
> It seems that the check in page_to_skb() can do similar things.
Right.
Thanks
>
> Thanks,
> Yongji
>
next prev parent reply other threads:[~2021-05-26 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 4:58 Xie Yongji
2021-05-25 6:30 ` Jason Wang
2021-05-25 8:45 ` Yongji Xie
2021-05-26 7:52 ` Jason Wang [this message]
2021-05-26 12:39 ` Yongji Xie
2021-05-25 9:41 ` kernel test robot
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=efb7d2e0-39b0-129d-084b-122820c93138@redhat.com \
--to=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.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
all inboxes | Powered by JetHome®