linux-kernel - Re: [PATCH] ISDN: mark as 32-bit only

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: <20061002.133715.63105344.davem@davemloft.net>
Date:	Mon, 02 Oct 2006 13:37:15 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeff@...zik.org
Cc:	jengelh@...ux01.gwdg.de, kkeil@...e.de, kai.germaschewski@....de,
	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ISDN: mark as 32-bit only

From: Jeff Garzik <jeff@...zik.org>
Date: Sun, 01 Oct 2006 23:54:42 -0400

> Jan Engelhardt wrote:
> >> Tons of ISDN drivers cast pointers to/from 32-bit values, which just
> >> won't work on 64-bit.
> > 
> > Should not that be fixed instead of restricting isdn to 32bit?
> 
> It hasn't been fixed in many years, and I don't see anyone stepping up 
> to the plate, even with my current trolling...  :)
> 
> > Though this is probably the best temporary workaround until someone can 
> > fix up all the "tons".
> 
> I have a better workaround, I think.

I totally agree with Jeff.  The ISDN layer is effectively unmaintained
and the vast majority of the ISDN work that does actually occur is
done out-of-tree.

If someone cares enough about the ISDN layer, they can make changes
after Jeff's goes in to reduce the protection to a per-driver basis.

But right now, blocking this whole unmaintained pile of poo on 64-bit
is the best starting point.

We're talking about effectively an 8 year old code base that hasn't
been touched much at all during that time.  Let's be honest about the
situation.  The only subsystem that is more unmaintained and gathering
dust is probably the ftape layer :-)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/