netdev - Re: [PATCH 0/5] isdn: deprecate non-mISDN drivers

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 24 Apr 2019 11:15:32 +0200
From:   Simon Horman <horms@...ge.net.au>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Karsten Keil <isdn@...ux-pingi.de>,
        Networking <netdev@...r.kernel.org>,
        isdn4linux@...tserv.isdn4linux.de, Paul Bolle <pebolle@...cali.nl>,
        Holger Schurig <holgerschurig@...glemail.com>,
        Tilman Schmidt <tilman@...p.cc>,
        Al Viro <viro@...iv.linux.org.uk>,
        gigaset307x-common@...ts.sourceforge.net
Subject: Re: [PATCH 0/5] isdn: deprecate non-mISDN drivers

On Wed, Apr 24, 2019 at 10:14:55AM +0200, Arnd Bergmann wrote:
> On Wed, Apr 24, 2019 at 9:56 AM Simon Horman <horms@...ge.net.au> wrote:
> >
> > Hi Arnd,
> >
> > On Tue, Apr 23, 2019 at 05:11:32PM +0200, Arnd Bergmann wrote:
> > > When isdn4linux came up in the context of another patch series, I
> > > remembered that we had discussed removing it a while ago.
> > >
> > > It turns out that the suggestion from Karsten Keil wa to remove I4L
> > > in 2018 after the last public ISDN networks are shut down. This has
> > > happened now (with a very small number of exceptions), so I guess it's
> > > time to try again.
> > >
> > > We currently have three ISDN stacks in the kernel: the original
> > > isdn4linux, the newer CAPI, and finally mISDN stack.
> > >
> > > As far as I can tell, anyone using ISDN with mainline kernel drivers in
> > > the past few years uses mISDN, and this is typically used for voice-only
> > > PBX installations that don't require a public network.
> > >
> > > The older stacks support additional features for data networks, but those
> > > typically make no sense any more if there is no network to connect to.
> > >
> > > My proposal for this time is to kill off isdn4linux entirely, as it seems
> > > to have been unusable for quite a while. This code has been abandoned
> > > for many years and it does get in the way of maintenance.
> >
> > I think there is an editing error somewhere above. Perhaps it should read
> >
> > ... and it does not get anything in the way of maintenance.
> 
> This is certainly a true statement as well, but what I meant is that
> the presence of isdn4linux in the kernel is causing extra work whenever
> we want to do treewide changes. I'll rephrase to make that clearer.

Thanks Arnd, much appreciated.