linux-kernel - Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 01 Feb 2008 13:09:56 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper
	(bisected)


On Fri, 2008-02-01 at 12:50 +0100, Rafael J. Wysocki wrote:
> On Friday, 1 of February 2008, Peter Zijlstra wrote:

> > > It arts run as root, or does it use RLIMIT_RTPRIO to allow users to
> > > execute realtime tasks?
> 
> artswrapper is setuid root and RLIMIT_RTPRIO is apparently not used.
> Still, artswrapper is running as a regular user, so it most probably drops
> privileges early.
> 
> BTW, it fails while running the artsmessage utility used for displaying arts
> error messages, so I guess there's an error in arts that this thing tries to
> display and deadlocks (or something like that).
> 
> Should I test the patch nevertheless?

Don't think that would help any in this situation. The thing to look out
for are RT tasks running with a different uid than 0.

This patch would only stop a task from obtaining RT class scheduling
when already in a (misconfigured) group. If the task is RT and then
switches group another - similar - thing is needed.

Does this artsmessage thing also run with RT priority?



--
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/