linux-kernel - Re: possible deadlock on nouveau

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] [day] [month] [year] [list]

Date:	Tue, 6 May 2014 16:36:20 -0400
From:	Ilia Mirkin <imirkin@...m.mit.edu>
To:	balbi@...com
Cc:	David Airlie <airlied@...ux.ie>, Ben Skeggs <bskeggs@...hat.com>,
	Dave Airlie <airlied@...hat.com>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Martin Peres <martin.peres@...ri.fr>
Subject: Re: possible deadlock on nouveau

On Tue, May 6, 2014 at 4:29 PM, Felipe Balbi <balbi@...com> wrote:
> Hi,
>
> Just caught this with v3.14-rc4 running with
>
>         01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1)
>
> full dmesg attached
>
> [  239.589213] ======================================================
> [  239.589214] [ INFO: possible circular locking dependency detected ]
> [  239.589216] 3.15.0-rc4-fb+ #5 Not tainted
> [  239.589217] -------------------------------------------------------
> [  239.589218] swapper/1/0 is trying to acquire lock:
> [  239.589219]  (&(&priv->lock)->rlock#2){-.....}, at: [<ffffffff814a6b98>] nouveau_therm_update+0x48/0x310
> [  239.589228]
> [  239.589228] but task is already holding lock:
> [  239.589230]  (&(&priv->sensor.alarm_program_lock)->rlock){-.....}, at: [<ffffffff814a85a4>] alarm_timer_callback+0x54/0xe0
> [  239.589234]
> [  239.589234] which lock already depends on the new lock.

I believe this is fixed by
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=61679fe153b2b9ea5b5e2ab93305419e85e99a9d

Try a more recent kernel? Or did you perhaps mean that you were
running into this with v3.15-rc4, in which case that commit didn't fix
the issue hard enough...

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