linux-kernel - Re: [git pull] drm urgent fix

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: <CA+55aFweWR=nDzc2Y=rCtL_H8JfdprQiCimN5dwc+TgyD4Bjsg@mail.gmail.com>
Date:	Wed, 25 Mar 2015 20:04:41 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Airlie <airlied@...il.com>
Cc:	Dave Airlie <airlied@...ux.ie>, Daniel Vetter <daniel@...ll.ch>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm urgent fix

On Wed, Mar 25, 2015 at 3:43 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I'm going to wait a bit more with this, since clearly things are still
> in flux, and these two commits don't actually fix everything at all.
>
> There's apparently at least one more fix necessary.

Indeed. I can see the problem myself.

With current git I get two warnings:

   WARNING: CPU: 3 PID: 325 at include/linux/kref.h:47
drm_framebuffer_reference+0x72/0x80 [drm]()
   WARNING: CPU: 4 PID: 107 at drivers/gpu/drm/drm_atomic.c:482
drm_atomic_check_only+0x32d/0x4f0 [drm]()

and testing the pull it gets rid of the first one, but no tthe second one.

So that urgent fix is very much still lacking.

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