From: viro@parcelfarce.linux.theplanet.co.uk
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Nikita Danilov <Nikita@Namesys.COM>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
trond myklebust <trondmy@trondhjem.org>
Subject: Re: d_splice_alias() problem.
Date: Tue, 4 May 2004 10:46:42 +0100 [thread overview]
Message-ID: <20040504094642.GL17014@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <40973F7F.A9FA4F1@melbourne.sgi.com>
On Tue, May 04, 2004 at 05:00:15PM +1000, Greg Banks wrote:
> Ok, how about this...it's portable, and not racy, but may perturb the
> logic slightly by also taking dentries off the unused list in the case
> where they already had d_count>=1. I'm not sure how significant that is.
> In any case this also passes my tests.
a) ask RCU folks to review - the current logics in dcache.c is extremely
brittle as it is.
b) after rereading that code, I _really_ don't like the crap with "hashed
but disconnected" nfsd is pulling off. Neil, care to give detailed reasons
why you are doing that?
next prev parent reply other threads:[~2004-05-04 9:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 13:02 d_splice_alias() problem Nikita Danilov
2004-04-23 15:40 ` Andreas Dilger
2004-04-23 16:20 ` Nikita Danilov
2004-04-23 23:49 ` Andrew Morton
2004-04-26 12:45 ` Nikita Danilov
2004-04-30 4:54 ` Neil Brown
2004-04-30 7:50 ` Greg Banks
2004-04-30 13:28 ` Nikita Danilov
2004-05-03 23:46 ` Neil Brown
2004-05-03 12:02 ` Greg Banks
2004-05-03 23:28 ` Neil Brown
2004-05-04 0:05 ` Greg Banks
2004-05-04 7:00 ` Greg Banks
2004-05-04 9:46 ` viro [this message]
2004-05-04 10:21 ` Greg Banks
2004-05-05 0:11 ` Neil Brown
2004-05-10 3:03 ` Neil Brown
2004-05-10 4:50 ` Greg Banks
2004-05-10 3:27 ` Neil Brown
2004-05-10 11:28 ` Greg Banks
2004-05-13 5:58 ` Neil Brown
2004-05-13 7:15 ` Greg Banks
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=20040504094642.GL17014@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=Nikita@Namesys.COM \
--cc=gnb@melbourne.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=trondmy@trondhjem.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