From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@digeo.com>
Cc: Daniel McNeil <daniel@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.68 2/2] i_size atomic access
Date: Fri, 25 Apr 2003 03:42:08 +0200 [thread overview]
Message-ID: <20030425014208.GC26194@dualathlon.random> (raw)
In-Reply-To: <20030424180503.2c2a8bea.akpm@digeo.com>
On Thu, Apr 24, 2003 at 06:05:03PM -0700, Andrew Morton wrote:
> And if the race _does_ hit, what is the effect? Assuming stat() was fixed
> with i_sem, I don't think the race has a very serious effect. We won't
writepage needs it too to avoid returning -EIO and I doubt you want to
take the i_sem in writepage
readpage is another obvious candidate where taking the i_sem is not an
option (even if it's one not risking to lose info in the fs, but it can
lose info in userspace or generate a malfunction).
Andrea
next prev parent reply other threads:[~2003-04-25 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:30 [PATCH 2.5.68 2/2] i_size atomic access Daniel McNeil
2003-04-25 1:05 ` Andrew Morton
2003-04-25 1:42 ` Andrea Arcangeli [this message]
2003-04-25 10:57 ` Andrew Morton
2003-04-25 23:17 ` Daniel McNeil
2003-04-30 0:40 ` Daniel McNeil
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=20030425014208.GC26194@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@digeo.com \
--cc=daniel@osdl.org \
--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 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).