linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Joern Engel <joern@logfs.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: NULL dereference in logfs_get_wblocks()
Date: Mon, 25 Jun 2012 21:40:40 +0800	[thread overview]
Message-ID: <20120625134040.GA6038@localhost> (raw)

Hi Joern,

I got this dmesg when running xfstests 206 in kvm:

[12016.870431] FAT-fs (loop0): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[12016.960017] FAT-fs (loop0): bogus number of reserved sectors
[12017.018620] FAT-fs (loop0): Can't find a valid FAT filesystem
[12017.109282] VFS: could not find a valid V7 on loop0.
[12017.216596] LogFS: Start mount 0
[12017.314045] LogFS: Start unmounting
[12017.373512] BUG: unable to handle kernel NULL pointer dereference at           (null)
[12017.373512] IP: [<ffffffff810da6ec>] ftrace_raw_event_lock_acquire+0x46/0xe9
[12017.373512] PGD 7b9f067 PUD 6f15067 PMD 0 
[12017.373512] Oops: 0000 [#1] SMP DEBUG_PAGEALLOC
[12017.373512] CPU 0 
[12017.373512] Modules linked in:
[12017.373512] 
[12017.373512] Pid: 2898, comm: mount Not tainted 3.5.0-rc2+ #12 Bochs Bochs
[12017.373512] RIP: 0010:[<ffffffff810da6ec>]  [<ffffffff810da6ec>] ftrace_raw_event_lock_acquire+0x46/0xe9
[12017.373512] RSP: 0018:ffff88000ab99ac8  EFLAGS: 00010046
[12017.373512] RAX: 0000000000000000 RBX: ffff880006b44ee8 RCX: ffffffffffffffff
[12017.373512] RDX: 0000000000000000 RSI: 000000000000015f RDI: 0000000000000000
[12017.373512] RBP: ffff88000ab99b28 R08: 0000000000000000 R09: 0000000000000002
[12017.373512] R10: ffffffff82f1462f R11: ffff88000ab99bb8 R12: ffffffff84047910
[12017.373512] R13: 0000000000000000 R14: 0000000000000002 R15: 0000000000000002
[12017.373512] FS:  00007f82ecc417e0(0000) GS:ffff880017200000(0000) knlGS:0000000000000000
[12017.373512] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[12017.373512] CR2: 0000000000000000 CR3: 0000000016778000 CR4: 00000000000006f0
[12017.373512] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[12017.373512] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[12017.373512] Process mount (pid: 2898, threadinfo ffff88000ab98000, task ffff880006a01400)
[12017.373512] Stack:
[12017.373512]  0000000000000001 7fffffffffffffff ffff880000000000 0000000000000092
[12017.373512]  ffff88000ab99fd8 0000000000000001 ffff880006a01400 0000000000000000
[12017.373512]  ffff88000a1df888 ffffffff81394df0 0000000000000002 0000000000000000
[12017.373512] Call Trace:
[12017.373512]  [<ffffffff81394df0>] ? logfs_get_wblocks+0x3a/0x4a
[12017.373512]  [<ffffffff810ddebd>] lock_acquire+0x92/0x103
[12017.373512]  [<ffffffff81394df0>] ? logfs_get_wblocks+0x3a/0x4a
[12017.373512]  [<ffffffff82f14732>] ? wait_for_completion+0x1d/0x1f
[12017.373512]  [<ffffffff81394df0>] ? logfs_get_wblocks+0x3a/0x4a
[12017.373512]  [<ffffffff82f134e3>] __mutex_lock_common+0x58/0x383
[12017.373512]  [<ffffffff81394df0>] ? logfs_get_wblocks+0x3a/0x4a
[12017.373512]  [<ffffffff82f1391d>] mutex_lock_nested+0x40/0x45
[12017.373512]  [<ffffffff81394df0>] logfs_get_wblocks+0x3a/0x4a
[12017.373512]  [<ffffffff81391e62>] logfs_sync_fs+0x1a/0x37
[12017.373512]  [<ffffffff81391e48>] ? logfs_cleanup_gc+0x98/0x98
[12017.373512]  [<ffffffff811aade0>] __sync_filesystem+0x6b/0x7f
[12017.373512]  [<ffffffff811aae44>] sync_filesystem+0x38/0x4d
[12017.373512]  [<ffffffff81398291>] logfs_kill_sb+0x2c/0xe1
[12017.373512]  [<ffffffff81187933>] deactivate_locked_super+0x26/0x57
[12017.373512]  [<ffffffff81398f7d>] logfs_get_sb_device+0x13b/0x147
[12017.373512]  [<ffffffff81399094>] logfs_mount+0x10b/0x11b
[12017.373512]  [<ffffffff81188aa7>] mount_fs+0x69/0x156
[12017.373512]  [<ffffffff81154536>] ? __alloc_percpu+0x10/0x12
[12017.373512]  [<ffffffff8119dbec>] vfs_kern_mount+0x65/0xd2
[12017.373512]  [<ffffffff8119e092>] do_kern_mount+0x4d/0xdf
[12017.373512]  [<ffffffff8119f7c8>] do_mount+0x1c4/0x216
[12017.373512]  [<ffffffff8119fad9>] sys_mount+0x88/0xc2
[12017.373512]  [<ffffffff82f1cf90>] tracesys+0xdd/0xe2
[12017.373512] Code: 89 45 b0 e8 07 f7 ff ff 48 8b 7b 18 48 89 45 b8 48 83 c9 ff 65 48 8b 04 25 20 ca 00 00 44 8b b8 44 e0 ff ff 31 c0 41 8b 74 24 48 <f2> ae 48 8d 7d c8 f7 d1 45 89 f8 89 4d b4 48 63 d1 48 8b 4d b8 
[12017.373512] RIP  [<ffffffff810da6ec>] ftrace_raw_event_lock_acquire+0x46/0xe9
[12017.373512]  RSP <ffff88000ab99ac8>
[12017.373512] CR2: 0000000000000000

Thanks,
Fengguang

                 reply	other threads:[~2012-06-25 13:40 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=20120625134040.GA6038@localhost \
    --to=fengguang.wu@intel.com \
    --cc=joern@logfs.org \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).