linux-kernel - Re: 2.6.32 CONFIG

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: <20091204122638.597d30b5@lxorguk.ukuu.org.uk>
Date:	Fri, 4 Dec 2009 12:26:38 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Graham Murray <gmurray@...wayone.co.uk>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: 2.6.32 CONFIG_SX marked as BROKEN

On Fri, 04 Dec 2009 11:08:05 +0000
Graham Murray <gmurray@...wayone.co.uk> wrote:

> Commit 412145947adfca60a4b5b4893fbae82dffa25edd marked CONFIG_SX as
> Broken. The commit comments state that there are no users. We are using
> SX cards in production servers. I discovered this when I attempted to
> upgrade a development server to 2.6.32 and it failed to find the cards.

The original long discussion with the patch was intentionally trimmed for
the kernel submit. They were marked broken not just because we could find
no users but also because the code in the kernel has some very serious
flaws which I was able to demonstrate are exploitable.

Had it merely sucked it wouldn't have been marked as broken.

The bigger problem is that the design of the ancient midlayer gs code it
uses is so broken that it really needs a major rework or the sx driver
extracting from it completely. Both are major bits of work.

Alan

--
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/