From: Jens Axboe <axboe@kernel.dk>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org, joern@logfs.org, logfs@logfs.org
Subject: Re: [null_blk] INFO: trying to register non-static key.
Date: Tue, 11 Feb 2014 20:41:09 -0700 [thread overview]
Message-ID: <20140212034109.GB9739@kernel.dk> (raw)
In-Reply-To: <20140212024728.GA10263@localhost>
On Wed, Feb 12 2014, Fengguang Wu wrote:
> Hi Jens,
>
> I got the below dmesg and the first bad commit is
>
> commit f2298c0403b0dfcaef637eba0c02c4a06d7a25ab
> Author: Jens Axboe <axboe@kernel.dk>
> CommitDate: Fri Oct 25 11:56:00 2013 +0100
Hmm dunno, the below looks more like a logfs issue, given the calltrace.
The fact that null_blk is the device used is probably less interesting.
> [ 18.158432] VFS: could not find a valid V7 on nullb0.
> [ 18.159280] LogFS: Start mount 1
> [ 18.159732] LogFS: Start unmounting
> [ 18.160368] INFO: trying to register non-static key.
> [ 18.160986] the code is fine but needs lockdep annotation.
> [ 18.161675] turning off the locking correctness validator.
> [ 18.162341] CPU: 0 PID: 634 Comm: mount Not tainted 3.14.0-rc2-wl-01363-gf8a1366 #2
> [ 18.163266] 0000000000000000 ffff88000b839c00 ffffffff827922a5 ffff88000b839cb8
> [ 18.163516] ffffffff810c0202 ffff88000bac1008 ffff88000b839c98 ffff88000b839c58
> [ 18.163516] 0000000000000002 ffff88000bb4f000 ffff880000000000 ffffffff00000001
> [ 18.163516] Call Trace:
> [ 18.163516] [<ffffffff827922a5>] dump_stack+0x19/0x1b
> [ 18.163516] [<ffffffff810c0202>] __lock_acquire+0x252/0x1d80
> [ 18.163516] [<ffffffff8115cc10>] ? writeback_inodes_sb_nr+0xc0/0xe0
> [ 18.163516] [<ffffffff81296146>] ? logfs_get_wblocks+0x76/0x90
> [ 18.163516] [<ffffffff810c2590>] lock_acquire+0x70/0x90
> [ 18.163516] [<ffffffff81296146>] ? logfs_get_wblocks+0x76/0x90
> [ 18.163516] [<ffffffff827a26f1>] mutex_lock_nested+0x61/0x380
> [ 18.163516] [<ffffffff81296146>] ? logfs_get_wblocks+0x76/0x90
> [ 18.163516] [<ffffffff81296146>] logfs_get_wblocks+0x76/0x90
> [ 18.163516] [<ffffffff81293024>] logfs_sync_fs+0x14/0x30
> [ 18.163516] [<ffffffff81160929>] sync_filesystem+0x59/0xb0
> [ 18.163516] [<ffffffff8129a327>] logfs_kill_sb+0x27/0xf0
> [ 18.163516] [<ffffffff81137afd>] deactivate_locked_super+0x2d/0x50
> [ 18.163516] [<ffffffff8129b1f3>] logfs_mount+0x763/0x7e0
> [ 18.163516] [<ffffffff811391d0>] mount_fs+0x10/0xe0
> [ 18.163516] [<ffffffff81153f49>] vfs_kern_mount+0x69/0x140
> [ 18.163516] [<ffffffff827a5efc>] ? _raw_read_unlock+0x2c/0x50
> [ 18.163516] [<ffffffff81156354>] do_mount+0x934/0xb90
> [ 18.163516] [<ffffffff81111462>] ? might_fault+0x52/0xb0
> [ 18.163516] [<ffffffff811040a5>] ? strndup_user+0x35/0x50
> [ 18.163516] [<ffffffff811568fc>] SyS_mount+0x8c/0xd0
> [ 18.163516] [<ffffffff827a713b>] system_call_fastpath+0x1a/0x1f
--
Jens Axboe
prev parent reply other threads:[~2014-02-12 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 2:47 [null_blk] INFO: trying to register non-static key Fengguang Wu
2014-02-12 3:41 ` Jens Axboe [this message]
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=20140212034109.GB9739@kernel.dk \
--to=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logfs@logfs.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