From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Dave Chinner <david@fromorbit.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Mikulas Patocka <mpatocka@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux-next: build failure after merge of the vfs tree
Date: Wed, 4 Jan 2012 13:47:46 -0500 [thread overview]
Message-ID: <20120104184746.GA8461@infradead.org> (raw)
In-Reply-To: <20120104180033.GE28907@quack.suse.cz>
On Wed, Jan 04, 2012 at 07:00:33PM +0100, Jan Kara wrote:
> On Wed 04-01-12 13:50:20, Dave Chinner wrote:
> > On Wed, Jan 04, 2012 at 02:17:54AM +0000, Al Viro wrote:
> > > I'm still not
> > > sure about ->statfs(), BTW - any input on that would be welcome. Can
> > > it end up blocked on a frozen fs until said fs is thawed?
> >
> > I don't see why this should ever happen - ->statfs has to work on
> > read-only filesystems so shoul dnot be modifying state, and hence
> > should never need to care about the frozen state of the superblock.
> Well, I'm also not aware of a filesystem where ->statfs would wait on
> frozen filesystem. Just note that e.g. for stat(2) frozen filesystem and
> RO filesystem *are* different because of atime updates. So stat(2) can
> block on frozen fs because of atime update while on RO filesystem it is
> just fine.
Neither of those should cause atime updates.
next prev parent reply other threads:[~2012-01-04 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120103124331.f0f0043f8ca464c9ff13f4d3@canb.auug.org.au>
[not found] ` <20120103133942.GC31457@quack.suse.cz>
2012-01-03 14:45 ` linux-next: build failure after merge of the vfs tree Al Viro
2012-01-04 2:17 ` Al Viro
2012-01-04 2:50 ` Dave Chinner
2012-01-04 18:00 ` Jan Kara
2012-01-04 18:47 ` Christoph Hellwig [this message]
2012-01-04 22:26 ` Jan Kara
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=20120104184746.GA8461@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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).