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
| ||
|
Message-ID: <CAM_iQpXLBR3gnheLTxeu_wkELs5jOS1+SaeiLZknA6sbC19NmA@mail.gmail.com> Date: Sat, 23 Feb 2019 17:11:08 -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: > > You are forcing everyone who wants to use this to add a curstom local > source code change into their build. What's wrong with this? People carry custom changes in anyway, do we really need to care about all the downstream changes? If yes, can I just add some debugging prink's that no one is going to use except me? My argument would be you can't force me to add a custom local source code change. Can we just play this fairly instead of just for any special people? Thanks!
Powered by blists - more mailing lists