linux-kernel - Re: [PATCH 12/13] hrtimer: create a "timer

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]

Date:	Tue, 30 Sep 2008 17:54:34 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	kosaki.motohiro@...fujitsu.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, dwmw2@...radead.org,
	drepper@...hat.com, mingo@...e.hu, tglx@...x.de
Subject: Re: [PATCH 12/13] hrtimer: create a "timer_slack" field in the task struct

Hi Arjan,

Thank you for quick responce.

> > I wonder to why PR_SET_TIMERSLACK decreasing doesn't need root
> > privilege.
> > 
> > example,
> > nice() systemcall is
> >   - nice increasing (pirority decreasing) doesn't need root privilege.
> >   - nice decreasing (priority incriasing) need root privilege.
> > 
> > So, I think time slack setting need similar one.
> > Otherwise, non-privilege user can increase power consumpsion easily
> > by PR_SET_TIMERSLACK.
> > 
> > What do you think?
> 
> setting timerslack to 0 has no real negative effects on the system on
> the one hand, on the other hand, it'll be multimedia apps and games who
> want to do this.
> 
> Requiring this type of app to be root doesn't sound like a good idea,
> especially since all you get by "cheating" is ... the exact behavior
> you ask for anyway. "Increased power consumption" isn't a root
> privilege, the app can consume much more power just by a "while (1);"
> loop for example.

Right.

But I worry about an end user can't find a application which 
spent large power comsumption.
Many laptop users think battery life is really really important.

end user can find "while(1)" app easily by top command.
but they can't find timerslack==0 app easily.

So, I can drop my proposal. but I hope you explain your expected end user usages.



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