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  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]
Date:	Thu, 2 May 2013 10:57:27 +1000
From:	Dave Airlie <>
To:	Daniel Vetter <>
Cc:	Borislav Petkov <>,
	lkml <>,
	dri-devel <>
Subject: Re: WARNING: at drivers/gpu/drm/drm_crtc.c:82 drm_warn_on_modeset_not_all_locked+0x8d/0xc0()

On Thu, May 2, 2013 at 10:41 AM, Daniel Vetter <> wrote:
> On Thu, May 2, 2013 at 2:02 AM, Borislav Petkov <> wrote:
>> Hi,
>> I'm seeing this when booting latest Linus tree + tip/master in kvm.
>> Config is attached. Looks like it cannot find root fs and panics and
>> calls the panic notifier which screams in drm_crtc.c because not all
>> modeset locks are taken. Maybe bogus?
> Locking in the drm panic notifiere is completely bogus (as in simply
> does not exist). The only difference is that with the new locking
> scheme in 3.9 we're now pretty obnixious about checking for these
> kinds of things. Also, drm drivers love to sleep in the panic
> handlers, too. It's somewhere on my giant list of things to fix in drm
> land, but I'm not sure whether I'll get around to it in this life or
> the next. Maybe we just need to shut up the WARN in case of a panic
> ...

Maybe? of course you do.

its a panic, getting anything on the screen is vastly more important than
the locking being perfect, any chance of any info landing on the screen
is being decreased by this spew.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists