From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Hudec Subject: Re: Some questions about memory allocation and BKL Date: Sun, 26 Oct 2003 16:54:18 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20031026155418.GM1465@vagabond> References: <20031026140113.GL1465@vagabond> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel Return-path: Received: from cimice4.lam.cz ([212.71.168.94]:19687 "EHLO vagabond.light.src") by vger.kernel.org with ESMTP id S263235AbTJZPya (ORCPT ); Sun, 26 Oct 2003 10:54:30 -0500 To: Ian Kent Content-Disposition: inline In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org On Sun, Oct 26, 2003 at 23:59:09 +0800, Ian Kent wrote: > > Thanks. This is exaclty what I needed to clear things up. > > I don't mean to be a pest but I have just one more question. > > In 2.6 there is a lock for the vfsmount mount list. I can't see anything > in 2.4 or the doco. How should this structure be protected during a > traversal of the vfsmount tree? > > On Sun, 26 Oct 2003, Jan Hudec wrote: > > > (try to look it up in rename code). I don't know about mountpoint, but > > obviously requires some locking. > > d_mountpoint just returns the value of dentry->d_mounted, an int. Yes. But to know what locks you need when you read it, you must look what locks are held when it's changed. ------------------------------------------------------------------------------- Jan 'Bulb' Hudec