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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 22 May 2014 16:05:30 -0700
From:	Kees Cook <>
Cc:	Kees Cook <>,
	Andy Lutomirski <>,
	Oleg Nesterov <>,
	Alexander Viro <>,
	Peter Zijlstra <>,
	James Morris <>,
	Eric Paris <>,
	Juri Lelli <>,
	John Stultz <>,
	"David S. Miller" <>,
	Daniel Borkmann <>,
	Alex Thorlton <>,
	Rik van Riel <>,
	Daeseok Youn <>,
	David Rientjes <>,
	"Eric W. Biederman" <>,
	Dario Faggioli <>,
	Rashika Kheria <>,
	liguang <>,
	Geert Uytterhoeven <>,,
Subject: [PATCH v5 0/6] seccomp: add PR_SECCOMP_EXT and SECCOMP_EXT_ACT_TSYNC

This adds the ability for threads to request seccomp filter
synchronization across their thread group (either at filter attach time
or later). (For example, for Chrome to make sure graphic driver threads
are fully confined after seccomp filters have been attached.)

To support this, seccomp locking on writes is introduced, along with
refactoring of no_new_privs. Races with thread creation are handled via
the tasklist_list.

I think all the concerns raised during the discussion[1] of the first
version of this patch have been addressed. However, the races involved
have tricked me before. :)




 - move includes around (drysdale)
 - drop set_nnp return value (luto)
 - use smp_load_acquire/store_release (luto)
 - merge nnp changes to seccomp always, fewer ifdef (luto)
 - cleaned up locking further, as noticed by David Drysdale
 - added SECCOMP_EXT_ACT_FILTER for new filter install options
 - reworked to avoid clone races

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists