LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)
Date: Sat, 2 Feb 2008 00:39:58 +0100	[thread overview]
Message-ID: <200802020040.05519.rjw@sisk.pl> (raw)
In-Reply-To: <1201867797.32654.52.camel@lappy>

On Friday, 1 of February 2008, Peter Zijlstra wrote:
> 
> 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?

Well, it's in a strange state (after it's broken).  From top:

PR = -51
NI = 0
S = R
%CPU = 0.0
%MEM = 0.0

Here's the corresponding trace from sysrq+t:

artswrapper   R  running task     5128  5776      1
 ffff81007a8dbd88 0000000000000046 000000015c4321b0 ffff81006aa6e5c8
 ffffffff806daa00 ffffffff806daa00 ffffffff806daa00 ffffffff806daa00
 ffffffff806daa00 ffffffff806daa00 ffffffff806d7a60 ffffffff806daa00
Call Trace:
 [<ffffffff8022fdb7>] ? try_to_wake_up+0x77/0x200
 [<ffffffff8023573d>] __cond_resched+0x2d/0x60
 [<ffffffff804ddce1>] _cond_resched+0x31/0x40
 [<ffffffff804ddd24>] wait_for_common+0x34/0x170
 [<ffffffff8022fdb7>] ? try_to_wake_up+0x77/0x200
 [<ffffffff804ddec8>] wait_for_completion+0x18/0x20
 [<ffffffff80235aba>] sched_exec+0xba/0xf0
 [<ffffffff802b5a64>] do_execve+0x64/0x220
 [<ffffffff802097c6>] sys_execve+0x46/0x70
 [<ffffffff8020bab7>] stub_execve+0x67/0xb0

  reply	other threads:[~2008-02-01 23:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:37 Rafael J. Wysocki
2008-02-01  2:04 ` Rafael J. Wysocki
2008-02-01  7:44   ` Peter Zijlstra
2008-02-01  9:50     ` Peter Zijlstra
2008-02-01 11:50       ` Rafael J. Wysocki
2008-02-01 12:09         ` Peter Zijlstra
2008-02-01 23:39           ` Rafael J. Wysocki [this message]
2008-02-05 21:46             ` Dmitry Adamushko
2008-02-06  1:21               ` Rafael J. Wysocki
     [not found] ` <b647ffbd0802060040wbfe16afq4355e8f4f31ab06b@mail.gmail.com>
     [not found]   ` <1202288548.19243.47.camel@lappy>
2008-02-06 18:25     ` Rafael J. Wysocki
2008-02-06 21:43       ` Peter Zijlstra
2008-02-06 21:50         ` Rafael J. Wysocki
2008-02-06 22:01           ` Peter Zijlstra
2008-02-06 22:18             ` Rafael J. Wysocki
2008-02-06 22:34               ` Peter Zijlstra
2008-02-06 23:31                 ` Rafael J. Wysocki
2008-02-06 23:34                   ` Ingo Molnar
2008-02-07 19:53                     ` Rafael J. Wysocki
2008-02-07 21:20                       ` Peter Zijlstra
2008-02-10 12:30                     ` Rafael J. Wysocki

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=200802020040.05519.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --subject='Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).