From: zwane@commfireservices.com
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH][2.5.33] oops on futexfs mount
Date: Tue, 3 Sep 2002 06:37:34 -0400 (EDT) [thread overview]
Message-ID: <20020903103734.4412BBC51@hemi.commfireservices.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
Hi Rusty,
I know it's in the don't do that category ;)
Index: linux-2.5.33/kernel/futex.c
===================================================================
RCS file: /build/cvsroot/linux-2.5.33/kernel/futex.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 futex.c
--- linux-2.5.33/kernel/futex.c 31 Aug 2002 22:32:06 -0000 1.1.1.1
+++ linux-2.5.33/kernel/futex.c 3 Sep 2002 08:51:31 -0000
@@ -359,6 +359,7 @@
static struct file_system_type futex_fs_type = {
.name = "futexfs",
.get_sb = futexfs_get_sb,
+ .kill_sb = kill_anon_super,
};
static int __init init(void)
Unable to handle kernel NULL pointer dereference at virtual address 00000000
00000000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0060:[<00000000>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: cf729240 ebx: cf729200 ecx: 00000001 edx: 00000000
esi: c552e000 edi: c0441d20 ebp: c54f3000 esp: c552fee8
ds: 0068 es: 0068 ss: 0068
Stack: c0155088 cf729200 cf7edcf8 cf7edcf8 c016b538 cf7edcf8 ffffffea c17df194
cf7edcf8 c016cac8 cf729200 cd66b824 42029c74 00000000 00001000 c54e8000
00000000 c552ff50 c016ccfb c552ff50 c54e8000 00000000 00000000 c54f3000
Call Trace: [<c0155088>] [<c016b538>] [<c016cac8>] [<c016ccfb>] [<c0140068>]
[<c016cb2c>] [<c016d362>] [<c0107bdf>]
Code: Bad EIP value.
>>EIP; 00000000 Before first symbol
Trace; c0155088 <deactivate_super+98/140>
Trace; c016b538 <__mntput+18/30>
Trace; c016cac8 <do_add_mount+128/140>
Trace; c016ccfb <do_mount+17b/1a0>
Trace; c0140068 <s_show+198/2c0>
Trace; c016cb2c <copy_mount_options+4c/a0>
Trace; c016d362 <sys_mount+e2/180>
Trace; c0107bdf <syscall_call+7/b>
reply other threads:[~2002-09-03 10:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020903103734.4412BBC51@hemi.commfireservices.com \
--to=zwane@commfireservices.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).