From: Christoph Hellwig <hch@infradead.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20pre5aa1
Date: Thu, 5 Sep 2002 18:09:04 +0100 [thread overview]
Message-ID: <20020905180904.A8406@infradead.org> (raw)
In-Reply-To: <20020905165307.GC1254@dualathlon.random>; from andrea@suse.de on Thu, Sep 05, 2002 at 06:53:07PM +0200
On Thu, Sep 05, 2002 at 06:53:07PM +0200, Andrea Arcangeli wrote:
> btw, even if xfs is applied before the inode_read_write-atomic, please
> make sure xfs will learn using the i_size_read when out of the semaphore
> and i_size_write too. I know the locking is different there but I doubt
> you're just managing the i_size without races.
XFS always has the XFS i_lock around accessing it. Either in read mode
or in write mode for updates (the lock is a so-called mrlock which
basically as a rwsem with a few subtile differences).
Anyway most acceses i_size in the new code are done by the generic
code now as XFS calls it internally. Take a look at the update I sent
you a few seconds ago :)
next prev parent reply other threads:[~2002-09-05 17:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 23:35 2.4.20pre5aa1 Andrea Arcangeli
2002-09-04 23:56 ` 2.4.20pre5aa1 Andrew Morton
2002-09-05 0:25 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 12:44 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 16:53 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 17:09 ` Christoph Hellwig [this message]
2002-09-05 18:41 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 18:46 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:59 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:02 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:13 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:17 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:48 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:06 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:15 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:26 ` 2.4.20pre5aa1 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=20020905180904.A8406@infradead.org \
--to=hch@infradead.org \
--cc=andrea@suse.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.