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] [day] [month] [year] [list]
Message-ID: <87560af9-970c-d36d-e1de-e13c593e4b33@gmail.com>
Date:   Sun, 10 Feb 2019 20:01:33 -0700
From:   David Ahern <dsahern@...il.com>
To:     Davide Caratti <dcaratti@...hat.com>,
        Stephen Hemminger <stephen@...workplumber.org>
Cc:     Andrea Claudi <aclaudi@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next] use print_{,h}hu instead of print_uint when
 format specifier is %{,h}hu

On 2/7/19 3:51 AM, Davide Caratti wrote:
> in this way, a useless cast to unsigned int is avoided in bpf_print_ops()
> and print_tunnel().
> 
> Tested with:
>  # ./tdc.py -c bpf
> 
> Suggested-by: Stephen Hemminger <stephen@...workplumber.org>
> Cc: Andrea Claudi <aclaudi@...hat.com>
> Signed-off-by: Davide Caratti <dcaratti@...hat.com>
> ---
>  ip/ipl2tp.c | 4 ++--
>  lib/bpf.c   | 6 +++---
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 

applied to iproute2-next. Thanks


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ