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-prev] [day] [month] [year] [list]
Message-ID: <08ac439a-6530-7feb-5eb8-ba60bfa92cda@gmail.com>
Date:   Sat, 18 Jan 2020 14:49:09 -0700
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org
Cc:     dsahern@...il.com, mlxsw@...lanox.com,
        Ido Schimmel <idosch@...lanox.com>
Subject: Re: [PATCH iproute2-next] ip route: Print "rt_offload" and "rt_trap"
 indication

On 1/16/20 11:43 AM, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@...lanox.com>
> 
> The kernel now signals the offload state of a route using the
> 'RTM_F_OFFLOAD' and 'RTM_F_TRAP' flags. Print these to help users
> understand the offload state of each route. The "rt_" prefix is used in
> order to distinguish it from the offload state of nexthops.
> 
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> ---
>  ip/iproute.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 

applied to iproute2-next. Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ