From: Gurudas Pai <gurudas.pai@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel BUG at mm/truncate.c:479! on 2.6.37-rc8
Date: Thu, 20 Jan 2011 12:18:55 +0530 [thread overview]
Message-ID: <4D37DAD7.3050100@oracle.com> (raw)
In-Reply-To: <4D1C2E86.9000004@oracle.com>
Hi Hugh,
Gurudas Pai wrote:
>>> With 2.6.37-rc8 , run a fio test over nfs, with following jobfile,
>>> and we
>>> hit kernel bug.
>>
>> Have you tried the same test on earlier releases?
>> I think the bug is old, yet only recently reported.
> I tried with 2.6.36.2 , even there it is panicing.
>
>
>> This NFS-triggered kernel BUG at mm/truncate.c:479 sounds very like
>> the FUSE-triggered kernel BUG at mm/truncate.c:475 on 2.6.36.1 for
>> which Miklos posted a patch on 14 December. Please give his patch
>> (below) a try and let us know if it fixes the issue for you - thanks.
> Issue fixed with the patch, Thanks :)
Is this patch included in mainline ?
>> There's another of these page_mapped truncation BUGs outstanding,
>> that we suspect has a different cause: yours doesn't sound like that
>> one. I can't explain why three people now in the space of one month
>> should at last hit these ancient bugs!
>>
>
>
> Thanks,
> -Guru
>
next prev parent reply other threads:[~2011-01-20 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 6:46 [BUG] kernel BUG at mm/truncate.c:479! on 2.6.37-rc8 Gurudas Pai
2010-12-29 20:09 ` Hugh Dickins
2010-12-30 7:02 ` Gurudas Pai
2011-01-20 6:48 ` Gurudas Pai [this message]
2011-01-20 11:27 ` Miklos Szeredi
2011-01-20 12:43 ` Gurudas Pai
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=4D37DAD7.3050100@oracle.com \
--to=gurudas.pai@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).