All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Dhaval Giani <dhaval@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>
Subject: Re: [BUG stable, 2.6.32.27] sched: delayed cleanup of user_struct
Date: Mon, 10 Jan 2011 19:43:04 +0100	[thread overview]
Message-ID: <20110110184303.GA12393@redhat.com> (raw)
In-Reply-To: <20110110182317.GA16694@suse.de>

On 01/10, Greg KH wrote:
>
> Tell us about what?  I'm totally confused here, what is the problem?

Please look at http://marc.info/?l=linux-kernel&m=129466345327931

I think that free_user's delayed logic is buggy, and the traces
from Stefan seems to confirm the theory.

As Mike suggests, we can just remove the deprecated USER_SCHED
code and forget about this problem.

Oleg.


      reply	other threads:[~2011-01-10 18:50 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
2011-01-10 18:23               ` Greg KH
2011-01-10 18:43                 ` Oleg Nesterov [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=20110110184303.GA12393@redhat.com \
    --to=oleg@redhat.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=efault@gmx.de \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.