From: Tejun Heo <tj@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Pavel Machek <pavel@ucw.cz>,
linux-pm@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
LKML <linux-kernel@vger.kernel.org>,
Colin Cross <ccross@android.com>
Subject: Re: [RFC PATCH] freezer: allow killing of frozen tasks
Date: Tue, 20 Aug 2013 08:27:27 -0400 [thread overview]
Message-ID: <20130820122727.GC3926@htj.dyndns.org> (raw)
In-Reply-To: <7346644.tueXegsfXu@vostro.rjw.lan>
On Tue, Aug 20, 2013 at 02:34:14PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, August 20, 2013 08:22:00 AM Tejun Heo wrote:
> > On Tue, Aug 20, 2013 at 02:30:18PM +0200, Rafael J. Wysocki wrote:
> > > > So, I don't think we can simply turn TASK_UNITERRUPTIBLE to
> > > > TASK_KILLABLE at this point. We really need to strictly define where
> > > > a task can freeze before being able to do anything like this.
> > >
> > > But we could do that for user space tasks I suppose?
> >
> > Even for userland tasks, we don't know where the task is stuck at. I
> > think there are enough freeze points in the kernel which are in the
> > middle of something which can be used by userland tasks excuting some
> > syscall. We need to collect all those sites into well defined trap
> > points before doing this.
>
> OK, thanks!
I scanned through try_to_freeze() users and it seems like we don't
have that many which can be hit by userland tasks. I think it should
be doable to audit all the users, remove the ones which can be invoked
by userland and make try_to_freeze() whine loudly if it's running off
a userland task except from well-defined spots. Anyways, we need to
ensure that userland task doesn't get stuck deep in the kernel before
allowing this.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-08-20 12:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 11:20 [RFC PATCH] freezer: allow killing of frozen tasks Bartlomiej Zolnierkiewicz
2013-08-20 12:23 ` Rafael J. Wysocki
2013-08-20 12:18 ` Tejun Heo
2013-08-20 12:30 ` Rafael J. Wysocki
2013-08-20 12:22 ` Tejun Heo
2013-08-20 12:34 ` Rafael J. Wysocki
2013-08-20 12:27 ` Tejun Heo [this message]
2013-08-20 12:41 ` Rafael J. Wysocki
2013-09-25 5:52 ` Kyungmin Park
2013-09-25 8:07 ` Rafael J. Wysocki
2013-09-26 1:46 ` Colin Cross
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=20130820122727.GC3926@htj.dyndns.org \
--to=tj@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=ccross@android.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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