All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson-jG/AHqQBv7lBDgjK7y7TUQ@public.gmane.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Text-based mount interface breaking non-UDP mounts
Date: Sat, 26 Apr 2008 01:55:46 +0200	[thread overview]
Message-ID: <20080425235546.GA9053@uio.no> (raw)
In-Reply-To: <4D5FA350-EED5-4204-8D70-E3BE5E400595@oracle.com>

On Fri, Apr 25, 2008 at 06:13:03PM -0400, Chuck Lever wrote:
> I just tried this specific use case.
>
> Because of the local packet filtering on the client, the kernel's RPC  
> client is getting -EPERM when trying to send the initial rpcbind  
> request.
>
> As far as I can see, nothing in the RPC client knows how to deal  
> specifically with that error code, so it punts the request, and the  
> mount fails.
>
> When I originally tested mount protocol/version negotiation, I used only 
> server-side filtering.

I checked the original bug report, and indeed it seems that the blocking was
on the client there as well. I'll ask the user to check what happens when the
filtering is done server-side instead.

There's also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476128, but I
believe that's a different bug.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

  reply	other threads:[~2008-04-25 23:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 21:49 Text-based mount interface breaking non-UDP mounts Steinar H. Gunderson
     [not found] ` <20080423214929.GA24387-6Z/AllhyZU4@public.gmane.org>
2008-04-24 14:12   ` Chuck Lever
2008-04-25  8:01     ` Steinar H. Gunderson
     [not found]       ` <20080425080128.GA4848-6Z/AllhyZU4@public.gmane.org>
2008-04-25 14:19         ` Chuck Lever
2008-04-25 14:27           ` Steinar H. Gunderson
     [not found]             ` <20080425142712.GA6119-6Z/AllhyZU4@public.gmane.org>
2008-04-25 22:13               ` Chuck Lever
2008-04-25 23:55                 ` Steinar H. Gunderson [this message]
     [not found]                   ` <20080425235546.GA9053-6Z/AllhyZU4@public.gmane.org>
2008-04-25 23:57                     ` Steinar H. Gunderson
     [not found]                       ` <20080425235713.GA9109-6Z/AllhyZU4@public.gmane.org>
2008-04-28 15:28                         ` Chuck Lever
2008-04-28 21:11                           ` Chuck Lever
2008-04-28 15:16                     ` Chuck Lever
2008-05-05 12:34                       ` Steve Dickson
2008-04-26 15:23   ` Frank A. Kingswood
     [not found]     ` <481348E4.3000003-YzJE6wl5KmBjuoFY8sQqqY5Lr7LD32fptUK59QYPAWc@public.gmane.org>
2008-04-26 15:29       ` Frank A. Kingswood
2008-04-26 15:38   ` Frank A. Kingswood
     [not found]     ` <48134C77.9090700-YzJE6wl5KmBjuoFY8sQqqY5Lr7LD32fptUK59QYPAWc@public.gmane.org>
2008-04-28 15:13       ` Chuck Lever
2008-04-28 18:24         ` Frank A. Kingswood
     [not found]           ` <48161671.2070508-YzJE6wl5KmBjuoFY8sQqqY5Lr7LD32fptUK59QYPAWc@public.gmane.org>
2008-04-28 18:44             ` Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2008-05-04 22:39 vincent
     [not found] ` <20080504223934.GA11746-CCKDRK/Hd0cdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2008-05-05  4:20   ` Frank A. Kingswood
2008-05-05 14:13   ` 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=20080425235546.GA9053@uio.no \
    --to=sgunderson-jg/ahqqbv7lbdgjk7y7tuq@public.gmane.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.