Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Nov 2002 22:40:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Nov 2002 22:40:08 -0500 Received: from bjl1.asuk.net.64.29.81.in-addr.arpa ([81.29.64.88]:57047 "EHLO bjl1.asuk.net") by vger.kernel.org with ESMTP id ; Mon, 11 Nov 2002 22:40:08 -0500 Date: Tue, 12 Nov 2002 03:46:48 +0000 From: Jamie Lokier To: Rusty Russell Cc: "Perez-Gonzalez, Inaky" , "'Mark Mielke'" , linux-kernel@vger.kernel.org Subject: Users locking memory using futexes Message-ID: <20021112034648.GA11766@bjl1.asuk.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 18 Perez-Gonzalez, Inaky wrote: > [...] each time you lock a futex you are pinning the containing page > into physical memory, that would cause that if you have, for > example, 4000 futexes locked in 4000 different pages, there is going > to be 4 MB of memory locked in [...] Ouch! It looks to me like userspace can use FUTEX_FD to lock many pages of memory, achieving the same as mlock() but without the resource checks. Denial of service attack? -- Jamie - 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/