From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steve French" Subject: Re: mount options for selectively disabling parts of CIFS Unix Extensions Date: Mon, 16 Jul 2007 18:11:02 -0500 Message-ID: <524f69650707161611r4e29273cn751ffce503bd2d49@mail.gmail.com> References: <524f69650707161540n4f4e785ai6c6039d3240456f9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: linux-cifs-client@lists.samba.org, samba-technical@lists.samba.org, linux-fsdevel@vger.kernel.org Return-path: Received: from py-out-1112.google.com ([64.233.166.183]:35543 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751783AbXGPXLD (ORCPT ); Mon, 16 Jul 2007 19:11:03 -0400 Received: by py-out-1112.google.com with SMTP id d32so2583250pye for ; Mon, 16 Jul 2007 16:11:02 -0700 (PDT) In-Reply-To: <524f69650707161540n4f4e785ai6c6039d3240456f9@mail.gmail.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I would like opinions on how to handle a specific use question ... if the user has mounted e.g. \\server1\shareA (e.g. on a Samba server) using defaults (and thus gotten support for the Unix Extensions, but then does a second mount trying to disable Unix Extensions (e.g. "mount -t cifs //server1/shareB /mnt -o nounix" then what should the result be: 1) mount fails? If so what return code - there is no easy way to pass error strings back across mount (get_sb returns an int - a posix return code) 2) mount succeeds, ignoring the "nounix" option but prints a warning to dmesg 3) mount succeeds but turns off the Unix Capability bits so no Unix Extension requests are sent on either shareA or shareB (although the server behavior will still be a little different than if the client had not negotiated Unix Extensions at all, at least it will be different unless the session drops and is reconnected at which time the server will see the Unix Extensions disabled) 4) mount succeeds and no Unix Extension requests are sent on the tree id for shareB (the requests to shareA are unaffected) etc. Ideas? On 7/16/07, Steve French wrote: > I have seen various requests from users to disable part of the CIFS > Unix Extensions on mount