<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/kernel, branch v2.6.14.5</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/kernel?h=v2.6.14.5</id>
<link rel='self' href='https://git.amat.us/linux/atom/kernel?h=v2.6.14.5'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2005-12-27T00:08:58Z</updated>
<entry>
<title>[PATCH] kernel/params.c: fix sysfs access with CONFIG_MODULES=n</title>
<updated>2005-12-27T00:08:58Z</updated>
<author>
<name>Jason Wessel</name>
<email>jason.wessel@windriver.com</email>
</author>
<published>2005-12-20T22:41:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eec59235580a82f31ec66e066666332b804b0714'/>
<id>urn:sha1:eec59235580a82f31ec66e066666332b804b0714</id>
<content type='text'>
All the work was done to setup the file and maintain the file handles but
the access functions were zeroed out due to the #ifdef.  Removing the
#ifdef allows full access to all the parameters when CONFIG_MODULES=n.

akpm: put it back again, but use CONFIG_SYSFS instead.

This patch has already been included in Linus' tree.

Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Add try_to_freeze to kauditd</title>
<updated>2005-12-14T23:43:00Z</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2005-12-12T18:03:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=97086d3e713e1175c4a83fc3c8bbcd8d8ac8578d'/>
<id>urn:sha1:97086d3e713e1175c4a83fc3c8bbcd8d8ac8578d</id>
<content type='text'>
kauditd was causing suspends to fail because it refused to freeze.  Adding
a try_to_freeze() to its sleep loop solves the issue.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
Acked-by: Pavel Machek &lt;pavel@suse.cz&gt;
Cc: David Woodhouse &lt;dwmw2@infradead.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix crash when ptrace poking hugepage areas</title>
<updated>2005-12-14T23:42:54Z</updated>
<author>
<name>David Gibson</name>
<email>david@gibson.dropbear.id.au</email>
</author>
<published>2005-11-30T03:46:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d948e779d14768cee4077ad5b477d58d42b20371'/>
<id>urn:sha1:d948e779d14768cee4077ad5b477d58d42b20371</id>
<content type='text'>
set_page_dirty() will not cope with being handed a page * which is part of
a compound page, but not the master page in that compound page.  This case
can occur via access_process_vm() if you attemp to write to another
process's hugepage memory area using ptrace() (causing an oops or hang).

This patch fixes the bug by only calling set_page_dirty() from
access_process_vm() if the page is not a compound page.  We already use a
similar fix in bio_set_pages_dirty() for the case of direct io to
hugepages.

Signed-off-by: David Gibson &lt;david@gibson.dropbear.id.au&gt;
Acked-by: William Irwin &lt;wli@holomorphy.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Don't auto-reap traced children</title>
<updated>2005-11-24T22:10:07Z</updated>
<author>
<name>Oleg Nesterov</name>
<email>oleg@tv-sign.ru</email>
</author>
<published>2005-11-10T14:22:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=423885efc678eec81b59e4c200417be58ede9d2f'/>
<id>urn:sha1:423885efc678eec81b59e4c200417be58ede9d2f</id>
<content type='text'>
If a task is being traced we never auto-reap it even if it might look
like its parent doesn't care. The tracer obviously _does_ care.

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix ptrace self-attach rule</title>
<updated>2005-11-11T05:22:08Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@osdl.org</email>
</author>
<published>2005-11-09T19:37:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=082d52c56f642d21b771a13221068d40915a1409'/>
<id>urn:sha1:082d52c56f642d21b771a13221068d40915a1409</id>
<content type='text'>
Before we did CLONE_THREAD, the way to check whether we were attaching
to ourselves was to just check "current == task", but with CLONE_THREAD
we should check that the thread group ID matches instead.

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] - fix signal-&gt;live leak in copy_process()</title>
<updated>2005-11-11T05:18:55Z</updated>
<author>
<name>Oleg Nesterov</name>
<email>oleg@tv-sign.ru</email>
</author>
<published>2005-11-09T18:22:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d212503f82d7ef3b63ed20ab97bb68a69616d06c'/>
<id>urn:sha1:d212503f82d7ef3b63ed20ab97bb68a69616d06c</id>
<content type='text'>
exit_signal() (called from copy_process's error path) should decrement
-&gt;signal-&gt;live, otherwise forking process will miss 'group_dead' in
do_exit().

Signed-off-by: Oleg Nesterov &lt;oleg@tv-sign.ru&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] CVE-2005-2709 sysctl unregistration oops</title>
<updated>2005-11-08T19:14:00Z</updated>
<author>
<name>Al Viro</name>
<email>viro@zeniv.linux.org.uk</email>
</author>
<published>2005-11-08T15:03:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e4e0411221c7d4f2bd82fa5e21745f927a1bff28'/>
<id>urn:sha1:e4e0411221c7d4f2bd82fa5e21745f927a1bff28</id>
<content type='text'>
You could open the /proc/sys/net/ipv4/conf/&lt;if&gt;/&lt;whatever&gt; file, then
wait for interface to go away, try to grab as much memory as possible in
hope to hit the (kfreed) ctl_table.  Then fill it with pointers to your
function. Then do read from file you've opened and if you are lucky,
you'll get it called as -&gt;proc_handler() in kernel mode.

So this is at least an Oops and possibly more.  It does depend on an
interface going away though, so less of a security risk than it would
otherwise be.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Yet more posix-cpu-timer fixes</title>
<updated>2005-10-27T16:08:43Z</updated>
<author>
<name>Roland McGrath</name>
<email>roland@redhat.com</email>
</author>
<published>2005-10-27T10:16:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=72ab373a5688a78cbdaf3bf96012e597d5399bb7'/>
<id>urn:sha1:72ab373a5688a78cbdaf3bf96012e597d5399bb7</id>
<content type='text'>
This just makes sure that a thread's expiry times can't get reset after
it clears them in do_exit.

This is what allowed us to re-introduce the stricter BUG_ON() check in
a362f463a6d316d14daed0f817e151835ce97ff7.

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>Revert "remove false BUG_ON() from run_posix_cpu_timers()"</title>
<updated>2005-10-27T16:07:33Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@g5.osdl.org</email>
</author>
<published>2005-10-27T16:07:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a362f463a6d316d14daed0f817e151835ce97ff7'/>
<id>urn:sha1:a362f463a6d316d14daed0f817e151835ce97ff7</id>
<content type='text'>
This reverts commit 3de463c7d9d58f8cf3395268230cb20a4c15bffa.

Roland has another patch that allows us to leave the BUG_ON() in place
by just making sure that the condition it tests for really is always
true.

That goes in next.

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix cpu timers expiration time</title>
<updated>2005-10-26T22:21:14Z</updated>
<author>
<name>Oleg Nesterov</name>
<email>oleg@tv-sign.ru</email>
</author>
<published>2005-10-26T16:26:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7a4ed937aa44acdeb8c6ba671509dc7b54b09d3a'/>
<id>urn:sha1:7a4ed937aa44acdeb8c6ba671509dc7b54b09d3a</id>
<content type='text'>
There's a silly off-by-one error in the code that updates the expiration
of posix CPU timers, causing them to not be properly updated when they
hit exactly on their expiration time (which should be the normal case).

This causes them to then fire immediately again, and only _then_ get
properly updated.

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
