From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Marvin <marvin24@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: vfs related crash in 2.6.33-rc2
Date: Thu, 31 Dec 2009 05:59:32 +0900 [thread overview]
Message-ID: <87637omb4b.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <200912302144.36718.marvin24@gmx.de> (Marvin's message of "Wed, 30 Dec 2009 21:44:36 +0100")
Marvin <marvin24@gmx.de> writes:
>> Marvin <marvin24@gmx.de> writes:
>> > Hi,
>> >
>> > I'm getting a lot of these:
>> >
>> > kernel: general protection fault: 0000 [#1] SMP
>> > kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:18.3/modalias
>> > kernel: CPU 0
>> > kernel: Pid: 12177, comm: packagekitd Not tainted 2.6.33-rc2 #1
>> > ...
>> >
>> > filesystem is ext4 (in case it matters).
>>
>> BTW, are you using nfs client on this machine?
>>
>
> um - yes, now that I think about it... I killed a nfs umount process (because of an
> offline server) shortly before the oopses started to fire.
OK. Probably, this oops would be same with one which happened on my
machine recently. That path in patch corrupts dcache hash, so it can be
the cause of strange behavior or oops on dcache hash.
If so, the attached patch would fix it.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Recent change is missing to update "rehash". With that change, it will
become the cause of adding dentry to hash twice.
This explains the reason of Oops (dereference the freed dentry in
__d_lookup()) on my machine.
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
fs/nfs/dir.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/nfs/dir.c~nfs-d_rehash-fix fs/nfs/dir.c
--- linux-2.6/fs/nfs/dir.c~nfs-d_rehash-fix 2009-12-28 06:18:09.000000000 +0900
+++ linux-2.6-hirofumi/fs/nfs/dir.c 2009-12-28 06:18:16.000000000 +0900
@@ -1615,6 +1615,7 @@ static int nfs_rename(struct inode *old_
goto out;
new_dentry = dentry;
+ rehash = NULL;
new_inode = NULL;
}
}
_
next prev parent reply other threads:[~2009-12-30 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 16:33 vfs related crash in 2.6.33-rc2 Marvin
2009-12-30 19:44 ` OGAWA Hirofumi
2009-12-30 20:44 ` Marvin
2009-12-30 20:59 ` OGAWA Hirofumi [this message]
2010-01-06 23:41 ` Andrew Morton
2010-01-06 23:55 ` Trond Myklebust
2010-01-07 9:27 ` Marvin
2010-01-07 13:45 ` Trond Myklebust
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=87637omb4b.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin24@gmx.de \
/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