From: Jan Hudec <bulb@ucw.cz>
To: Ian Kent <raven@themaw.net>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Some questions about memory allocation and BKL
Date: Sun, 26 Oct 2003 16:54:18 +0100 [thread overview]
Message-ID: <20031026155418.GM1465@vagabond> (raw)
In-Reply-To: <Pine.LNX.4.44.0310262351510.3069-100000@raven.themaw.net>
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 <bulb@ucw.cz>
next prev parent reply other threads:[~2003-10-26 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 4:42 Some questions about memory allocation and BKL Ian Kent
2003-10-26 9:44 ` Jan Hudec
2003-10-26 11:27 ` Ian Kent
2003-10-26 12:43 ` Jan Hudec
2003-10-26 13:21 ` Ian Kent
2003-10-26 14:01 ` Jan Hudec
2003-10-26 15:59 ` Ian Kent
2003-10-26 15:54 ` Jan Hudec [this message]
2003-10-26 18:37 ` dirty buffer_head, but not marked dirty Mark B
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031026155418.GM1465@vagabond \
--to=bulb@ucw.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox