Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932137Ab0LAVC7 (ORCPT ); Wed, 1 Dec 2010 16:02:59 -0500 Received: from smtp-out.google.com ([216.239.44.51]:38194 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932123Ab0LAVC6 (ORCPT ); Wed, 1 Dec 2010 16:02:58 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version:content-type; b=UE/Snh5JDjCcfNRy7f1cB3VmEjFLb7b2yceOcLJ2aucDPNgqlli3I5EwSF8xAUg1j+ MtLbXDUXChNyicv0WVZw== Date: Wed, 1 Dec 2010 13:02:48 -0800 (PST) From: Hugh Dickins X-X-Sender: hughd@tigran.mtv.corp.google.com To: Andrew Morton cc: Trond Myklebust , Linus Torvalds , Nick Piggin , Nick Bowler , Linux Kernel Mailing List , linux-nfs@vger.kernel.org, Rik van Riel , Christoph Hellwig , Al Viro Subject: Re: [PATCH v2 3/3] NFS: Fix a memory leak in nfs_readdir In-Reply-To: <20101201123341.d12ef362.akpm@linux-foundation.org> Message-ID: References: <1291217804-11257-1-git-send-email-Trond.Myklebust@netapp.com> <1291217804-11257-2-git-send-email-Trond.Myklebust@netapp.com> <20101201150428.GA2879@elliptictech.com> <1291217804-11257-3-git-send-email-Trond.Myklebust@netapp.com> <1291217804-11257-4-git-send-email-Trond.Myklebust@netapp.com> <1291229669.6609.24.camel@heimdal.trondhjem.org> <1291234251.6609.39.camel@heimdal.trondhjem.org> <20101201123341.d12ef362.akpm@linux-foundation.org> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1677 Lines: 36 On Wed, 1 Dec 2010, Andrew Morton wrote: > On Wed, 01 Dec 2010 15:10:50 -0500 > Trond Myklebust wrote: > > > --- a/include/linux/fs.h > > +++ b/include/linux/fs.h > > @@ -602,6 +602,7 @@ struct address_space_operations { > > sector_t (*bmap)(struct address_space *, sector_t); > > void (*invalidatepage) (struct page *, unsigned long); > > int (*releasepage) (struct page *, gfp_t); > > + void (*freepage)(struct page *); > > ssize_t (*direct_IO)(int, struct kiocb *, const struct iovec *iov, > > loff_t offset, unsigned long nr_segs); > > int (*get_xip_mem)(struct address_space *, pgoff_t, int, > > It would be good to think about and then clearly spell out exactly what > state the page is in here. It is locked, and I assume clean and not > under writeback. What about its refcount, freezedness status and > eligibility for lookups? > > And as Hugh pointed out, some callees might needs the address_space* > although we can perhaps defer that until such a callee turns up. > If/when that happens we might have a problem though: if this locked > page is no longer attached to the address_space then what now pins the > address_space, protecting it from inode reclaim? That's an excellent point and trumps mine: it would be actively wrong to provide the struct address_space *mapping arg I was asking for. (Bet someone then tries stashing it away via page->private though.) Hugh -- 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/