linux-kernel - Re: fsl-dcu not works on latest "drm-next"

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]

Date:	Fri, 27 May 2016 20:50:48 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Stefan Agner <stefan@...er.ch>
Cc:	Alexander Stein <alexander.stein@...tec-electronic.com>,
	linux-kernel@...r.kernel.org, Meng Yi <meng.yi@....com>,
	dri-devel@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
	airlied@...hat.com
Subject: Re: fsl-dcu not works on latest "drm-next"

On Fri, May 27, 2016 at 10:36:21AM -0700, Stefan Agner wrote:
> On 2016-05-27 05:20, Mark Brown wrote:

> > That's another way of addressing it of course, but unless the register
> > map actually is sparse it's probably still sensible to send the
> > conversion to flat cache as a fix.

> The regcache is used for suspend, but the suspend implementation in its
> current form is not in not working. Hence I felt it is not worth fixing
> part of something which is broken as a whole anyway.

> So far I was under the impression the "only" issue using REGCACHE_RBTREE
> is that it triggers a warning when enabling lockdep. 

The warning is warning about a real issue that might crop up - it's not
just cosmetic, it's doing allocations inside a spinlock which could
break badly.  Even if it doesn't help this issue I'd recommend getting a
fix in if you can to avoid it blowing up on people (unless the more
complete set of changes can go in as a bugfix of course in which case
it's moot).

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)