netdev - Re: [RFC 3/4] nfp: make use of extended ack message reporting

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

Date:   Tue, 25 Apr 2017 10:20:22 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     jhs@...atatu.com
Cc:     jakub.kicinski@...ronome.com, netdev@...r.kernel.org,
        johannes@...solutions.net, dsa@...ulusnetworks.com,
        daniel@...earbox.net, alexei.starovoitov@...il.com,
        bblanco@...il.com, john.fastabend@...il.com, kubakici@...pl,
        oss-drivers@...ronome.com
Subject: Re: [RFC 3/4] nfp: make use of extended ack message reporting

From: Jamal Hadi Salim <jhs@...atatu.com>
Date: Tue, 25 Apr 2017 08:42:32 -0400

> So are we going to standardize these strings?

No.

> i.e what if some user has written a bash script that depends on this
> string and it gets changed later.

They can't do that.

It's free form extra information an application may or not provide
to the user when the kernel emits it.