From: Mike Galbraith <efault@gmx.de>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
Kay Sievers <kay.sievers@vrfy.org>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [BUG stable, 2.6.32.27] sched: delayed cleanup of user_struct
Date: Mon, 10 Jan 2011 18:07:50 +0100 [thread overview]
Message-ID: <1294679270.8345.12.camel@marge.simson.net> (raw)
In-Reply-To: <20110110141959.GA312@redhat.com>
On Mon, 2011-01-10 at 15:19 +0100, Oleg Nesterov wrote:
> On 01/10, Stefan Priebe - Profihost AG wrote:
> >
> >>> You can find the logs here:
> >>> http://pastebin.com/hNd15E8K
> >>
> >> Good. Sadly, I didn't see this trace before...
> >>
> >> kernel BUG at kernel/workqueue.c:287!
> >>
> >> this matches "INIT_DELAYED_WORK() can corrupt the pending work" I
> >> mentioned.
> > Sorry to ask this but this could also be "workarounded" by disabled
> > GROUP_SCHED? Or is this another thing?
>
> Yes, this looks like the same thing.
>
> But let me repeat, today I looked at this code for the first time ;)
>
> > Will wait if greg or anybody else can tell
> > us something about it.
>
> Indeed.
I'd be inclined to just shoot USER_SCHED, since it's dead upstream. I'm
putting a small backport series together, and could add that to the mix.
-Mike
next prev parent reply other threads:[~2011-01-10 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2AB8F7.7030506@profihost.ag>
[not found] ` <20110110114913.GA22298@redhat.com>
2011-01-10 12:36 ` [BUG stable, 2.6.32.27] sched: delayed cleanup of user_struct Oleg Nesterov
2011-01-10 12:46 ` Stefan Priebe - Profihost AG
2011-01-10 13:35 ` Oleg Nesterov
2011-01-10 14:01 ` Stefan Priebe - Profihost AG
2011-01-10 14:08 ` Oleg Nesterov
2011-01-10 14:23 ` Stefan Priebe - Profihost AG
2011-01-10 14:19 ` Oleg Nesterov
2011-01-10 17:07 ` Mike Galbraith [this message]
2011-01-10 18:23 ` Greg KH
2011-01-10 18:43 ` Oleg Nesterov
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=1294679270.8345.12.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=s.priebe@profihost.ag \
/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