Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 13 Dec 2002 04:45:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 13 Dec 2002 04:45:58 -0500 Received: from pc2-cwma1-4-cust129.swan.cable.ntl.com ([213.105.254.129]:31688 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Fri, 13 Dec 2002 04:45:58 -0500 Subject: Re: atyfb in 2.5.51 From: Alan Cox To: Geert Uytterhoeven Cc: "David S. Miller" , James Simmons , Benjamin Herrenschmidt , Paul Mackerras , Linux Kernel Mailing List , Linux Frame Buffer Device Development In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 13 Dec 2002 10:26:55 +0000 Message-Id: <1039775215.25097.5.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 637 Lines: 13 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 - 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/