From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Oleg <graycardinal@pisem.net>
Cc: linux-kernel@vger.kernel.org, manfred@colorfullife.com
Subject: Re: PROBLEM: kmem_cache_create: duplicate cache fat_cache
Date: Fri, 20 May 2005 22:16:22 +0900 [thread overview]
Message-ID: <87u0ky82c9.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <200505201831.27842.graycardinal@pisem.net> (Oleg's message of "Fri, 20 May 2005 18:31:27 +0400")
Oleg <graycardinal@pisem.net> writes:
> Thank you, but "goto opps", not "goto oops" in patch.
Ahh, sorry. I attached a fixed patch.
>>Didn't you run the modules_install after changed .config?
> No, I'm don't run modules_install. I'm build all modules first and use it (if required) for all my kernel's... And I have one init script, where :
> ...
> /sbin/modprobe vfat
> ...
> I want test to load any modules. Why not ?
If you use the different config kernel, it may use the different
structures size etc., it's obviously wrong and this miss match can be
the cause of Oops.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
mm/slab.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff -puN mm/slab.c~slab-dont-call-bug mm/slab.c
--- linux-2.6.12-rc4/mm/slab.c~slab-dont-call-bug 2005-05-20 22:04:21.000000000 +0900
+++ linux-2.6.12-rc4-hirofumi/mm/slab.c 2005-05-20 22:04:51.000000000 +0900
@@ -1488,8 +1488,10 @@ next:
printk("kmem_cache_create: duplicate cache %s\n",name);
up(&cache_chain_sem);
unlock_cpu_hotplug();
- BUG();
- }
+ set_fs(old_fs);
+ cachep = NULL;
+ goto opps;
+ }
}
set_fs(old_fs);
}
_
next prev parent reply other threads:[~2005-05-20 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 8:17 PROBLEM: kmem_cache_create: duplicate cache fat_cache Oleg
2005-05-19 18:10 ` OGAWA Hirofumi
2005-05-20 14:31 ` Re[2]: " Oleg
2005-05-20 13:16 ` OGAWA Hirofumi [this message]
2005-06-06 19:43 ` Manfred Spraul
2005-06-07 14:26 ` OGAWA Hirofumi
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=87u0ky82c9.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=graycardinal@pisem.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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