From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jonathan Couper <jonathan-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Mutex Hang on GC in lockd for 2.6.22-14
Date: Mon, 21 Jan 2008 16:03:57 -0500 [thread overview]
Message-ID: <20080121210357.GP17468@fieldses.org> (raw)
In-Reply-To: <47950544.2080205-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
On Tue, Jan 22, 2008 at 09:49:08AM +1300, Jonathan Couper wrote:
> Heya,
>
> What's the path for that getting rolled back into the 2.6.22 chain? In
> generally I'm happy with my 2.6.22 kernel. Is Jeff submitting those
> fixes to the 2.6.22 release at some stage, do you know?
There appear to be two separate problems here with two fixes:
- the possibility of multiple lockd's at once, fixed by Jeff's
patches.
- the double-lock problem, fixed by Trond's two patches.
It sounds like the latter may actually be what you're more in need of?
They're probably easier to backport in any case.
I don't know if those are in 2.6.22, or if 2.6.22 is still open. I'd
add pointers to those two patches to the bugzilla report for the ubuntu
people to look at.
--b.
prev parent reply other threads:[~2008-01-21 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <479427C5.8020203@spiderfan.org>
[not found] ` <18324.11227.8442.938224@notabene.brown>
[not found] ` <18324.11227.8442.938224-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-01-21 5:24 ` Mutex Hang on GC in lockd for 2.6.22-14 Jonathan Couper
[not found] ` <47942CA4.1060700-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
2008-01-21 18:31 ` J. Bruce Fields
2008-01-21 20:49 ` Jonathan Couper
[not found] ` <47950544.2080205-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
2008-01-21 21:03 ` J. Bruce Fields [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=20080121210357.GP17468@fieldses.org \
--to=bfields@fieldses.org \
--cc=jonathan-3c88B9b11vOEi8DpZVb4nw@public.gmane.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox