From: Jan Kara <jack@suse.cz>
To: xfs@oss.sgi.com
Subject: Warning from unlock_new_inode
Date: Wed, 22 Feb 2012 23:01:37 +0100 [thread overview]
Message-ID: <20120222220137.GB3650@quack.suse.cz> (raw)
Hello,
while running fsstress on XFS partition with 3.3-rc4 kernel + my freeze
fixes (they do not touch anything relevant AFAICT) I've got the following
warning:
[ 62.699499] ------------[ cut here ]------------
[ 62.699531] WARNING: at fs/inode.c:967 unlock_new_inode+0x70/0x80()
[ 62.699538] Hardware name: Bochs
[ 62.699543] Modules linked in: xfs exportfs ipv6 mperf loop processor thermal_sys 8250_pnp button 8250 serial_core
[ 62.699572] Pid: 2397, comm: fsstress Not tainted 3.3.0-rc4-xen+ #9
[ 62.699578] Call Trace:
[ 62.699588] [<ffffffff81131130>] ? unlock_new_inode+0x70/0x80
[ 62.699598] [<ffffffff8103667a>] warn_slowpath_common+0x7a/0xb0
[ 62.699606] [<ffffffff810366c5>] warn_slowpath_null+0x15/0x20
[ 62.699613] [<ffffffff81131130>] unlock_new_inode+0x70/0x80
[ 62.699668] [<ffffffffa00b787f>] xfs_setup_inode+0x20f/0x2f0 [xfs]
[ 62.699696] [<ffffffffa00b3614>] xfs_iget+0x884/0x8c0 [xfs]
[ 62.699721] [<ffffffffa00b2e78>] ? xfs_iget+0xe8/0x8c0 [xfs]
[ 62.699748] [<ffffffffa00b8898>] xfs_bulkstat_one_int+0xa8/0x350 [xfs]
[ 62.699775] [<ffffffffa00b8770>] ? xfs_inumbers_fmt+0x70/0x70 [xfs]
[ 62.699803] [<ffffffffa00b8b5b>] xfs_bulkstat_one+0x1b/0x20 [xfs]
[ 62.699832] [<ffffffffa00b8f0a>] xfs_bulkstat+0x3aa/0x810 [xfs]
[ 62.699858] [<ffffffffa00b8b40>] ? xfs_bulkstat_one_int+0x350/0x350 [xfs]
[ 62.699899] [<ffffffffa00b4266>] xfs_ioc_bulkstat+0xe6/0x180 [xfs]
[ 62.699925] [<ffffffffa00b5756>] xfs_file_ioctl+0x426/0xa30 [xfs]
[ 62.699945] [<ffffffff810f7edb>] ? might_fault+0x3b/0x90
[ 62.699958] [<ffffffff81110191>] ? kfree_debugcheck+0x11/0x30
[ 62.699966] [<ffffffff81111d6e>] ? kmem_cache_free+0x13e/0x150
[ 62.699975] [<ffffffff8112954c>] do_vfs_ioctl+0x9c/0x590
[ 62.699987] [<ffffffff81114df0>] ? fd_install+0x30/0x60
[ 62.699997] [<ffffffff8138b5a5>] ? sysret_check+0x22/0x5d
[ 62.700005] [<ffffffff81129a8a>] sys_ioctl+0x4a/0x80
[ 62.700012] [<ffffffff8138b579>] system_call_fastpath+0x16/0x1b
[ 62.700020] ---[ end trace 0a20034268e46d92 ]---
It is the first time I've got this warning and I'm already testing for
quite some time so it doesn't look easily reproducible...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-02-22 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 22:01 Jan Kara [this message]
2012-02-28 8:34 ` Warning from unlock_new_inode Christoph Hellwig
2012-02-28 10:11 ` Jan Kara
2012-02-29 0:53 ` Dave Chinner
2012-02-29 1:49 ` Dave Chinner
2012-02-29 9:03 ` Christoph Hellwig
2012-02-29 10:24 ` Jan Kara
2012-03-01 3:03 ` Ben Myers
2012-03-01 3:58 ` Dave Chinner
2012-03-01 5:09 ` Eric Sandeen
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=20120222220137.GB3650@quack.suse.cz \
--to=jack@suse.cz \
--cc=xfs@oss.sgi.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