From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NLM: Revert parts of commit 24e36663
Date: Fri, 26 Sep 2008 14:45:54 -0400 [thread overview]
Message-ID: <20080926184554.GA1492@fieldses.org> (raw)
In-Reply-To: <AED0D581-07B0-4EC6-90AB-2F61B6F3C76B@oracle.com>
On Fri, Sep 26, 2008 at 01:53:58PM -0400, Chuck Lever wrote:
> On Sep 25, 2008, at Sep 25, 2008, 5:38 PM, J. Bruce Fields wrote:
>> On Wed, Sep 24, 2008 at 02:50:36PM -0400, Chuck Lever wrote:
>>> statd and some servers always need lockd to listen on UDP, so always
>>> start both lockd listener sockets.
>>>
>>> This probably leaks an svc_serv if the TCP listener can't be created,
>>> but it will do for now.
>>>
>>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>>> ---
>>>
>>> I currently have this workaround lurking in my git repo. Is there
>>> some kind
>>> of fix for this issue planned for 2.6.28?
>>
>> Not that I know of.
>>
>>> This is only a reminder, not a suggested patch.
>>
>> Any chance you could generate a patch?
>
> I can, but no guarantee it will be in time for the 2.6.28 merge window.
>
> Would we consider this a regression fix?
I suppose so. (Are there any bug reports? If so, could we get URL's
for them into the commit message?)
> If so, we could post it after
> the merge window closes. It would give a little more time to do some
> testing.
That sound suspiciously like "since this is a high priority, it will be
accepted later, so we can make it a lower priority." Help!
But anyway, yes, we might have more time.
--b.
next prev parent reply other threads:[~2008-09-26 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 18:50 [PATCH] NLM: Revert parts of commit 24e36663 Chuck Lever
[not found] ` <20080924184732.4078.83334.stgit-lQeC5l55kZ7wdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-24 18:54 ` Trond Myklebust
2008-09-26 15:50 ` Talpey, Thomas
2008-09-25 21:38 ` J. Bruce Fields
2008-09-26 17:53 ` Chuck Lever
2008-09-26 18:45 ` J. Bruce Fields [this message]
2008-09-26 18:49 ` Trond Myklebust
2008-09-26 18:51 ` J. Bruce Fields
2008-09-26 19:04 ` Chuck Lever
2008-09-26 19:11 ` Trond Myklebust
2008-09-26 19:44 ` J. Bruce Fields
2008-09-26 19:54 ` Chuck Lever
2008-09-26 19:57 ` Trond Myklebust
2008-09-26 21:11 ` Chuck Lever
2008-09-26 22:22 ` Trond Myklebust
2008-09-26 23:30 ` J. Bruce Fields
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=20080926184554.GA1492@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.com \
/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