linux-kernel - Re: [PATCH] Set bounds on what /proc/self/make-it-fail accepts.

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:	Wed, 19 Feb 2014 14:07:50 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: [PATCH] Set bounds on what /proc/self/make-it-fail accepts.

On Wed, 19 Feb 2014, Andrew Morton wrote:

> If we're touching the task_struct we could make it a bool.
> 
> Or just a single bit(field).  task_struct already has a bunch of
> bitfields in it (strangely, they aren't contiguous).  But some locking
> would be needed if tasks-other-than-current can modify the bit.
> 

Or store to any adjacent bit in the word.  I think the simplest solution 
is to use kstrtoint() and test for val == !!val since, as we all know, 
{simple,strict}_strto* is deprecated per checkpatch :)
--
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/