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]
Message-Id: <20200805.121110.1918790855908756881.davem@davemloft.net>
Date:   Wed, 05 Aug 2020 12:11:10 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     liuhangbin@...il.com
Cc:     gnault@...hat.com, netdev@...r.kernel.org, pmachata@...il.com,
        roopa@...ulusnetworks.com, dsahern@...nel.org, akaris@...hat.com
Subject: Re: [PATCH net] Revert "vxlan: fix tos value before xmit"

From: Hangbin Liu <liuhangbin@...il.com>
Date: Wed, 5 Aug 2020 18:18:07 +0800

> Should I re-post the patch with Fixes flag?

No, I took care the Fixes tag and queued this up for -stable.

But you do need to explain what kind of testing you even did on this
change we are reverting.  Did you make this change purely on
theoretical grounds and a code audit?

Because it is clear now that this commit broke things and did not fix
anything at all.

Please explain.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ