lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07b6b325-9a15-222f-e618-d149b57cbac2@yusur.tech>
Date:   Sat, 6 May 2023 16:56:35 +0800
From:   Hao Chen <chenh@...ur.tech>
To:     Xuan Zhuo <xuanzhuo@...ux.alibaba.com>
Cc:     huangml@...ur.tech, zy@...ur.tech,
        "Michael S. Tsirkin" <mst@...hat.com>,
        Jason Wang <jasowang@...hat.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        "open list:VIRTIO CORE AND NET DRIVERS" 
        <virtualization@...ts.linux-foundation.org>,
        "open list:NETWORKING DRIVERS" <netdev@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] virtio_net: set default mtu to 1500 when 'Device maximum
 MTU' bigger than 1500



在 2023/5/6 10:50, Xuan Zhuo 写道:
> On Sat,  6 May 2023 10:15:29 +0800, Hao Chen <chenh@...ur.tech> wrote:
>> When VIRTIO_NET_F_MTU(3) Device maximum MTU reporting is supported.
>> If offered by the device, device advises driver about the value of its
>> maximum MTU. If negotiated, the driver uses mtu as the maximum
>> MTU value. But there the driver also uses it as default mtu,
>> some devices may have a maximum MTU greater than 1500, this may
>> cause some large packages to be discarded,
> 
> You mean tx packet?
Yes.
> 
> If yes, I do not think this is the problem of driver.
> 
> Maybe you should give more details about the discard.
> 
In the current code, if the maximum MTU supported by the virtio net 
hardware is 9000, the default MTU of the virtio net driver will also be 
set to 9000. When sending packets through "ping -s 5000", if the peer 
router does not support negotiating a path MTU through ICMP packets, the 
packets will be discarded. If the peer router supports negotiating path 
mtu through ICMP packets, the host side will perform packet sharding 
processing based on the negotiated path mtu, which is generally within 1500.
This is not a bugfix patch, I think setting the default mtu to within 
1500 would be more suitable here.Thanks.
>> so I changed the MTU to a more
>> general 1500 when 'Device maximum MTU' bigger than 1500.
>>
>> Signed-off-by: Hao Chen <chenh@...ur.tech>
>> ---
>>   drivers/net/virtio_net.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 8d8038538fc4..e71c7d1b5f29 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -4040,7 +4040,10 @@ static int virtnet_probe(struct virtio_device *vdev)
>>   			goto free;
>>   		}
>>
>> -		dev->mtu = mtu;
>> +		if (mtu > 1500)
> 
> s/1500/ETH_DATA_LEN/
> 
> Thanks.
> 
>> +			dev->mtu = 1500;
>> +		else
>> +			dev->mtu = mtu;
>>   		dev->max_mtu = mtu;
>>   	}
>>
>> --
>> 2.27.0
>>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ