linux-kernel - Re: [git pull] drm fixes for -rc1

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:	Tue, 29 Mar 2011 08:49:52 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Dave Airlie <airlied@...ux.ie>, torvalds@...ux-foundation.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm fixes for -rc1

On Tue, 29 Mar 2011 10:11:21 +0300, Pekka Enberg <penberg@...nel.org> wrote:
> On Mon, Mar 28, 2011 at 10:09 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
> Let me know if there's a patch/git tree to test. The flicker is
> extremely annoying and I boot the machine often because it's my main
> kernel development laptop.

I will let you know as soon as I have something ready for testing.
 
> > That's an old userspace bug, which so far no one has been able to
> > reproduce on the upstream ddx.
> 
> Is it harmless? Why is the kernel complaining about it?

Being pragmatic, so that I can tell one EINVAL apart from another. And
it's only mostly harmless. Userspace is attempting to write to/read from
a buffer it has marked as being no longer required, so some rendering is
going amiss. And it does not rule out the possibility that at some point
it will catch the error later and result in a SIGBUS being sent to the
application (probably X).

However since it is not a kernel error nor is it fatal, that and a lot of
similar messages can be demoted to debug.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
--
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/