From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Steinar H. Gunderson"
<sgunderson-jG/AHqQBv7lBDgjK7y7TUQ@public.gmane.org>,
linux-nfs@vger.kernel.org
Subject: Re: Text-based mount interface breaking non-UDP mounts
Date: Mon, 05 May 2008 08:34:46 -0400 [thread overview]
Message-ID: <481EFEE6.4040800@RedHat.com> (raw)
In-Reply-To: <EBC0B2E8-66BB-4692-8BF2-553804F6FA36@oracle.com>
Chuck Lever wrote:
> On Apr 25, 2008, at 7:55 PM, Steinar H. Gunderson wrote:
>> 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.
>
>
> FYI: Steve Dickson (nfs-utils maintainer) is already looking at removing
> EACCES from the list of temporary errors, so yes, we're aware of that
> issue.
Actually it has been removed already...
steved.
next prev parent reply other threads:[~2008-05-05 12:39 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
[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 [this message]
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=481EFEE6.4040800@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sgunderson-jG/AHqQBv7lBDgjK7y7TUQ@public.gmane.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