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

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: <1426499217.26437.7.camel@x220>
Date:	Mon, 16 Mar 2015 10:46:57 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Dave Airlie <airlied@...ux.ie>
Cc:	Thierry Reding <treding@...dia.com>, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [git pull] drm fixes

On Fri, 2015-03-13 at 12:36 +0100, Paul Bolle wrote:
> Dave Airlie schreef op vr 06-03-2015 om 21:52 [+0000]:
> > Thierry Reding (1):
> >       drm/mm: Support 4 GiB and larger ranges
> 
> Yesterday the screen on my (outdated) ThinkPad X41 went, well, black
> while it was busy compiling something unattended. I eventually had to
> power cycle that laptop to regain control. I found a drm related BUG()
> in the logs (pasted at the end of the message).
> 
> I only have three months worth of logs (a diagnoising session pushed
> most of the logs into /dev/null a few weeks ago). But this is the only
> time I saw that BUG in that period. Now that commit is the last thing
> touching that code, and the various unsigned long to u64 conversions
> _might_ just have gone wrong for 32 bits. I didn't spot anything utterly
> obvious in that commit, but point a finger at it just in case.

Surely fixed by commit 046d669c62f3 ("[PATCH] drm/mm: Fix support 4 GiB
and larger ranges"). It corrects a mistake introduced by the commit
quoted above. So at least I pointed a finger at the right commit.

Thanks,


Paul Bolle

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