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:	Thu, 4 Aug 2016 10:08:46 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Aravinda Prasad <aravinda@...ux.vnet.ibm.com>
Cc:	Hari Bathini <hbathini@...ux.vnet.ibm.com>, daniel@...earbox.net,
	peterz@...radead.org, linux-kernel@...r.kernel.org,
	acme@...nel.org, alexander.shishkin@...ux.intel.com,
	mingo@...hat.com, paulus@...ba.org, ebiederm@...ssion.com,
	kernel@...p.com, viro@...iv.linux.org.uk, ananth@...ibm.com
Subject: Re: [RFC PATCH v2 2/3] tracefs: add instances support for uprobe
 events

On Thu, 4 Aug 2016 19:16:03 +0530
Aravinda Prasad <aravinda@...ux.vnet.ibm.com> wrote:


> Separation is based on the context in which the function is called.
> Hence, containers can see only those kernel functions that are
> triggered/invoked by the processes running inside that container and
> should not see other kernel functions, for example, called by RCU grace
> period kthread or any other kthread.
> 

What about interrupts and softirqs? They run under the container
process's context, but service other processes outside the container.
Same goes for trace events.

-- Steve

Powered by blists - more mailing lists