<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/connector/cn_proc.c, branch linux-3.11.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.11.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.11.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2013-11-04T12:35:13Z</updated>
<entry>
<title>proc connector: fix info leaks</title>
<updated>2013-11-04T12:35:13Z</updated>
<author>
<name>Mathias Krause</name>
</author>
<published>2013-09-30T20:03:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=067cb429b87e651f83329ef4a86b997c0688cb81'/>
<id>urn:sha1:067cb429b87e651f83329ef4a86b997c0688cb81</id>
<content type='text'>
[ Upstream commit e727ca82e0e9616ab4844301e6bae60ca7327682 ]

Initialize event_data for all possible message types to prevent leaking
kernel stack contents to userland (up to 20 bytes). Also set the flags
member of the connector message to 0 to prevent leaking two more stack
bytes this way.

Signed-off-by: Mathias Krause &lt;minipli@googlemail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>connector: Added coredumping event to the process connector</title>
<updated>2013-03-20T17:23:21Z</updated>
<author>
<name>Jesper Derehag</name>
</author>
<published>2013-03-19T20:50:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2b5faa4c553f90ee2dde1d976b220b1ca9741ef0'/>
<id>urn:sha1:2b5faa4c553f90ee2dde1d976b220b1ca9741ef0</id>
<content type='text'>
Process connector can now also detect coredumping events.

Main aim of patch is get notified at start of coredumping, instead of
having to wait for it to finish and then being notified through EXIT
event.

Could be used for instance by process-managers that want to get
notified as soon as possible about process failures, and not
necessarily beeing notified after coredump, which could be in the
order of minutes depending on size of coredump, piping and so on.

Signed-off-by: Jesper Derehag &lt;jderehag@hotmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>proc connector: reject unprivileged listener bumps</title>
<updated>2013-02-27T18:08:35Z</updated>
<author>
<name>Kees Cook</name>
</author>
<published>2013-02-25T21:32:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e70ab977991964a5a7ad1182799451d067e62669'/>
<id>urn:sha1:e70ab977991964a5a7ad1182799451d067e62669</id>
<content type='text'>
While PROC_CN_MCAST_LISTEN/IGNORE is entirely advisory, it was possible
for an unprivileged user to turn off notifications for all listeners by
sending PROC_CN_MCAST_IGNORE. Instead, require the same privileges as
required for a multicast bind.

Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Cc: Evgeniy Polyakov &lt;zbr@ioremap.net&gt;
Cc: Matt Helsley &lt;matthltc@us.ibm.com&gt;
Cc: stable@vger.kernel.org
Acked-by: Evgeniy Polyakov &lt;zbr@ioremap.net&gt;
Acked-by: Matt Helsley &lt;matthltc@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>userns: Convert process event connector to handle kuids and kgids</title>
<updated>2012-09-07T02:37:10Z</updated>
<author>
<name>Eric W. Biederman</name>
</author>
<published>2012-02-08T00:48:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9582d90196aa879e6acf866f02a1adead08707b5'/>
<id>urn:sha1:9582d90196aa879e6acf866f02a1adead08707b5</id>
<content type='text'>
- Only allow asking for events from the initial user and pid namespace,
  where we generate the events in.

- Convert kuids and kgids into the initial user namespace to report
  them via the process event connector.

Cc: David Miller &lt;davem@davemloft.net&gt;
Acked-by: Evgeniy Polyakov &lt;zbr@ioremap.net&gt;
Acked-by: Serge Hallyn &lt;serge.hallyn@canonical.com&gt;
Signed-off-by: Eric W. Biederman &lt;ebiederm@xmission.com&gt;
</content>
</entry>
<entry>
<title>drivers: connector: fixed coding style issues</title>
<updated>2012-07-17T06:23:52Z</updated>
<author>
<name>Valentin Ilie</name>
</author>
<published>2012-07-14T13:08:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f3c48ecce56df6168be07377bf32bba88314b14c'/>
<id>urn:sha1:f3c48ecce56df6168be07377bf32bba88314b14c</id>
<content type='text'>
V2: Replaced assignment in if statement.
Fixed coding style issues.

Signed-off-by: Valentin Ilie &lt;valentin.ilie@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>connector: add comm change event report to proc connector</title>
<updated>2011-09-28T17:41:50Z</updated>
<author>
<name>Vladimir Zapolskiy</name>
</author>
<published>2011-09-21T09:26:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f786ecba4158880f8cdc0ebb93e7d78e6c125449'/>
<id>urn:sha1:f786ecba4158880f8cdc0ebb93e7d78e6c125449</id>
<content type='text'>
Add an event to monitor comm value changes of tasks.  Such an event
becomes vital, if someone desires to control threads of a process in
different manner.

A natural characteristic of threads is its comm value, and helpfully
application developers have an opportunity to change it in runtime.
Reporting about such events via proc connector allows to fine-grain
monitoring and control potentials, for instance a process control daemon
listening to proc connector and following comm value policies can place
specific threads to assigned cgroup partitions.

It might be possible to achieve a pale partial one-shot likeness without
this update, if an application changes comm value of a thread generator
task beforehand, then a new thread is cloned, and after that proc
connector listener gets the fork event and reads new thread's comm value
from procfs stat file, but this change visibly simplifies and extends the
matter.

Signed-off-by: Vladimir Zapolskiy &lt;vzapolskiy@gmail.com&gt;
Acked-by: Evgeniy Polyakov &lt;zbr@ioremap.net&gt;
Cc: David Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Andrew Morton &lt;akpm@google.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>proc_fork_connector: a lockless -&gt;real_parent usage is not safe</title>
<updated>2011-07-29T01:26:32Z</updated>
<author>
<name>Oleg Nesterov</name>
</author>
<published>2011-07-29T01:26:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9e8f90dfe58eb19140bc66655170c7aef9eadbf2'/>
<id>urn:sha1:9e8f90dfe58eb19140bc66655170c7aef9eadbf2</id>
<content type='text'>
proc_fork_connector() uses -&gt;real_parent lockless.  This is not safe if
copy_process() was called with CLONE_THREAD or CLONE_PARENT, in this case
the parent != current can go away at any moment.

Signed-off-by: Oleg Nesterov &lt;oleg@redhat.com&gt;
Cc: Vladimir Zapolskiy &lt;vzapolskiy@gmail.com&gt;
Cc: "David S. Miller" &lt;davem@davemloft.net&gt;
Cc: Evgeniy Polyakov &lt;zbr@ioremap.net&gt;
Cc: Evgeniy Polyakov &lt;johnpol@2ka.mipt.ru&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>atomic: use &lt;linux/atomic.h&gt;</title>
<updated>2011-07-26T23:49:47Z</updated>
<author>
<name>Arun Sharma</name>
</author>
<published>2011-07-26T23:09:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=60063497a95e716c9a689af3be2687d261f115b4'/>
<id>urn:sha1:60063497a95e716c9a689af3be2687d261f115b4</id>
<content type='text'>
This allows us to move duplicated code in &lt;asm/atomic.h&gt;
(atomic_inc_not_zero() for now) to &lt;linux/atomic.h&gt;

Signed-off-by: Arun Sharma &lt;asharma@fb.com&gt;
Reviewed-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Cc: Ingo Molnar &lt;mingo@elte.hu&gt;
Cc: David Miller &lt;davem@davemloft.net&gt;
Cc: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Acked-by: Mike Frysinger &lt;vapier@gentoo.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>drivers/connector/cn_proc.c: remove unused local</title>
<updated>2011-07-26T03:57:17Z</updated>
<author>
<name>Andrew Morton</name>
</author>
<published>2011-07-26T00:13:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f19da2ce8ef5e49b8b8ea199c3601dd45d71b262'/>
<id>urn:sha1:f19da2ce8ef5e49b8b8ea199c3601dd45d71b262</id>
<content type='text'>
Fix the warning

  drivers/connector/cn_proc.c: In function 'proc_ptrace_connector':
  drivers/connector/cn_proc.c:176: warning: unused variable 'tracer'

Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>connector: add an event for monitoring process tracers</title>
<updated>2011-07-18T19:38:33Z</updated>
<author>
<name>Vladimir Zapolskiy</name>
</author>
<published>2011-07-15T17:45:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f701e5b73a1a79ea62ffd45d9e2bed4c7d5c1fd2'/>
<id>urn:sha1:f701e5b73a1a79ea62ffd45d9e2bed4c7d5c1fd2</id>
<content type='text'>
This change adds a procfs connector event, which is emitted on every
successful process tracer attach or detach.

If some process connects to other one, kernelspace connector reports
process id and thread group id of both these involved processes. On
disconnection null process id is returned.

Such an event allows to create a simple automated userspace mechanism
to be aware about processes connecting to others, therefore predefined
process policies can be applied to them if needed.

Note, a detach signal is emitted only in case, if a tracer process
explicitly executes PTRACE_DETACH request. In other cases like tracee
or tracer exit detach event from proc connector is not reported.

Signed-off-by: Vladimir Zapolskiy &lt;vzapolskiy@gmail.com&gt;
Acked-by: Evgeniy Polyakov &lt;zbr@ioremap.net&gt;
Cc: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Oleg Nesterov &lt;oleg@redhat.com&gt;
</content>
</entry>
</feed>
