Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 22 Dec 2002 08:33:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 22 Dec 2002 08:33:50 -0500 Received: from mail2.sonytel.be ([195.0.45.172]:16865 "EHLO mail.sonytel.be") by vger.kernel.org with ESMTP id ; Sun, 22 Dec 2002 08:33:50 -0500 Date: Sun, 22 Dec 2002 14:40:11 +0100 (MET) From: Geert Uytterhoeven To: Alan Cox cc: "David S. Miller" , James Simmons , Benjamin Herrenschmidt , Paul Mackerras , Linux Kernel Mailing List , Linux Frame Buffer Device Development Subject: Re: atyfb in 2.5.51 In-Reply-To: <1039775215.25097.5.camel@irongate.swansea.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1240 Lines: 32 On 13 Dec 2002, Alan Cox wrote: > On Fri, 2002-12-13 at 08:53, Geert Uytterhoeven wrote: > > (At first I thought you meant an instruction where the opcode crosses those > > two memory types, but we don't put code in video RAM...) > > I did. The frame buffer drivers support mmap(). x86 has no "non-exec" > bit. So any user able to open /dev/fb can bring down such a box. Similar > things apply with early athlon and prefetching /dev/fb Weird... So it really crashes the box, not just throwing an exception? On PPC you cannot use prefetching on non-cached memory, but if you try it won't take down the whole box. Then make sure /dev/fb is accessible by `trusted' users on such machines. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/