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]
Date:   Wed, 24 Apr 2019 09:56:04 +0200
From:   Simon Horman <horms@...ge.net.au>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Karsten Keil <isdn@...ux-pingi.de>, 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

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.

> CAPI in turn is not quite as obsolete, but as I have been unable to find
> any users, I would suggest moving it to drivers/staging while we
> figure out if anyone is using it. If not, it can then be removed
> as well. If it turns out that there are users that are on 5.x kernels
> or need to update to them, we can decide to leave parts of it for
> longer, or move them back.
> 
> If anyone is still using isdn4linux and CAPI with modern kernels, please
> speak up now.
> 
>       Arnd
> 
> [1] https://patchwork.kernel.org/patch/8484861/#17900371

...

Powered by blists - more mailing lists