linux-kernel - Re: [git pull] drm: previous pull req + 1.

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: <alpine.DEB.2.00.0906220920080.23557@skynet.skynet.ie>
Date:	Mon, 22 Jun 2009 09:30:27 +0100 (IST)
From:	Dave Airlie <airlied@...ux.ie>
To:	Thomas Hellström <thomas@...pmail.org>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alex Deucher <alexdeucher@...il.com>,
	Andrew Lutomirski <luto@....edu>, dri-devel@...ts.sf.net,
	Jerome Glisse <jglisse@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm: previous pull req + 1.


> >   
> There is a ttm_fbdev_mmap() function in TTM that may help in this situation.
> As with the standard ttm mmap it's using fault() which means it's possible to
> move out the backing buffer object if you first reserve it and then call
> unmap_mapping_range() on the relevant fbdev address space to kill existing
> user-space mappings.

Yup I've looked at this from the fbdev pov, however I hit the same problem
with the fbcon writes happening pretty much whenever they wanted to.

It might be possible to move the fbcon around by updating screen_base, but 
you'd need to have some sort of lock around the read/write functions, I 
think locking on each individual read/write might be a lot of overhead.

Ideallly something analogous to the X server Prepare/Finish access hooks.

Dave.

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