linux-kernel - Re: [git pull] drm request 3

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:	Thu, 4 Mar 2010 19:25:24 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.sf.net
Subject: Re: [git pull] drm request 3

On Thu, Mar 04, 2010 at 11:14:11AM -0800, Linus Torvalds wrote:
> 
> 
> On Thu, 4 Mar 2010, Matthew Garrett wrote:
> > 
> > If you'd made it clear that you wanted the interface to be stable 
> > before it got merged, I suspect that it simply wouldn't have been merged 
> > until the interface was stable.
> 
> What kind of excuse is that? It's "we did bad things, but if we didn't do 
> those bad things, we'd have done _other_ bad things"?
> 
> Two wrong choices don't make a right.
> 
> Nobody has even answered me whether this is _forwards_compatible. It 
> clearly isn't backwards-compatible. IOW, is there _any_ way to move 
> back-and-forth over that commit, even if I can find a new libdrm?

Judging by 
http://cgit.freedesktop.org/mesa/drm/commit/?id=b496c63143e9a4ca02011582329bce2df99d9b7c 
, no. And if you're unhappy with that, don't use the driver. You enabled 
an option that's *documented* as potentially breaking between kernel 
releases, having been told that this was likely to happen, and now 
you're complaining?

> IOW, we know we have a problem here. But what's the solution? I know I can 
> revert it (I tried, I'm running that kernel now, nouveau works). That's 
> not a good solution, I know. But can you offer me a _better_ one? One that 
> doesn't involve "upgrade all the way to rawhide, and lose the ability to 
> bisect anything, or run plain 2.6.33".

Running -nv ought to be an option.

> So yes, I'm complaining. But I at least have mentioned one solution. You, 
> in contast, are just making excuses with no solutions.

You're asking volunteers who didn't ask for their driver to be merged to 
perform more work in order to support users they didn't ask for.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/