Linux NFS development
 help / color / mirror / Atom feed
From: Timo Aaltonen <tjaalton@cc.hut.fi>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: Last call for nfs-utils patches
Date: Sat, 8 Mar 2008 20:12:01 +0200 (EET)	[thread overview]
Message-ID: <alpine.OSF.0.99.0803082011110.100983@replicant.hut.fi> (raw)
In-Reply-To: <alpine.OSF.0.99.0803082004371.100983@replicant.hut.fi>

On Sat, 8 Mar 2008, Timo Aaltonen wrote:

> On Tue, 4 Mar 2008, Steve Dickson wrote:
>
>>
>> I'm planning on cutting a nfs-utils-1.1.2 release since
>> there has been a number commits since the last 1.1.1 release.
>>
>> The attached list are all of the commits that have been made to
>> the git://linux-nfs.org/nfs-utils git tree.
>>
>> (Note: to get a working copy of this tree use:
>>    git clone  git://linux-nfs.org/nfs-utils nfs-utils)
>>
>> So if you don't see a commit you have posted to either
>> the nfs or nfsv4 mailing list it probably means I missed it
>> so you might want to bring it to my attention.
>> (Please Note, the patch authors in some of my earlier
>> commit are incorrect. This was simply due to my lack
>> of git knowledge. Once it was pointed it out to me,
>> the problem was corrected.)
>>
>> Also if you were holding off posting some (hopefully)
>> non-intrusive patches now it the time. There is a very
>> good chance I will not cut the release until this weekend.
>
> Here's another patch (by Niall Sheridan) that needs approval:
>
> - - -
>
> rpc.gssd FD_ALLOC_BLOCK too low
>
> The max number of sec=krb5 mounts that rpc.gssd will handle is hardcoded
> at 32. From utils/gssd/gssd.h:
> #define FD_ALLOC_BLOCK 32
>
> This causes problems and errors like:
>  RPC: AUTH_GSS upcall timed out.
> when the number of kerberized nfs mounts approaches the hard limit.
>
> Since linux supports a maximum of 256 nfs mounts, perhaps this number can
> be upped to 200 or so.
>
> http://launchpadlibrarian.net/11961434/nfs-utils-fd-alloc-block.debdiff
>
> - - -
>
> what say you?

Oops, should've checked the git first.. this is fixed by commit 
d15fa02fe38f6f1c9183540810ac7bfeac0c7c17

:)

t

      reply	other threads:[~2008-03-08 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 15:17 Last call for nfs-utils patches Steve Dickson
     [not found] ` <47CD680B.1070106-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-03-04 16:55   ` Steinar H. Gunderson
2008-03-06  7:38 ` Timo Aaltonen
     [not found]   ` <alpine.OSF.0.99.0803060931390.100983-r6D5HDKEOC1C46yoE1Qrng@public.gmane.org>
2008-03-06 14:23     ` Steve Dickson
2008-03-06 22:06       ` Timo Aaltonen
2008-03-08 18:07 ` Timo Aaltonen
2008-03-08 18:12   ` Timo Aaltonen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.OSF.0.99.0803082011110.100983@replicant.hut.fi \
    --to=tjaalton@cc.hut.fi \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox