| 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
| ||
|
Message-ID: <21d7e9970710210517y585bf5a2lda34f0ae2d8b6183@mail.gmail.com> Date: Sun, 21 Oct 2007 22:17:45 +1000 From: "Dave Airlie" <airlied@...il.com> To: "Andi Kleen" <andi@...stfloor.org> Cc: "Nick Piggin" <nickpiggin@...oo.com.au>, "David Chinner" <dgc@....com>, "Jeremy Fitzhardinge" <jeremy@...p.org>, xfs@....sgi.com, Xen-devel <xen-devel@...ts.xensource.com>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, "Mark Williamson" <mark.williamson@...cam.ac.uk>, "Morten Bøgeskov" <xen-users@...ten.bogeskov.dk>, xfs-masters@....sgi.com Subject: Re: Interaction between Xen and XFS: stray RW mappings On 10/15/07, Andi Kleen <andi@...stfloor.org> wrote: > > Hmm, OK. It looks like DRM vmallocs memory (which gives highmem). > > I meant I'm not sure if it uses that memory uncached. I admit > not quite understanding that code. There used to be at least > one place where it set UC for an user mapping though. Currently the only DRM memory handed to userspace is vmalloc_32 in drm_scatter.c I notice the VIA driver does its own vmalloc for dmablit, so it may have an issue with this if highmem is involved. This will change with the upcoming memory manager so I'll need to investigate it a bit perhaps... 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/
Powered by blists - more mailing lists