netdev - patch for iproute2

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1905181350500.8326@feathers.ext.sig.nz>
Date:   Sat, 18 May 2019 13:52:36 +1000 (AEST)
From:   Martin Kealey <martin@...ahaupo.gen.nz>
To:     netdev@...r.kernel.org
Subject: patch for iproute2

Hello iproute2 maintainer.

(Sorry, I don't know your name)

I recently noticed a discrepancy: the internal documentation for the ip
command says that an *RTT* value can be sufficed with "s" (second) or "ms"
(millisecond), but in practice no suffix of any kind is accepted.

I found that that commit 697ac63905cb5ca5389cd840462ee9868123b77f to
git://git.kernel.org/pub/scm/network/iproute2/iproute2.git caused this
regression; it was over-zealous in disallowing non-digits in *all* contexts
where a number is expected.

As far as I can tell, this does not have any kernel-related impact, merely
it affects what arguments are accepted by the "ip" command.

I have a suitable patch for fixing this; what is the procedure for
submitting it?

-Martin