From: Andreas Happe <andreashappe@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test3-mm2: JFS/cryptoapi OOPS
Date: Tue, 19 Aug 2003 15:43:30 +0000 [thread overview]
Message-ID: <slrnbk4hd2.8pm.andreashappe@flatline.ath.cx> (raw)
trying to run 'mkfs.jfs /dev/loop1' on a file backed cryptoloop using
aes creates following OOPS. System is a P3m, UP with enabled preemption.
kernel BUG at mm/filemap.c:1930!
invalid operand: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c013e919>] Not tainted VLI
EFLAGS: 00010282
EIP is at generic_file_aio_write_nolock+0xe9/0x100
eax: c1523c20 ebx: 0ff01000 ecx: c156bdab edx: c014b1ab
esi: 00000000 edi: cfc19f6c ebp: cfc19e84 esp: cfc19e40
ds: 007b es: 007b ss: 0068
Process mkfs.jfs (pid: 8985, threadinfo=cfc18000 task=cb42b920)
Stack: 00000000 cfc18000 c03837d0 c0383898 c03837d0 cf84dba0 cf84dc30 cbd635e0
cfc19e84 cbd635e0 0ff01000 00000000 c013ea92 cfc19e84 cfc19f6c 00000001
cbd63600 00000000 00000002 00000000 00000001 ffffffff cbd635e0 c20a630c
Call Trace:
[<c013ea92>] __crc_generic_read_dir+0x14/0x32
[<c014b1ab>] do_anonymous_page+0x13b/0x250
[<c011d630>] autoremove_wake_function+0x0/0x50
[<c01192dc>] do_page_fault+0x23c/0x456
[<c01d94b2>] tty_read+0xf2/0x170
[<c0163107>] blkdev_file_write+0x37/0x40
[<c0159ce2>] vfs_write+0xe2/0x150
[<c0159e02>] sys_write+0x42/0x70
[<c03320cb>] syscall_call+0x7/0xb
Code: f2 90 89 7c 24 04 8b 44 24 40 c7 44 24 08 01 00 00 00 89 2c 24 89 44 24 0c e8 74 f3 ff ff 83 7d 10 ff 89 c7 75 cd e9 6f ff ff ff <0f> 0b 8a 07 9f a1 34 c0 e9 53 ff ff ff 8d 76 00 8d bc 27 00 00
--Andreas
next reply other threads:[~2003-08-19 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 15:43 Andreas Happe [this message]
2003-08-19 18:38 ` 2.6.0-test3-mm2 recommended test bed Mitch Sako
2003-08-20 20:19 ` Cliff White
2003-08-19 22:12 ` 2.6.0-test3-mm2: JFS/cryptoapi OOPS Andrew Morton
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=slrnbk4hd2.8pm.andreashappe@flatline.ath.cx \
--to=andreashappe@gmx.net \
--cc=linux-kernel@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