From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265524AbTFRUnX (ORCPT ); Wed, 18 Jun 2003 16:43:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265525AbTFRUnX (ORCPT ); Wed, 18 Jun 2003 16:43:23 -0400 Received: from ns.suse.de ([213.95.15.193]:34060 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S265524AbTFRUnW (ORCPT ); Wed, 18 Jun 2003 16:43:22 -0400 Date: Wed, 18 Jun 2003 22:57:19 +0200 From: Andi Kleen To: Bruce Allan Cc: trond.myklebust@fys.uio.no, Andi Kleen , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Support non reserved ports for NFS client Message-ID: <20030618205719.GA3543@wotan.suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 18, 2003 at 01:07:05PM -0700, Bruce Allan wrote: > May I make the suggestion that instead of creating a new flag (i.e. > NFS_MOUNT_NONRESERVED) and using a new bit in the flags field of struct > nfs_mount_data, Andi use the already existing and unused NFS_MOUNT_SECURE > assuming that is what was originally intended for this bit. This would > also match in name with the secure/insecure export option on the server. Makes sense yes. Thanks for the suggestion. -Andi