linux-kernel - Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <2CC45724-FD70-4F00-84F7-4D0E2158D6B5@netapp.com>
Date:	Wed, 22 Jul 2009 18:03:03 -0400
From:	Andy Adamson <andros@...app.com>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	Ben Greear <greearb@...delatech.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-nfs@...r.kernel.org
Subject: Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.


On Jul 22, 2009, at 5:47 PM, Trond Myklebust wrote:

> On Wed, 2009-07-22 at 17:32 -0400, Andy Adamson wrote:
>> nfs4_init_session should simply return if the nfs_client  
>> cl_cons_state
>> is not NFS_CS_SESSION_INITING.
>> I shouldn't be trying to set the session max_resp_sz/max_rqst_sz to
>> the rsize/wsize, but rather to the maximum rsize/wsize supported by
>> the client.
>> If the server accepts or increases the max_resp_sz/max_rqst_sz then
>> all is well.
>> If the server reduces the max_resp_sz/max_rqst_sz, the maximum rsize/
>> wsize available for NFSv4.1 partition mounts to the server needs to  
>> be
>> reduced accordingly. So the nfs_server rsize/wsize needs to be bound
>> by the session max_resp_sz/max_rqst_sz as well as by the maximum
>> supported size.
>
> Well.... The rsize/wsize is one thing, but how about acls? We simply
> don't know how big they may become.

Yeah - has anything been submitted for 4.2 to fix this? (a readdir  
cookie - like thingie)

>
>
> An alternative would be to let the server choose the
> max_rqst_sz/max_resp_sz by always requesting the maximum allowed  
> value.

OK  - maximum allowed value instead of maximum client supported value...

>
> Trond
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/