From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Holger Kiehl <Holger.Kiehl-ra7Ruw+Xvfw@public.gmane.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: NFS write OOPS with 2.6.29.2
Date: Sun, 10 May 2009 00:17:54 -0400 [thread overview]
Message-ID: <1241929074.5149.1.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0905091913010.3181-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Sat, 2009-05-09 at 19:16 +0000, Holger Kiehl wrote:
> On Mon, 4 May 2009, Andrew Morton wrote:
>
> >
> > (cc linux-nfs)
> >
> > On Sun, 3 May 2009 16:03:38 +0000 (GMT) Holger Kiehl <Holger.Kiehl-ra7Ruw+Xvfw@public.gmane.org> wrote:
> >
> >> Hello
> >>
> >> With plain kernel 2.6.29.2 I get the following OOPS (several of them) when
> >> writing lots of small files on the client system:
> >>
> >> May 3 18:48:34 obelix kernel: ------------[ cut here ]------------
> >> May 3 18:48:34 obelix kernel: kernel BUG at fs/nfs/write.c:252!
> >
> > I think this is a well-know bug, and fixes should be available in 2.6.29.3?
> >
> Thanks for this information. I just tried 2.6.29.3 and it still oopses.
> Are there any patches I can try?
The attached backports against 2.6.29 are untested, but they are known
to compile at least. Could you give them a try?
Cheers
Trond
[-- Attachment #2: patches-fix_nfs_mmap.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 8301 bytes --]
next prev parent reply other threads:[~2009-05-10 4:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0905031552340.1774@praktifix.dwd.de>
2009-05-05 6:14 ` NFS write OOPS with 2.6.29.2 Andrew Morton
2009-05-09 19:16 ` Holger Kiehl
[not found] ` <Pine.LNX.4.64.0905091913010.3181-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
2009-05-10 4:17 ` Trond Myklebust [this message]
[not found] ` <1241929074.5149.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-11 9:24 ` Holger Kiehl
[not found] ` <Pine.LNX.4.64.0905110919490.27423-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
2009-05-11 12:16 ` Trond Myklebust
[not found] ` <1242044201.6691.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-11 12:45 ` Holger Kiehl
[not found] ` <Pine.LNX.4.64.0905111240190.27423-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
2009-05-11 12:57 ` Trond Myklebust
[not found] ` <1242046675.6691.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-13 10:50 ` Suresh Jayaraman
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=1241929074.5149.1.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=Holger.Kiehl-ra7Ruw+Xvfw@public.gmane.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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