From: Chris Mason <clm@fb.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <torvalds@linux-foundation.org>, <linux-kernel@vger.kernel.org>
Subject: Re: New crashes walking proc with Saturday's git
Date: Sun, 23 Nov 2014 11:16:51 -0500 [thread overview]
Message-ID: <1416759411.24312.13@mail.thefacebook.com> (raw)
In-Reply-To: <20141123161120.GB7070@pd.tnic>
On Sun, Nov 23, 2014 at 11:11 AM, Borislav Petkov <bp@alien8.de> wrote:
> On Sun, Nov 23, 2014 at 10:56:27AM -0500, Chris Mason wrote:
>> On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason <clm@fb.com> wrote:
>> >Since it looks like a race between process exit and /proc, I'll
>> try to
>> >hammer on that for a better reproduction. But, here's hoping that
>> >someone has already seen this one:
>>
>> It falls over in less than 5 minutes with a fork bomb going. I'll
>> try to
>> bisect.
>
> I'm seeing the same thing:
It must be:
commit 6e998916dfe327e785e7c2447959b2c1a3ea4930
Author: Stanislaw Gruszka <sgruszka@redhat.com>
Date: Wed Nov 12 16:58:44 2014 +0100
sched/cputime: Fix clock_nanosleep()/clock_gettime() inconsistency
I'll do two runs to confirm, but it's the only related patch between
rc5 and now.
-chris
next prev parent reply other threads:[~2014-11-23 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:02 New crashes walking proc with Saturday's git Chris Mason
2014-11-23 15:56 ` Chris Mason
2014-11-23 16:11 ` Borislav Petkov
2014-11-23 16:16 ` Chris Mason [this message]
2014-11-23 16:32 ` Borislav Petkov
2014-11-23 16:36 ` Chris Mason
2014-11-23 16:49 ` Chris Mason
2014-11-23 16:59 ` Borislav Petkov
2014-11-23 21:05 ` Thomas Gleixner
2014-11-23 21:11 ` Chris Mason
2014-11-23 21:29 ` Chris Mason
2014-11-23 21:38 ` Borislav Petkov
2014-11-23 21:38 ` Thomas Gleixner
2014-11-23 21:42 ` Chris Mason
2014-11-23 22:04 ` [PATCH] sched: Provide update_curr callbacks for stop/idle scheduling classes Thomas Gleixner
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=1416759411.24312.13@mail.thefacebook.com \
--to=clm@fb.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.