linux-kernel - Re: [git pull] drm for 3.19-rc1

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]

Message-ID: <CA+55aFxmT98972EM7OaJoF_P8AoA1Lyj6WcN9LaT+MC_wgrhRQ@mail.gmail.com>
Date:	Mon, 15 Dec 2014 17:03:50 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Airlie <airlied@...il.com>
Cc:	Dave Airlie <airlied@...ux.ie>,
	Daniel Vetter <daniel.vetter@...el.com>,
	Jani Nikula <jani.nikula@...ux.intel.com>,
	Thomas Hellstrom <thellstrom@...are.com>,
	Alex Deucher <alexander.deucher@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm for 3.19-rc1

On Mon, Dec 15, 2014 at 4:48 PM, Dave Airlie <airlied@...il.com> wrote:
>
> I'd be inclined to just revert this for now, it is annoying we let
> userspace away with this, but we probably need to find a better
> way to enforce it, since the cat is out of the bag.

.. why did that commit ever even get far enough to get to me?

It seems to happen on any reasonably modern Intel graphics - at least
it happens on both my laptop and my desktop. And I'm running
bog-standard F20, so either nobody ever even tested that broken thing,
or nobody bothered to look at the messages to notice it was broken.
Either way, it shows a rather distinct lack of actual testing,
wouldn't you say?

I really see no excuse for crap like this. If I find obvious bugs
immediately, on my very normal hardware and very normal distribution,
that means that there is something wrong in the development process.
If I was some subtle timing-dependent thing, or I were to be using
eally odd hardware, or I had to do something special to trigger it,
that would be one thing. But that's definitely not the case here.

                       Linus "not happy" Torvalds
--
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/