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: <20100205090009.GA8272@elte.hu>
Date:	Fri, 5 Feb 2010 10:00:09 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Dave Airlie <airlied@...ux.ie>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	dri-devel@...ts.sf.net, Alex Deucher <alexdeucher@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org
Subject: Re: hung bootup with "drm/radeon/kms: move radeon KMS on/off switch
 out of staging."


* Dave Airlie <airlied@...ux.ie> wrote:

> 
> > If it now does not boot up if all its sub-options are enabled, even of some 
> > of those sub-options are new, does that count as a driver regression? Sure it 
> > does to me ...
> 
> But it doesn't to anyone else under any reasonable meaning of the word 
> regression.

There are reactions in this thread that contradict your 'anyone else' point.

> The config option states
> "Choose this option if you want kernel modesetting enabled by default,
>           and you have a new enough userspace to support this. Running old
>           userspaces with this enabled will cause pain."
> 
> Will cause pain sounds painful to me, I can make it seem much worse if 
> you'd like.

Except you are missing that the hang (and the first crash as well) happens on 
brand-new user-space just as much - not just on 'old userspaces'.

The bugs i've triggered are independent of any user-space component - it 
happens with a fresh distro just as much.

As i suggested before, at least the text should be updated to include what 
has been written about CONFIG_DRM_RADEON_KMS in this thread before:

 > This is a completely new driver.  It's only part of the existing drm for 
 > compatibility reasons.  It requires an entirely different graphics stack 
 > above it and works very differently from the old drm stack.

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ