From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: i_flags locking
Date: Sat, 30 Jun 2007 10:30:24 +0100 [thread overview]
Message-ID: <20070630093024.GB22354@infradead.org> (raw)
In-Reply-To: <20070625164244.GK18198@duck.suse.cz>
On Mon, Jun 25, 2007 at 06:42:44PM +0200, Jan Kara wrote:
> 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...
i_lock?
prev parent reply other threads:[~2007-06-30 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 16:42 i_flags locking Jan Kara
2007-06-30 9:30 ` Christoph Hellwig [this message]
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=20070630093024.GB22354@infradead.org \
--to=hch@infradead.org \
--cc=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).