From: Christoph Hellwig <hch@lst.de>
To: mbroz@redhat.com, jaxboe@fusionio.com
Cc: linux-kernel@vger.kernel.org
Subject: loop warnings in current git HEAD
Date: Sat, 23 Oct 2010 17:59:50 +0200 [thread overview]
Message-ID: <20101023155950.GA31946@lst.de> (raw)
The loop driver in current git HEAD is rather unhappy when running
xfstests. I gets lots of warnings like the one below. The most likely
culprit seems to be:
loop: add some basic read-only sysfs attributes
(commit ee86273062cbb310665fe49e1f1937d2cf85b0b9)
[ 1055.017350] WARNING: at /home/hch/work/linux-2.6/fs/sysfs/dir.c:451 sysfs_add_one+0xa4/0x110()
[ 1055.019843] Hardware name: Bochs
[ 1055.021004] sysfs: cannot create duplicate filename '/devices/virtual/block/loop0/loop'
[ 1055.023362] Modules linked in:
[ 1055.024274] Pid: 7028, comm: mount Tainted: G W 2.6.36+ #6
[ 1055.025622] Call Trace:
[ 1055.026312] [<c0169ead>] warn_slowpath_common+0x6d/0xa0
[ 1055.027464] [<c026f534>] ? sysfs_add_one+0xa4/0x110
[ 1055.028651] [<c026f534>] ? sysfs_add_one+0xa4/0x110
[ 1055.030329] [<c0169f5e>] warn_slowpath_fmt+0x2e/0x30
[ 1055.031877] [<c026f534>] sysfs_add_one+0xa4/0x110
[ 1055.033052] [<c09e7645>] ? mutex_lock_nested+0x35/0x40
[ 1055.034273] [<c026f5fc>] create_dir+0x5c/0xa0
[ 1055.035318] [<c026f712>] sysfs_create_subdir+0x22/0x30
[ 1055.036570] [<c0270aec>] internal_create_group+0x4c/0x170
[ 1055.037778] [<c0270c3c>] sysfs_create_group+0xc/0x10
[ 1055.038902] [<c079de83>] lo_ioctl+0x623/0x8c0
[ 1055.042214] [<c019a3fa>] ? print_lock_contention_bug+0x1a/0xe0
[ 1055.043471] [<c079d860>] ? lo_ioctl+0x0/0x8c0
[ 1055.044557] [<c07065ac>] __blkdev_driver_ioctl+0x2c/0x40
[ 1055.048076] [<c0706a9b>] blkdev_ioctl+0x21b/0x730
[ 1055.049155] [<c019bf3b>] ? trace_hardirqs_on+0xb/0x10
[ 1055.050277] [<c023ce0b>] block_ioctl+0x3b/0x50
[ 1055.051302] [<c023cdd0>] ? block_ioctl+0x0/0x50
[ 1055.059103] [<c02216ed>] do_vfs_ioctl+0x7d/0x5e0
[ 1055.060225] [<c021d510>] ? path_put+0x20/0x30
[ 1055.061263] [<c0217881>] ? sys_readlinkat+0x71/0x90
[ 1055.062360] [<c0221c89>] sys_ioctl+0x39/0x60
[ 1055.063358] [<c09e907d>] syscall_call+0x7/0xb
[ 1055.064470] ---[ end trace 1de52d78815cd17d ]---
next reply other threads:[~2010-10-23 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 15:59 Christoph Hellwig [this message]
2010-10-24 10:02 ` Milan Broz
2010-10-24 16:13 ` Christoph Hellwig
2010-10-24 16:18 ` Milan Broz
2010-10-25 7:11 ` [PATCH] loop: Properly clear sysfs in autoclear mode Milan Broz
2010-10-25 12:41 ` Jeff Chua
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=20101023155950.GA31946@lst.de \
--to=hch@lst.de \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.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
Powered by JetHome