From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Subject: i_flags locking
Date: Mon, 25 Jun 2007 18:42:44 +0200 [thread overview]
Message-ID: <20070625164244.GK18198@duck.suse.cz> (raw)
Hi,
I came across the following question: What is the proper locking for
using i_flags? I've noticed i_flags are read freely without any lock.
The modifications I've seen e.g. in ext3 were done under i_mutex. Is this
right?
BTW it means that when checking i_flags we can see intermediate states
in ext3_set_inode_flags() when all flags are cleared and the proper flags
are not yet set, right?
I'm currently playing with something like inotify for subtree and I'd
need to modify i_flags but using i_mutex unpleasantly interferes with
directory locking...
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next reply other threads:[~2007-06-25 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 16:42 Jan Kara [this message]
2007-06-30 9:30 ` i_flags locking Christoph Hellwig
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=20070625164244.GK18198@duck.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).