From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs: use INIT_WORK_ONSTACK in xfs_alloc_vextent()
Date: Sat, 9 Jun 2012 09:12:27 +1000 [thread overview]
Message-ID: <20120608231227.GY22848@dastard> (raw)
In-Reply-To: <4FD2535A.3050302@redhat.com>
On Fri, Jun 08, 2012 at 02:32:42PM -0500, Eric Sandeen wrote:
> w/o this change I was getting:
>
> [ 742.376495] ODEBUG: object is on stack, but not annotated
> [ 742.377007] ------------[ cut here ]------------
> [ 742.377007] WARNING: at lib/debugobjects.c:302 __debug_object_init+0x1c0/0x3d0()
> ...
> [ 742.377007] Call Trace:
> [ 742.377007] [<ffffffff81060dbf>] warn_slowpath_common+0x7f/0xc0
> [ 742.377007] [<ffffffff81060e1a>] warn_slowpath_null+0x1a/0x20
> [ 742.377007] [<ffffffff81336640>] __debug_object_init+0x1c0/0x3d0
> [ 742.377007] [<ffffffff8133689f>] debug_object_init+0x1f/0x30
> [ 742.377007] [<ffffffff81081cd9>] __init_work+0x19/0x30
> [ 742.377007] [<ffffffffa0299f81>] xfs_alloc_vextent+0x101/0x190 [xfs]
>
> on a debug 3.4 kernel.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Already posted by Jeff twice - I picked this up and started testing
it a couple of days ago:
http://marc.info/?l=linux-fsdevel&m=133877118608852&w=2
http://oss.sgi.com/archives/xfs/2012-06/msg00081.html
Sorry to burst you bubble, Eric, but I think Jeff gets this one. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-08 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 19:32 [PATCH] xfs: use INIT_WORK_ONSTACK in xfs_alloc_vextent() Eric Sandeen
2012-06-08 19:44 ` Ben Myers
2012-06-08 23:12 ` Dave Chinner [this message]
2012-06-08 23:14 ` 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=20120608231227.GY22848@dastard \
--to=david@fromorbit.com \
--cc=sandeen@redhat.com \
--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