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: <c44bd7e8-68ff-44f8-b50b-4d27b4fe29dc@app.fastmail.com>
Date:   Mon, 09 Jan 2023 09:44:38 +0100
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Jiri Slaby" <jirislaby@...nel.org>,
        "Jan Engelhardt" <jengelh@...i.de>
Cc:     "Stephen Hemminger" <stephen@...workplumber.org>,
        Netdev <netdev@...r.kernel.org>,
        "David Ahern" <dsahern@...nel.org>,
        "Jonathan Corbet" <corbet@....net>,
        "David S . Miller" <davem@...emloft.net>,
        "Eric Dumazet" <edumazet@...gle.com>,
        "Jakub Kicinski" <kuba@...nel.org>,
        "Paolo Abeni" <pabeni@...hat.com>,
        "Thomas Bogendoerfer" <tsbogend@...ha.franken.de>,
        "Michael Ellerman" <mpe@...erman.id.au>,
        "Nicholas Piggin" <npiggin@...il.com>,
        "Christophe Leroy" <christophe.leroy@...roup.eu>,
        "Pablo Neira Ayuso" <pablo@...filter.org>,
        "Jozsef Kadlecsik" <kadlec@...filter.org>,
        "Florian Westphal" <fw@...len.de>, "Borislav Petkov" <bp@...e.de>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        "Andrew Morton" <akpm@...ux-foundation.org>,
        "Neeraj Upadhyay" <quic_neeraju@...cinc.com>,
        "Randy Dunlap" <rdunlap@...radead.org>,
        "Damien Le Moal" <damien.lemoal@...nsource.wdc.com>,
        "Muchun Song" <songmuchun@...edance.com>,
        "Akhmat Karakotov" <hmukos@...dex-team.ru>,
        "Antoine Tenart" <atenart@...nel.org>,
        "Xin Long" <lucien.xin@...il.com>,
        "Juergen Gross" <jgross@...e.com>,
        "Hans de Goede" <hdegoede@...hat.com>,
        "Nathan Fontenot" <nathan.fontenot@....com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        "Suma Hegde" <suma.hegde@....com>, "Chen Yu" <yu.c.chen@...el.com>,
        "William Breathitt Gray" <vilhelm.gray@...il.com>,
        "Xie Yongji" <xieyongji@...edance.com>,
        Pali Rohár <pali@...nel.org>,
        "Alexandre Ghiti" <alexandre.ghiti@...onical.com>,
        "Chuck Lever" <chuck.lever@...cle.com>,
        "Jeff Layton" <jlayton@...nel.org>,
        "Paul Gortmaker" <paul.gortmaker@...driver.com>,
        "Nikolay Aleksandrov" <razor@...ckwall.org>,
        "Sebastian Andrzej Siewior" <bigeasy@...utronix.de>,
        "Menglong Dong" <imagedong@...cent.com>,
        "Petr Machata" <petrm@...dia.com>,
        "Daniel Borkmann" <daniel@...earbox.net>,
        "Roopa Prabhu" <roopa@...dia.com>,
        "Yuwei Wang" <wangyuweihx@...il.com>,
        "Shakeel Butt" <shakeelb@...gle.com>,
        "Kuniyuki Iwashima" <kuniyu@...zon.com>,
        "Kees Cook" <keescook@...omium.org>,
        "Stefano Garzarella" <sgarzare@...hat.com>,
        "Florian Fainelli" <f.fainelli@...il.com>,
        "Wang Qing" <wangqing@...o.com>, "Yu Zhe" <yuzhe@...china.com>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        "open list" <linux-kernel@...r.kernel.org>,
        "open list:MIPS" <linux-mips@...r.kernel.org>,
        "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" 
        <linuxppc-dev@...ts.ozlabs.org>,
        "open list:NETFILTER" <netfilter-devel@...r.kernel.org>,
        "open list:NETFILTER" <coreteam@...filter.org>
Subject: Re: [PATCH net-next] Remove DECnet support from kernel

On Mon, Jan 9, 2023, at 09:34, Jiri Slaby wrote:
> On 09. 01. 23, 9:14, Jan Engelhardt wrote:
>> On Monday 2023-01-09 08:04, Jiri Slaby wrote:
>
> Right, we used to keep providing also defines and structs in uapi 
> headers of removed functionality. So that the above socket would 
> compile, but fail during runtime.
>
> I am not biased to any solution. In fact, I found out trinity was fixed 
> already. So either path networking takes, it's fine by me. I'm not sure 
> about the chromium users, though (and I don't care).

Chromium and some of the others look like automatically generated
lists of files and the rest seem to have compile-time checks.

>From a brief look at all the packages in the debian codesearch
link you provided, I don't see any that are likely to cause
problems aside from trinity.

    Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ