From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: tridge@samba.org, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>,
Neil Brown <neilb@cse.unsw.edu.au>, Andrew Morton <akpm@osdl.org>
Subject: Re: make -j4 gets stuck w/ ccache over NFS - solved!
Date: Thu, 10 Mar 2005 11:24:35 -0500 [thread overview]
Message-ID: <20050310162435.GE12787@fieldses.org> (raw)
In-Reply-To: <20050310054737.GA27656@jupiter.solarsys.private>
On Thu, Mar 10, 2005 at 12:47:37AM -0500, Mark M. Hoffman wrote:
> Thanks for the suggestions. It wasn't very important to me so I didn't
> make time to follow up on it. I was just playing w/ ccache at the time.
>
> Finally I noticed this patch from -mm1... and it solves the problem.
>
> nfsd--lockd-dont-try-to-match-callback-requests-against-export-table.patch
>
> How I tested: I applied the first 12 patches in 2.6.11-mm1; the above
> mentioned was last - couldn't reproduce the bug. When I unapplied just
> that one, I saw it again.
>
> original bug report:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=110238645132535&w=3
>
> Greg: have you considered this one for 2.6.11.x?
That patch depends on 3 of the previous 4 patches. Taken together I
doubt they meet the criteria for 2.6.11.x.
It's probably possible to write a shorter and more obvious one-off fix
just for that tree, but I'm not sure it's worth it for a bug that, while
it's obviously extremely annoying for some workloads, doesn't quite
reach the level of, say, a root exploit.
--b.
next prev parent reply other threads:[~2005-03-10 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 2:24 make -j4 gets stuck w/ ccache over NFS Mark M. Hoffman
2004-12-07 6:22 ` Martin Pool
2004-12-08 7:25 ` tridge
2005-03-10 5:47 ` make -j4 gets stuck w/ ccache over NFS - solved! Mark M. Hoffman
2005-03-10 16:24 ` J. Bruce Fields [this message]
2005-03-10 17:11 ` Greg KH
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=20050310162435.GE12787@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhoffman@lightlink.com \
--cc=neilb@cse.unsw.edu.au \
--cc=tridge@samba.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.