linux-kernel - Re: [PATCH] sched: allow unsetting SCHED_RESET_ON

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <507F25F3.1010301@canonical.com>
Date:	Wed, 17 Oct 2012 23:41:07 +0200
From:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
To:	Lennart Poettering <lennart@...ttering.net>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sched: allow unsetting SCHED_RESET_ON_FORK when new policy
 is not realtime

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/