linux-kernel - RE: livepatch: change to a per-task consistency model

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]

Message-ID: <063D6719AE5E284EB5DD2968C1650D6D5F4C5254@AcuExch.aculab.com>
Date:	Tue, 24 May 2016 15:06:54 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Jiri Kosina' <jikos@...nel.org>
CC:	Josh Poimboeuf <jpoimboe@...hat.com>,
	"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
	Jessica Yu <jeyu@...hat.com>,
	Vojtech Pavlik <vojtech@...e.com>,
	Petr Mladek <pmladek@...e.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"x86@...nel.org" <x86@...nel.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	"Andy Lutomirski" <luto@...nel.org>,
	"live-patching@...r.kernel.org" <live-patching@...r.kernel.org>,
	Jiri Slaby <jslaby@...e.cz>, Miroslav Benes <mbenes@...e.cz>,
	"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
	Chris J Arges <chris.j.arges@...onical.com>
Subject: RE: livepatch: change to a per-task consistency model

From: Jiri Kosina 
> Sent: 23 May 2016 19:45
> > Related, please can we have a flag for the sleep and/or process so that
> > an uninterruptible sleep doesn't trigger the 'hung task' detector
> 
> TASK_KILLABLE

Not sure that does what I want.
It appears to allow some 'kill' actions to wake the process.
I'm sure I've looked at the 'hung task' code since 2007.

> > and also stops the process counting towards the 'load average'.
> 
> TASK_NOLOAD

Ah, that was added in May 2015.
Not surprising I didn't know about it.

I'll leave the code doing:
  set_current_state(signal_pending(current) ? TASK_UNINTERRUPTIBLE ? TASK_INTERRUPTIBLE);
for a while longer.

	David