From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Mason <clm@fb.com>
Cc: Borislav Petkov <bp@alien8.de>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: New crashes walking proc with Saturday's git
Date: Sun, 23 Nov 2014 22:05:43 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1411232141590.6439@nanos> (raw)
In-Reply-To: <1416761342.24312.15@mail.thefacebook.com>
On Sun, 23 Nov 2014, Chris Mason wrote:
> On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov <bp@alien8.de> wrote:
> > On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote:
> > > 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.
>
> I've adding Ingo and Stanislaw to the cc. With
> 6e998916dfe327e785e7c2447959b2c1a3ea4930 reverted, I'm no longer crashing.
>
> Repeating the stack trace for the new cc list. I see the crash with atop or
> similar walkers of /proc racing against exiting programs. Given the NULL rip,
> this line from the patch is probably broken, but it really feels like we
> should be falling over on p->sched_class and not on the update_curr func.
>
> + p->sched_class->update_curr(rq);
>
> I'm leaving my fork bomb running on two machines with the patch reverted to
> make sure.
The sched_class instances which do not have update_curr are stop_task
and idle. Patch below.
I'm sure nobody thought about the stats read code path here.
[ 1053.759741] [<ffffffff81208348>] do_task_stat+0x8b8/0xb00
do_task_stat(()
thread_group_cputime_adjusted()
thread_group_cputime()
task_cputime()
task_sched_runtime()
if (task_current(rq, p) && task_on_rq_queued(p)) {
update_rq_clock(rq);
p->sched_class->update_curr(rq);
}
Now if the stats are read for a stomp machine task, aka 'migration/N'
and that task is current on its cpu. Ooops.
I added the callback for idle tasks as well for completeness sake.
Thanks,
tglx
---
diff --git a/kernel/sched/idle_task.c b/kernel/sched/idle_task.c
index 67ad4e7f506a..c65dac8c97cd 100644
--- a/kernel/sched/idle_task.c
+++ b/kernel/sched/idle_task.c
@@ -75,6 +75,10 @@ static unsigned int get_rr_interval_idle(struct rq *rq, struct task_struct *task
return 0;
}
+static void update_curr_idle(struct rq *rq)
+{
+}
+
/*
* Simple, special scheduling class for the per-CPU idle tasks:
*/
@@ -101,4 +105,5 @@ const struct sched_class idle_sched_class = {
.prio_changed = prio_changed_idle,
.switched_to = switched_to_idle,
+ .update_curr = update_curr_idle,
};
diff --git a/kernel/sched/stop_task.c b/kernel/sched/stop_task.c
index 67426e529f59..79ffec45a6ac 100644
--- a/kernel/sched/stop_task.c
+++ b/kernel/sched/stop_task.c
@@ -102,6 +102,10 @@ get_rr_interval_stop(struct rq *rq, struct task_struct *task)
return 0;
}
+static void update_curr_stop(struct rq *rq)
+{
+}
+
/*
* Simple, special scheduling class for the per-CPU stop tasks:
*/
@@ -128,4 +132,5 @@ const struct sched_class stop_sched_class = {
.prio_changed = prio_changed_stop,
.switched_to = switched_to_stop,
+ .update_curr = update_curr_stop,
};
next prev parent reply other threads:[~2014-11-23 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:02 Chris Mason
2014-11-23 15:56 ` Chris Mason
2014-11-23 16:11 ` Borislav Petkov
2014-11-23 16:16 ` Chris Mason
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 [this message]
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=alpine.DEB.2.11.1411232141590.6439@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=clm@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sgruszka@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®