From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH][RFC] inode->u.nfs_i allocated separately
Date: Fri, 22 Jun 2001 14:27:39 +0200 [thread overview]
Message-ID: <15155.14779.124958.686172@charged.uio.no> (raw)
In-Reply-To: <Pine.GSO.4.21.0106220234370.1959-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0106220234370.1959-100000@weyl.math.psu.edu>
>>>>> " " == Alexander Viro <viro@math.psu.edu> writes:
> Trond, could you review the patch below? I believe that it's
> OK
> wrt races around iget(), but I'd appreciate if you take a look
> at it.
It certainly doesn't suffer from the problem I raised last time, so at
first glance, I'd say it's OK. I'll see if I can't dig up some dirt on
it over the weekend though ;-).
Cheers,
Trond
parent reply other threads:[~2001-06-22 12:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.GSO.4.21.0106220234370.1959-100000@weyl.math.psu.edu>]
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=15155.14779.124958.686172@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®