[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0911122153320.24119@localhost.localdomain>
Date: Thu, 12 Nov 2009 21:55:50 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Oleg Nesterov <oleg@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Mike Galbraith <efault@....de>, Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
Greg KH <gregkh@...e.de>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Tejun Heo <tj@...nel.org>
Subject: Re: GPF in run_workqueue()/list_del_init(cwq->worklist.next) on
resume (was: Re: Help needed: Resume problems in 2.6.32-rc, perhaps related
to preempt_count leakage in keventd)
On Thu, 12 Nov 2009, Rafael J. Wysocki wrote:
> On Thursday 12 November 2009, Thomas Gleixner wrote:
> > On Wed, 11 Nov 2009, Oleg Nesterov wrote:
> > > Well, yes. Because any buggy user can easily kill the system, and we
> > > constantly have the bugs like this one.
> > >
> > > I think we should teach workqueue.c to use debugobjects.c at least.
> >
> > Here you go. Would be interesting to know whether it catches the
> > problem at hand.
>
> How would I tell if it did?
Apply the patch, enable debugobjects and try to reproduce the failure
- w/o the fix patch of course :)
debugobjects should catch the attempt to free the memory which holds
the work_struct, cancel it and print a backtrace where this happened.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists