netdev - Re: [PATCH v3 net-next 2/2] net: sock: undefine SOCK

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: <CAM_iQpX=EE89g3jO6jAfpGmKrjhYscW5EwE+ZLPhh_70f4Ojuw@mail.gmail.com>
Date:   Sat, 23 Feb 2019 17:26:52 -0800
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     Yafang Shao <laoar.shao@...il.com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Joe Perches <joe@...ches.com>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>,
        shaoyafang@...iglobal.com
Subject: Re: [PATCH v3 net-next 2/2] net: sock: undefine SOCK_DEBUGGING

On Sat, Feb 23, 2019 at 1:21 PM David Miller <davem@...emloft.net> wrote:
>
> From: Yafang Shao <laoar.shao@...il.com>
> Date: Sun, 17 Feb 2019 22:26:32 +0800
> > The reason why I don't remove it comepletely is that someone may still
> > would like to use it for debugging.

Please remove it completely.

The rule here is we upstream only care about in-tree users, any out-of-tree
user is beyond what we care. They either need to push their code that uses
this to upstream, or have to carry a revert downstream.

People carry downstream changes all the time, this one isn't an exception.

Let's respect rules.

Thanks.