From: Lei Wen <adrian.wenl@gmail.com>
To: Tejun Heo <tj@kernel.org>
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: Tue, 12 Mar 2013 14:41:10 +0800 [thread overview]
Message-ID: <CALZhoSST8DWKhG9FBJp_Z+WVMLVsiS84zebsNSsnLaKw0f=ZyA@mail.gmail.com> (raw)
In-Reply-To: <20130312061303.GB20037@mtj.dyndns.org>
On Tue, Mar 12, 2013 at 2:13 PM, Tejun Heo <tj@kernel.org> wrote:
> On Tue, Mar 12, 2013 at 02:01:16PM +0800, Lei Wen wrote:
>> I see...
>> How about only check those workqueue structure not on stack?
>> For current onstack usage is rare, and should be easier to check with.
>
> No, kzalloc is not required. The memory area can come from any source.
> If you're interested in improving the debug situation, please stop
> trying to do something impossible (you can't track lifetime of random
> memory area without extra bookkeeping) try to find out why debugobj
> didn't detect it (did you even enable it? either via
> CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT or "debug_objects" boot param).
>
I see...
Thanks for the detailed explanation! :)
Thanks,
Lei
prev parent reply other threads:[~2013-03-12 6:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 7:31 workqueue panic in 3.4 kernel 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
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 [this message]
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='CALZhoSST8DWKhG9FBJp_Z+WVMLVsiS84zebsNSsnLaKw0f=ZyA@mail.gmail.com' \
--to=adrian.wenl@gmail.com \
--cc=leiwen@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).