From: Oleg Drokin <green@namesys.com>
To: Christoph Hellwig <hch@angband.namesys.com>,
marcelo@hera.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backport iget_locked from 2.5/2.6
Date: Tue, 26 Aug 2003 15:27:16 +0400 [thread overview]
Message-ID: <20030826112716.GA14680@namesys.com> (raw)
In-Reply-To: <20030825140714.GA17359@lst.de>
Helllo!
On Mon, Aug 25, 2003 at 04:07:14PM +0200, Christoph Hellwig wrote:
> Provide an iget variant without unlocking the inode and ->read_inode
> call. This is needed for XFS and IIRC the reiserfs folks wanted it,
> too.
No. This patch is useless for our purposes. (and coda/nfs ).
We wanted to get rid of a race where inode allocation and
filling fs specific parts are done non-atomically.
The patch below does not achieve this. We still fill inode private part
outside of inode_lock locked region.
Bye,
Oleg
next prev parent reply other threads:[~2003-08-26 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 14:07 [PATCH] backport iget_locked from 2.5/2.6 Christoph Hellwig
2003-08-26 11:27 ` Oleg Drokin [this message]
2003-08-26 13:48 ` Christoph Hellwig
2003-08-26 13:54 ` Oleg Drokin
2003-08-26 14:30 ` Christoph Hellwig
2003-08-26 14:35 ` Oleg Drokin
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=20030826112716.GA14680@namesys.com \
--to=green@namesys.com \
--cc=hch@angband.namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@hera.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