From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: oops in rpc_pipe_release
Date: Tue, 08 Nov 2005 15:51:33 -0500 [thread overview]
Message-ID: <43710FD5.8080306@RedHat.com> (raw)
In-Reply-To: <1131479893.32482.45.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>
> I'd rather like to find out how this is happening, and fix the root
> cause. Your patch seems like a bit too much of a band-aid.
Yeah I know its a hack.... I just wanted to make sure it address
the root cause of Vince's problem... Unfortunately I'm a bit
under the gun w.r.t, to deadlines... and an oops is an oops...
so I might have to go with it...
>
> My point is that we should never want to find ourselves in the situation
> that the directory is being cleared without the auth code having first
> cleaned up and deleted its pipes.
Well here is how you should be able to reproduce it
as spelled out in bz 171112:
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171112)
root# mount -o krb5 server:/export /mnt
user$ cd /mnt
root# /bin/service nets stop
root# /bin/service rpcidmapd stop
root# kill -9 $(pgrep -u <user>)
steved.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-11-08 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 0:04 oops in rpc_pipe_release Vince Busam
2005-11-08 0:10 ` J. Bruce Fields
2005-11-08 14:23 ` Steve Dickson
2005-11-08 18:37 ` Vince Busam
2005-11-08 18:58 ` Steve Dickson
2005-11-08 19:58 ` Trond Myklebust
2005-11-08 20:51 ` Steve Dickson [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=43710FD5.8080306@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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