From: Benny Halevy <bhalevy@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: pnfs mailing list <pnfs@linux-nfs.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] NFSD: fix handling of unsupported nfsv4 ops
Date: Wed, 04 Mar 2009 23:11:55 +0200 [thread overview]
Message-ID: <49AEEE9B.2040507@panasas.com> (raw)
In-Reply-To: <20090304210200.GG28951@fieldses.org>
On Mar. 04, 2009, 23:02 +0200, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Thu, Feb 26, 2009 at 12:37:22PM -0800, Benny Halevy wrote:
>> Both patches fix issues I introduced in 2.6.27.
>> The first one is more crucial to get to the 2.6.2{7,8} stable streams
>> but while at it, I'd pull both.
>> This was triggered in connectathon with the Sun OpenSolaris
>> client trying to read extended attrs (when copying a file).
>> This translates to a NFS4 OP_OPENATTR which caused our server to barf.
>
> Thanks! But, sorry, somehow I didn't get both of these (probably a
> screwup on my end); would you mind resending?
Just did.
>
> Also, have you checked to make sure there aren't any other holes in our
> list of operations?
Yup. OPENATTR was the only hole I found.
Benny
>
> --b.
>
>> [PATCH 1/2] NFSD: provide encode routine for OP_OPENATTR
>> [PATCH 2/2] NFSD: return nfsv4 error code nfserr_notsupp rather than nfsv[23]'s nfserr_opnotsupp
>>
>> Benny
next prev parent reply other threads:[~2009-03-04 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 20:37 [PATCH 0/2] NFSD: fix handling of unsupported nfsv4 ops Benny Halevy
2009-03-04 21:02 ` J. Bruce Fields
2009-03-04 21:11 ` Benny Halevy [this message]
2009-03-06 20:36 ` J. Bruce Fields
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=49AEEE9B.2040507@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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