From: Jens Axboe <axboe@kernel.dk>
To: Ed Cashin <ecashin@coraid.com>
Cc: Josh Boyer <jwboyer@redhat.com>,
"mitko@banksoft-bg.com" <mitko@banksoft-bg.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-team@fedoraproject.org" <kernel-team@fedoraproject.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Oops on aoe module removal
Date: Thu, 03 Jan 2013 20:45:40 +0100 [thread overview]
Message-ID: <50E5DFE4.5020007@kernel.dk> (raw)
In-Reply-To: <ffc5cf0d1e3273770b65bc7de4a4851e@coraid.com>
On 2013-01-03 20:28, Ed Cashin wrote:
> Lines: 75
>
> On Thu, Jan 03, 2013 at 12:15:35PM -0600, Ed Cashin wrote:
> ...
>>>>>>> On Jan 3, 2013, at 8:25 AM, Josh Boyer wrote:
> ...
>>>>>>>> [699170.611997] aoe: AoE v47 initialised.
> ...
>>>>>>>> [699231.308319] WARNING: at lib/list_debug.c:62 __list_del_entry+0x82/0xd0()
>>>>>>>> [699231.312031] Hardware name: S5000VSA
>>>>>>>> [699231.315658] list_del corruption. next->prev should be ffff880009fa37e8, but was ffffffff81c79c00
>>>>>>>> [699231.319352] Modules linked in: aoe(-) ip6table_filter ip6_tables ebtable_nat ebtables lockd sunrpc bridge 8021q garp stp llc vfat fat binfmt_misc iTCO_wdt iTCO_vendor_support vhost_net lpc_ich radeon tun macvtap mfd_core serio_raw coretemp i2c_algo_bit ttm i5000_edac macvlan drm_kms_helper e1000e edac_core microcode i5k_amb shpchp i2c_i801 drm kvm_intel i2c_core kvm ioatdma dca raid1
>>>>>>>> [699231.336259] Pid: 8584, comm: modprobe Not tainted 3.6.11-1.fc17.x86_64 #1
>>>>>>>> [699231.340561] Call Trace:
>>>>>>>> [699231.344865] [<ffffffff8105c8ef>] warn_slowpath_common+0x7f/0xc0
>>>>>>>> [699231.349212] [<ffffffff8105c9e6>] warn_slowpath_fmt+0x46/0x50
>>>>>>>> [699231.353595] [<ffffffff812eee52>] __list_del_entry+0x82/0xd0
>>>>>>>> [699231.357954] [<ffffffff812eeeb1>] list_del+0x11/0x40
>>>>>>>> [699231.362319] [<ffffffff812f6458>] percpu_counter_destroy+0x28/0x50
>>>>>>>> [699231.366712] [<ffffffff8114c513>] bdi_destroy+0x43/0x140
>>>>>>>> [699231.371127] [<ffffffff812be20c>] blk_release_queue+0x8c/0xc0
>>>>>>>> [699231.375454] [<ffffffff812dc322>] kobject_cleanup+0x82/0x1b0
>>>>>>>> [699231.379675] [<ffffffff812dc1ab>] kobject_put+0x2b/0x60
>>>>>>>> [699231.383851] [<ffffffff812b80a5>] blk_put_queue+0x15/0x20
>>>>>>>> [699231.387899] [<ffffffff812bc659>] blk_cleanup_queue+0xc9/0xe0
>>>>>>>> [699231.391794] [<ffffffffa01f53f5>] aoedev_freedev+0x135/0x150 [aoe]
>>>>>>>> [699231.395668] [<ffffffffa01f59a5>] aoedev_exit+0x65/0x80 [aoe]
>>>>>>>> [699231.399493] [<ffffffffa01f5afe>] aoe_exit+0x2e/0x40 [aoe]
>>>>>>>> [699231.403273] [<ffffffff810bdefe>] sys_delete_module+0x16e/0x2d0
>>>>>>>> [699231.407119] [<ffffffff8161db56>] ? __schedule+0x3c6/0x7a0
>>>>>>>> [699231.411050] [<ffffffff8119054a>] ? sys_write+0x4a/0x90
>>>>>>>> [699231.415033] [<ffffffff81627329>] system_call_fastpath+0x16/0x1b
>>>>>>>> [699231.419117] ---[ end trace 9e1558af1964b569 ]---
>>>>>>>> [699231.423248] ------------[ cut here ]------------
>
> The blk_alloc_queue has already done a bdi_init, so do not bdi_init again in
> aoeblk_gdalloc.
>
> The patch below applies to v3.5.6, with its v47 aoe driver. On my system it
> eliminates the list_del corruption messages.
Since the patch doesn't apply to current -git, does the problem not
exist there?
--
Jens Axboe
next prev parent reply other threads:[~2013-01-03 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 13:25 Oops on aoe module removal Josh Boyer
2013-01-03 14:02 ` Ed Cashin
2013-01-03 14:09 ` Jens Axboe
2013-01-03 14:12 ` Jens Axboe
2013-01-03 15:28 ` Ed Cashin
2013-01-03 15:34 ` Jens Axboe
2013-01-03 18:15 ` Ed Cashin
2013-01-03 19:28 ` Ed Cashin, Ed Cashin
2013-01-03 19:45 ` Jens Axboe [this message]
2013-01-03 19:57 ` Ed Cashin
2013-01-03 20:50 ` Ed Cashin
2013-01-03 21:00 ` Josh Boyer
2013-01-04 12:35 ` Josh Boyer
2013-01-03 21:20 ` Ed Cashin
2013-01-13 5:34 ` Ben Hutchings
2013-01-13 14:23 ` Ed Cashin
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=50E5DFE4.5020007@kernel.dk \
--to=axboe@kernel.dk \
--cc=ecashin@coraid.com \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitko@banksoft-bg.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.