From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dave Jones <davej@redhat.com>
Cc: Stresslinux Kernel <lk@stresslinux.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.20.2: kernel BUG at fs/nfs/write.c:505!
Date: Mon, 12 Mar 2007 13:17:57 -0400 [thread overview]
Message-ID: <1173719877.6436.40.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20070312171324.GC22223@redhat.com>
On Mon, 2007-03-12 at 13:13 -0400, Dave Jones wrote:
> On Mon, Mar 12, 2007 at 01:00:31PM -0400, Trond Myklebust wrote:
>
> > > Code: 0f 0b eb fe f0 ff 41 44 c7 85 18 01 00 00 01 00 00 00 48 8b
> > > RIP [<ffffffff8032fb83>] nfs_wait_on_requests_locked+0x43/0xb2
> > > RSP <ffff81007d669ca8>
> >
> > Known issue. There is already a fix available in the -mm kernel
> > (attached).
>
> Did this get sent to -stable too for .20.3 ?
Sorry, no. It is not even in mainline yet. I've been travelling a bit
too much recently.
Cheers
Trond
prev parent reply other threads:[~2007-03-12 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 13:39 2.6.20.2: kernel BUG at fs/nfs/write.c:505! Stresslinux Kernel
2007-03-12 17:00 ` Trond Myklebust
2007-03-12 17:13 ` Dave Jones
2007-03-12 17:17 ` Trond Myklebust [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=1173719877.6436.40.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@stresslinux.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