From: William Lee Irwin III <wli@holomorphy.com>
To: Neil Brown <neilb@cse.unsw.edu.au>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: nfsd oops 2.6.7-rc1
Date: Fri, 28 May 2004 21:47:23 -0700 [thread overview]
Message-ID: <20040529044723.GA2093@holomorphy.com> (raw)
In-Reply-To: <20040529032540.GA1310@holomorphy.com>
On Sat, May 29, 2004 at 01:24:29PM +1000, Neil Brown wrote:
>> Ok, I think I've found it. There is a missing dget. See below/.
>> NeilBrown
On Fri, May 28, 2004 at 08:25:40PM -0700, William Lee Irwin III wrote:
> Thanks! Testing ETA 10-15 minutes (time needed for kernel compiles).
No oopsen for 30 minutes so it's working wonderfully thus far, but I've
seen things go wrong a number of hours out from boot before. I'll try
to follow up with another ack after it's been longer.
-- wli
prev parent reply other threads:[~2004-05-29 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 2:35 nfsd oops 2.6.7-rc1 William Lee Irwin III
2004-05-29 3:24 ` Neil Brown
2004-05-29 3:25 ` William Lee Irwin III
2004-05-29 4:47 ` William Lee Irwin III [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=20040529044723.GA2093@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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