[nfsv4] OPEN_DOWNGRADE and posix byte range locking issue
Trond Myklebust <Trond.Myklebust@netapp.com> Wed, 07 July 2010 23:31 UTC
Return-Path: <Trond.Myklebust@netapp.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C8EE3A6918 for <nfsv4@core3.amsl.com>; Wed, 7 Jul 2010 16:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQ9I9FbNkH8X for <nfsv4@core3.amsl.com>; Wed, 7 Jul 2010 16:31:10 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id CF60C3A68FB for <nfsv4@ietf.org>; Wed, 7 Jul 2010 16:31:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,555,1272870000"; d="scan'208";a="397569543"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 07 Jul 2010 16:30:50 -0700
Received: from svlrsexc2-prd.hq.netapp.com (svlrsexc2-prd.hq.netapp.com [10.57.115.31]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o67NUnTs022040 for <nfsv4@ietf.org>; Wed, 7 Jul 2010 16:30:50 -0700 (PDT)
Received: from SACMVEXC2-PRD.hq.netapp.com ([10.99.115.18]) by svlrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Jul 2010 16:30:50 -0700
Received: from 10.58.60.215 ([10.58.60.215]) by SACMVEXC2-PRD.hq.netapp.com ([10.99.115.16]) with Microsoft Exchange Server HTTP-DAV ; Wed, 7 Jul 2010 23:30:23 +0000
Received: from heimdal.trondhjem.org by SACMVEXC2-PRD.hq.netapp.com; 07 Jul 2010 19:30:23 -0400
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: nfsv4@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Organization: NetApp
Date: Wed, 07 Jul 2010 19:30:23 -0400
Message-ID: <1278545423.15524.26.camel@heimdal.trondhjem.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.2 (2.30.2-1.fc13)
X-OriginalArrivalTime: 07 Jul 2010 23:30:50.0446 (UTC) FILETIME=[6F463EE0:01CB1E2C]
Subject: [nfsv4] OPEN_DOWNGRADE and posix byte range locking issue
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 23:31:12 -0000
Neither RFC3530, nor RFC5661 appear to list NFS4ERR_LOCKS_HELD as a valid response when the client calls OPEN_DOWNGRADE. The question is: what should the server then do if the NFS client holds a WRITE_LT lock, but then asks for an OPEN_DOWNGRADE to OPEN4_SHARE_ACCESS_READ. I understand that this is sanctioned in Windows server environments, but it should definitely be forbidden in a POSIX environment, and NFS4ERR_LOCKS_HELD would appear to fit the bill... Trond
- [nfsv4] OPEN_DOWNGRADE and posix byte range locki… Trond Myklebust
- Re: [nfsv4] OPEN_DOWNGRADE and posix byte range l… Noveck_David
- Re: [nfsv4] OPEN_DOWNGRADE and posix byte range l… Trond Myklebust
- Re: [nfsv4] OPEN_DOWNGRADE and posix byte range l… J. Bruce Fields
- Re: [nfsv4] OPEN_DOWNGRADE and posix byte range l… david.noveck
- Re: [nfsv4] OPEN_DOWNGRADE and posix byte range l… J. Bruce Fields