linux-kernel - Re: [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check

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: <20150325132650.GZ1349@phenom.ffwll.local>
Date:	Wed, 25 Mar 2015 14:26:50 +0100
From:	Daniel Vetter <daniel@...ll.ch>
To:	Sedat Dilek <sedat.dilek@...il.com>
Cc:	Dave Airlie <airlied@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and
 drm_atomic_check_only()

On Tue, Mar 24, 2015 at 07:09:03PM +0100, Sedat Dilek wrote:
> On Mon, Mar 23, 2015 at 9:25 AM, Daniel Vetter <daniel@...ll.ch> wrote:
> > On Mon, Mar 23, 2015 at 07:25:27AM +0100, Sedat Dilek wrote:
> >> Hi,
> >>
> >> I did my weekly update of the Linux RC (here: v4.0-rc5) and fell over
> >> some warning in the drm area.
> >>
> >> Please have a look...
> >
> 
> Hi Daniel,
> 
> > Just to confirm: Both are new in -rc5 and haven't been around in -rc4?
> >
> 
> Yeah, rc4 was OK but with rc5 I have seen these warnings.
> 
> > Also can you pls give -nightly a spin and see what happens there?
> >
> 
> drm-intel-nightly (2015y-03m-24d-09h-19m-43s UTC) pulled on top of rc5
> does not show any warnings in the drm | i915 area.

drm-fixes has 2 cherry-picks from -next to address the worst offenders,
there's one more which is waiting for confirmation:

commit fb9981aa675eb7b398849915364916fd98833cfa
Author: Damien Lespiau <damien.lespiau@...el.com>
Date:   Thu Feb 5 19:24:25 2015 +0000

    drm/i915: Fix atomic state when reusing the firmware fb

Please apply that commit from -next on top of drm-fixes and retest.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
--
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/