linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: cel@citi.umich.edu
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: [Fwd: [Fwd: Re: 2.6.13-mm2]]]
Date: Thu, 22 Sep 2005 17:57:48 -0400	[thread overview]
Message-ID: <1127426268.8365.174.camel@lade.trondhjem.org> (raw)
In-Reply-To: <43330970.9030006@citi.umich.edu>

to den 22.09.2005 Klokka 15:43 (-0400) skreiv Chuck Lever:
> attached please find the original message containing the pmap reserved 
> port patch.

There's just one problem: it won't apply to my tree. Looks like this is
relative to something you haven't merged yet.

Cheers,
  Trond

> e-postmelding vedlegg ([Fwd: [Fwd: Re: 2.6.13-mm2]])
> to den 22.09.2005 Klokka 15:43 (-0400) skreiv Chuck Lever:
> > andrew-
> > 
> > please replace the one-liner that adds "xprt->resvport = 0;" to 
> > net/sunrpc/clnt.c with the attached patch.
> > 
> > i haven't heard confirmation from dominik on this, but trond and i 
> > suspect this is a reasonable replacement for the original patch.
> > e-postmelding vedlegg ([Fwd: Re: 2.6.13-mm2])
> > to den 22.09.2005 Klokka 15:43 (-0400) skreiv Chuck Lever:
> > > Looks like one of your patches...
> > > e-postmelding vedlegg, "Vidaresendt melding - Re: 2.6.13-mm2"
> > > to den 22.09.2005 Klokka 15:43 (-0400) skreiv Chuck Lever:
> > > > Dominik Karall <dominik.karall@gmx.net> wrote:
> > > > >
> > > > > On Thursday 08 September 2005 14:30, Andrew Morton wrote:
> > > > >  > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13
> > > > >  >-mm2/
> > > > > 
> > > > >  I have problems using NFS with 2.6.13-mm2, it failes to start, but works with 
> > > > >  2.6.13-ck1 (so pure 2.6.13 should work too, as there are no nfs related 
> > > > >  changes in -ck, I think).
> > > > >  Following messages appear in /var/log/messages:
> > > > > 
> > > > >  Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > > > >  rpc.statd[15041]: Version 1.0.7 Starting
> > > > >  NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> > > > >  NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
> > > > >  NFSD: starting 90-second grace period
> > > > >  portmap[15048]: connect from 127.0.0.1 to set(nfs): request from unprivileged 
> > > > >  port
> > > > >  nfsd[15046]: nfssvc: Permission denied
> > > > > 
> > > > > 
> > > > >  with 2.6.13-ck1:
> > > > > 
> > > > >  Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > > > >  rpc.statd[16126]: Version 1.0.7 Starting
> > > > >  NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> > > > >  NFSD: starting 90-second grace period
> > > > 
> > > > OK.  We don't have many nfsd patches at all in 2.6.13-mm2.  But there are
> > > > quite a few sunrpc changes.  Plus I have a few random nfs patches which
> > > > should be merged up or dropped.
> > > > 
> > > > In short: dunno.  Relevant people cc'ed ;)


  reply	other threads:[~2005-09-22 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 19:43 [Fwd: [Fwd: [Fwd: Re: 2.6.13-mm2]]] Chuck Lever
2005-09-22 21:57 ` Trond Myklebust [this message]
2005-09-23  1:24   ` Chuck Lever

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=1127426268.8365.174.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=akpm@osdl.org \
    --cc=cel@citi.umich.edu \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).