From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754316AbWLRRXO (ORCPT ); Mon, 18 Dec 2006 12:23:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754317AbWLRRXO (ORCPT ); Mon, 18 Dec 2006 12:23:14 -0500 Received: from paperclip.laurelnetworks.com ([63.94.127.69]:35197 "EHLO paperclip.laurelnetworks.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754316AbWLRRXN (ORCPT ); Mon, 18 Dec 2006 12:23:13 -0500 Message-ID: <4586CE7F.8060701@laurelnetworks.com> Date: Mon, 18 Dec 2006 12:23:11 -0500 From: Mike Accetta User-Agent: Thunderbird 1.5.0.8 (X11/20061107) MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Re: Change in multiple NFS mount behavior in 2.6.19? References: <45837A24.9040207@laurelnetworks.com> <31861.20061215212835.447659c8.randy.dunlap@oracle.com> In-Reply-To: <31861.20061215212835.447659c8.randy.dunlap@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Randy Dunlap wrote: > On Fri, 15 Dec 2006 23:46:28 -0500 Mike Accetta wrote: > >> After upgrading an NFS client from 2.6.18 to 2.6.19 (and also with >> 2.6.19.1) we see a change in behavior of multiple NFS mounts against the >> same server (running 2.4.20 in this case). With 2.6.18 we could mount >> different pieces of the same remote file system with distinct read-only >> and read-write attributes at corresponding places on the client. With >> 2.6.19 if the first mount is read-only, subsequent mounts seem to >> inherit the read-only status even though not explicitly mounted read-only. >> >> If I did the "git bisect" properly, the behavior changed with commit >> 54ceac4515986030c2502960be620198dd8fe25b and the description of this >> commit seems like it could indeed have caused this behavior, but perhaps >> not intentionally. I believe the client is making NFS V2 calls. Also, I >> am still able to issue a "mount -o remount,rw" on the client to regain >> read-write capability. Was this a regression or is this now the >> expected behavior for multiple NFS client mounts in 2.6.19? >> -- > > That would correspond to this bugzilla item, which explains > that multiple mount semantics for one filesystem are all shared. > > http://bugzilla.kernel.org/show_bug.cgi?id=7655 OK. I didn't think to search bugzilla as I hadn't seen anything go by on the list. Since this is now the expected behavior, I'll have to think about how to re-architect things. Thanks for the pointer. -- Mike Accetta ECI Telecom Ltd. Data Networking Division (previously Laurel Networks)