linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sameer Nanda <snanda@chromium.org>
To: David Rientjes <rientjes@google.com>
Cc: Luigi Semenzato <semenzato@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	mhocko@suse.cz, Johannes Weiner <hannes@cmpxchg.org>,
	rusty@rustcorp.com.au, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm, oom: Fix race when selecting process to kill
Date: Tue, 5 Nov 2013 19:04:03 -0800	[thread overview]
Message-ID: <CANMivWZrefY1bbgpJgABqcUwKfqOR9HQtGNY6cWdutcMASeo2A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311051727090.29471@chino.kir.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Tue, Nov 5, 2013 at 5:27 PM, David Rientjes <rientjes@google.com> wrote:

> On Tue, 5 Nov 2013, Luigi Semenzato wrote:
>
> > It's not enough to hold a reference to the task struct, because it can
> > still be taken out of the circular list of threads.  The RCU
> > assumptions don't hold in that case.
> >
>
> Could you please post a proper bug report that isolates this at the cause?
>

We've been running into this issue on Chrome OS. crbug.com/256326 has
additional
details.  The issue manifests itself as a soft lockup.

The kernel we've been seeing this on is 3.8.

We have a pretty consistent repro currently.  Happy to try out other
suggestions
for a fix.


>
> Thanks.
>



-- 
Sameer

[-- Attachment #2: Type: text/html, Size: 1514 bytes --]

  parent reply	other threads:[~2013-11-06  3:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 23:26 Sameer Nanda
2013-11-06  1:18 ` David Rientjes
2013-11-06  1:25   ` Luigi Semenzato
2013-11-06  1:27     ` David Rientjes
2013-11-06  3:00       ` Vladimir Murzin
2013-11-06  3:04       ` Sameer Nanda [this message]
2013-11-06  4:45         ` Luigi Semenzato
2013-11-06  7:17           ` Luigi Semenzato
2013-11-06 16:58             ` Sameer Nanda
2013-11-07  0:35               ` David Rientjes
2013-11-07 19:34                 ` Sameer Nanda
2013-11-08 18:07                 ` [PATCH v2] " Sameer Nanda
2013-11-08 18:45                   ` Oleg Nesterov
2013-11-08 19:49                     ` [PATCH v3] " Sameer Nanda
2013-11-09 15:16                       ` Oleg Nesterov
2013-11-11 23:15                         ` Sameer Nanda
2013-11-12  0:21                         ` [PATCH v4] " Sameer Nanda
2013-11-12 15:13                           ` Michal Hocko
2013-11-12 20:01                           ` Oleg Nesterov
2013-11-12 20:08                             ` Sameer Nanda
2013-11-12 20:23                               ` [PATCH v5] " Sameer Nanda
2013-11-13  2:33                                 ` David Rientjes
2013-11-13 16:46                                   ` Sameer Nanda
2013-11-13 17:18                                     ` [PATCH v6] " Sameer Nanda
2013-11-13 17:29                                       ` Oleg Nesterov
2013-11-14 13:43                                       ` dserrg
2013-11-14 17:03                                         ` Sameer Nanda

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=CANMivWZrefY1bbgpJgABqcUwKfqOR9HQtGNY6cWdutcMASeo2A@mail.gmail.com \
    --to=snanda@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=rientjes@google.com \
    --cc=rusty@rustcorp.com.au \
    --cc=semenzato@google.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