From: Tejun Heo <tj@kernel.org>
To: Lei Wen <adrian.wenl@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, leiwen@marvell.com,
wwang27@marvell.com
Subject: Re: workqueue panic in 3.4 kernel
Date: Mon, 11 Mar 2013 22:24:26 -0700 [thread overview]
Message-ID: <20130312052426.GV14556@mtj.dyndns.org> (raw)
In-Reply-To: <CALZhoSTnCC4si12xQXy2Cid5S2vAwOneOnZ_o2XNjidoqA9bsg@mail.gmail.com>
On Tue, Mar 12, 2013 at 01:18:01PM +0800, Lei Wen wrote:
> > You're initializing random piece of memory which may contain any
> > garbage and triggering BUG if some bit is set on it. No, you can't do
> > that. debugobj is the right tool for debugging object lifetime issues
> > and is already supported.
>
> The debugobj is not helping on this issue, I have enabled both
> CONFIG_DEBUG_OBJECTS_WORK and CONFIG_DEBUG_OBJECTS.
> But find they didn't report any issue at all.
It should. No idea why it didn't. Would be interesting to find out
why.
> And I am not init random memory, original issue is call init multi-times
> for one structure and that piece of memory already been allocated.
> And __INIT_WORK shouldn't call over random memory, right?
Memory areas aren't always zero on allocation.
--
tejun
next prev parent reply other threads:[~2013-03-12 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 7:31 Lei Wen
2013-03-05 16:32 ` Tejun Heo
2013-03-06 14:39 ` Lei Wen
2013-03-06 19:14 ` Tejun Heo
2013-03-07 1:15 ` Lei Wen
2013-03-07 15:22 ` Lei Wen
2013-03-07 15:49 ` Tejun Heo
2013-03-07 16:07 ` Thomas Gleixner
[not found] ` <CALZhoSQBH3RxSoaVDCYoCyRVRndht-Rk0rh_w5Dbp6+5T_auSw@mail.gmail.com>
2013-03-12 5:12 ` Tejun Heo
2013-03-12 5:18 ` Lei Wen
2013-03-12 5:24 ` Tejun Heo [this message]
2013-03-12 5:34 ` Lei Wen
2013-03-12 5:40 ` Tejun Heo
2013-03-12 6:01 ` Lei Wen
2013-03-12 6:13 ` Tejun Heo
2013-03-12 6:41 ` Lei Wen
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=20130312052426.GV14556@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=adrian.wenl@gmail.com \
--cc=leiwen@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wwang27@marvell.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
all inboxes | Powered by JetHome®