From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Lennart Poettering <lennart@poettering.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: allow unsetting SCHED_RESET_ON_FORK when new policy is not realtime
Date: Wed, 17 Oct 2012 23:41:07 +0200 [thread overview]
Message-ID: <507F25F3.1010301@canonical.com> (raw)
In-Reply-To: <507F20AC.6000308@canonical.com>
Op 17-10-12 23:18, Maarten Lankhorst schreef:
> When implementing SIGXCPU handling for a thread boosted with rtkit to realtime
> priority, I noticed that sched_setscheduler(somepid, SCHED_OTHER) would return
> -EPERM because the thread was previously SCHED_RR | SCHED_RESET_ON_FORK,
> and looking from the code that flag cannot be reset without sufficient rights.
>
Argh must not send patches right before going to bed, this leaves open a hole
if current policy is sched_idle and when nice level is at a privileged level still..
Not that I've ever seen nice level do anything. Will resend after I've had some sleep.
~Maarten
prev parent reply other threads:[~2012-10-17 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 21:18 [PATCH] sched: allow unsetting SCHED_RESET_ON_FORK when new policy is not realtime Maarten Lankhorst
2012-10-17 21:41 ` Maarten Lankhorst [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=507F25F3.1010301@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.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.