From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ken Chen <kenchen@google.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>,
Alexey Dobriyan <adobriyan@sw.ru>
Subject: Re: 2.6.21-git11: BUG in loop.ko
Date: Wed, 9 May 2007 17:05:21 -0700 [thread overview]
Message-ID: <20070509170521.ec2c9ae7.akpm@linux-foundation.org> (raw)
In-Reply-To: <46425EC9.5070209@goop.org>
On Wed, 09 May 2007 16:52:41 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Seems to be getting a 0 refcount. I don't see anything in the recent
> changes which might cause this, but this is relatively new behaviour.
> It was working for me in the 2.6.21-pre time period, but I haven't tried
> this since 2.6.21 was released.
>
> The BUG is actually triggered by the __module_get(THIS_MODULE) in
> loop_set_fd.
>
> J
>
> loop: module loaded
> device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
> ------------[ cut here ]------------
> kernel BUG at /home/jeremy/hg/xen/paravirt/linux/include/linux/module.h:396!
> invalid opcode: 0000 [#1]
> PREEMPT SMP
> Modules linked in: dm_snapshot dm_mod loop
> CPU: 1
> EIP: 0061:[<d085a911>] Not tainted VLI
> EFLAGS: 00010246 (2.6.21-paravirt #1339)
> EIP is at lo_ioctl+0x65/0xa52 [loop]
> eax: 00000000 ebx: cfb92c98 ecx: d085e480 edx: 00000200
> esi: 00004c00 edi: cf8ad428 ebp: cf37fdc0 esp: cf37fbf8
> ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0069
> Process losetup (pid: 440, ti=cf37e000 task=cf30b4d0 task.ti=cf37e000)
> Stack: c1390080 c1390080 cf37fc10 00000008 cf8ad428 cfbb2258 00000000 cf37fc34
> c01458c5 cfb92c98 c1392a40 cf30ba70 cf30b4d0 cf30ba54 00000002 cf30ba70
> cf30b4d0 cf30ba54 00000002 00000003 c134c088 c134c088 cf37fc90 c01215b8
> Call Trace:
> [<c0109173>] show_trace_log_lvl+0x1a/0x30
> [<c0109226>] show_stack_log_lvl+0x9d/0xa5
> [<c0109425>] show_registers+0x1f7/0x336
> [<c010967d>] die+0x119/0x21b
> [<c0382c78>] do_trap+0x8a/0xa4
> [<c0109ad1>] do_invalid_op+0x88/0x92
> [<c0382a42>] error_code+0x72/0x78
> [<c0211c79>] blkdev_driver_ioctl+0x4c/0x5d
> [<c02123de>] blkdev_ioctl+0x754/0x7a2
> [<c0198840>] block_ioctl+0x1b/0x1f
> [<c0182e2e>] do_ioctl+0x22/0x68
> [<c01830a6>] vfs_ioctl+0x232/0x245
> [<c0183102>] sys_ioctl+0x49/0x63
> [<c0108080>] syscall_call+0x7/0xb
> =======================
> Code: ff 83 f8 06 0f 87 5a 09 00 00 ff 24 85 5c bc 85 d0 8b 9b cc 01 00 00 b8 80 e4 85 d0 89 9d 5c fe ff ff e8 37 0a 8f ef 85 c0 75 04 <0f> 0b eb fe b8 01 00 00 00 e8 79 9f 8c ef e8 ec 4b 9c ef c1 e0
> EIP: [<d085a911>] lo_ioctl+0x65/0xa52 [loop] SS:ESP 0069:cf37fbf8
>
A few people have been playing with module refcounting lately. Did you
work out a reproduce-it recipe?
next prev parent reply other threads:[~2007-05-10 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 23:52 2.6.21-git11: BUG in loop.ko Jeremy Fitzhardinge
2007-05-10 0:05 ` Andrew Morton [this message]
2007-05-10 0:20 ` Jeremy Fitzhardinge
2007-05-10 7:39 ` Alexey Dobriyan
2007-05-10 10:33 ` Alexey Dobriyan
2007-05-11 6:10 ` Ken Chen
2007-05-11 15:09 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2007-05-11 7:40 devzero
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=20070509170521.ec2c9ae7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adobriyan@sw.ru \
--cc=jeremy@goop.org \
--cc=kay.sievers@vrfy.org \
--cc=kenchen@google.com \
--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