From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: v3.14-rc3: Shutdown triggers poison overwritten complaint
Date: Mon, 17 Feb 2014 14:06:01 +0100 [thread overview]
Message-ID: <53020939.70102@acm.org> (raw)
Hello,
While testing kernel 3.14-rc3 I noticed the call stack below. Had anyone
else perhaps already noticed this ? The test I ran was to change the
mlx4 port type a few times while the ib_ipoib kernel module was loaded.
Thanks,
Bart.
=============================================================================
BUG kmalloc-1024 (Tainted: G B D ): Poison overwritten
-----------------------------------------------------------------------------
INFO: 0xffff880817841ab0-0xffff880817841ab0. First byte 0x6a instead of 0x6b
INFO: Allocated in ib_umad_add_one+0x6e/0x4f0 [ib_umad] age=43184 cpu=0 pid=3820
__slab_alloc+0x448/0x4fa
__kmalloc+0x1f7/0x2b0
ib_umad_add_one+0x6e/0x4f0 [ib_umad]
ib_register_device+0x424/0x4e0 [ib_core]
mlx4_ib_add+0x8b4/0x10c0 [mlx4_ib]
mlx4_add_device+0x3d/0x90 [mlx4_core]
mlx4_register_device+0x5b/0x90 [mlx4_core]
mlx4_change_port_types+0x119/0x160 [mlx4_core]
set_port_type+0x1cc/0x270 [mlx4_core]
dev_attr_store+0x18/0x30
sysfs_kf_write+0x44/0x60
kernfs_fop_write+0xd5/0x150
vfs_write+0xba/0x1e0
SyS_write+0x49/0xa0
tracesys+0xd0/0xd5
INFO: Freed in ib_umad_close+0x130/0x140 [ib_umad] age=0 cpu=5 pid=5141
__slab_free+0x3c/0x29e
kfree+0x250/0x290
ib_umad_close+0x130/0x140 [ib_umad]
__fput+0xea/0x230
____fput+0xe/0x10
task_work_run+0xac/0xe0
do_notify_resume+0x9f/0xc0
int_signal+0x12/0x17
INFO: Slab 0xffffea00205e1000 objects=24 used=24 fp=0x (null) flags=0x2000000000004080
INFO: Object 0xffff880817841a68 @offset=6760 fp=0xffff8808178469a0
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2014-02-17 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53020939.70102@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.