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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <335b537bb55064a508cafdcfcadecb03c806a867.camel@microchip.com>
Date:   Tue, 6 Sep 2022 11:01:04 +0000
From:   <Arun.Ramadoss@...rochip.com>
To:     <netdev@...r.kernel.org>
Subject: Testing set_ageing_time in net: dsa

Hi,
I am implementing the set_ageing_time hook for the lan937x and ksz9477
switches. During testing the functionality using the user space
commands, found some differences. I am trying to set the ageing time to
10 seconds.
1. brctl setageing br0 10 - It is working as expected. msecs parameter
in the ageing time is received as 1000 (10 * 1000).
2. ip link set dev br0 type bridge ageing_time 10
	- It sets the ageing time as 0. When I debugged and printed the
value in lan937x_set_ageing_time, where I get the msecs parameter as
100 instead of 10000. The value is only multiples of 10 instead of 1000
during sec to msecs conversation.

Is there any difference in the user space command implementation
between brctl and ip?. And which command needs to be used for testing.
I bascially implementing it, is to test the kselftest for
bridge_vlan_aware.sh in kselftest/net/forwarding where the learning
test cases are failing. Any help is much appreciated.

Thanks
Arun 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ