From: Jeff Garzik <jeff@garzik.org>
To: Daniel J Blueman <daniel.blueman@gmail.com>,
Andrew Morton <akpm@osdl.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
nfsv4@linux-nfs.org, Neil Brown <neilb@suse.de>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Fwd: [PATCH 2/2] nfsd4: fix open-create permissions
Date: Wed, 08 Nov 2006 08:33:50 -0500 [thread overview]
Message-ID: <4551DCBE.1060508@garzik.org> (raw)
In-Reply-To: <6278d2220611060848n3585ebc5odbf39efd6a02ab2@mail.gmail.com>
Daniel J Blueman wrote:
> Linus, Trond,
>
> What is the chance of this patch making it into the final 2.6.19?
>
> WIthout it, there is a serious NFSv4 open() regression; I've been
> running it on client and server for ~1 week under load and it resolves
> the condition w/o side-effects. See the LKML thread "Poor NFSv4 first
> impressions" for further details.
strong ACK, provided that someone who knows the NFSv4 server code well
(Neil B?) gives it an ACK.
Jeff
next prev parent reply other threads:[~2006-11-08 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 12:03 Poor NFSv4 first impressions Daniel J Blueman
2006-11-06 16:07 ` Bill Davidsen
2006-11-06 16:17 ` J. Bruce Fields
2006-11-06 16:23 ` [PATCH 0/1] nfsd4: reindent do_open_lookup() J. Bruce Fields
2006-11-06 16:26 ` J. Bruce Fields
2006-11-06 16:24 ` [PATCH 2/2] nfsd4: fix open-create permissions J. Bruce Fields
2006-11-06 16:48 ` Fwd: " Daniel J Blueman
2006-11-08 13:33 ` Jeff Garzik [this message]
2006-11-08 18:04 ` Andrew Morton
2006-11-07 7:20 ` Poor NFSv4 first impressions Pavel Machek
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=4551DCBE.1060508@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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.