<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/lib, branch v2.6.16</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.16</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.16'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2006-02-22T17:39:02Z</updated>
<entry>
<title>Revert mount/umount uevent removal</title>
<updated>2006-02-22T17:39:02Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2006-02-22T17:39:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fa675765afed59bb89adba3369094ebd428b930b'/>
<id>urn:sha1:fa675765afed59bb89adba3369094ebd428b930b</id>
<content type='text'>
This change reverts the 033b96fd30db52a710d97b06f87d16fc59fee0f1 commit
from Kay Sievers that removed the mount/umount uevents from the kernel.
Some older versions of HAL still depend on these events to detect when a
new device has been mounted.  These events are not correctly emitted,
and are broken by design, and so, should not be relied upon by any
future program.  Instead, the /proc/mounts file should be polled to
properly detect this kind of event.

A feature-removal-schedule.txt entry has been added, noting when this
interface will be removed from the kernel.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] iomap_copy fallout (m68k)</title>
<updated>2006-02-18T21:30:40Z</updated>
<author>
<name>Al Viro</name>
<email>viro@zeniv.linux.org.uk</email>
</author>
<published>2006-02-03T07:06:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ad6b97fc929e5844bfd1d708ab1d74d131d7960d'/>
<id>urn:sha1:ad6b97fc929e5844bfd1d708ab1d74d131d7960d</id>
<content type='text'>
added __raw_writel(), sanitized include order in iomap_copy.c

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix over-zealous tag clearing in radix_tree_delete</title>
<updated>2006-02-16T16:45:50Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2006-02-16T03:43:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=90f9dd8f72773152b69042debd6b9ed6d224703a'/>
<id>urn:sha1:90f9dd8f72773152b69042debd6b9ed6d224703a</id>
<content type='text'>
If a tag is set for a node being deleted from a radix_tree, then that
tag gets cleared from the parent of the node, even if it is set for some
siblings of the node begin deleted.

This patch changes the logic to include a test for any_tag_set similar
to the logic a little futher down.  Care is taken to ensure that
'nr_cleared_tags' remains equals to the number of entries in the 'tags'
array which are set to '0' (which means that this tag is not set in the
tree below pathp-&gt;node, and should be cleared at pathp-&gt;node and
possibly above.

[ Nick says: "Linus FYI, I was able to modify the radix tree test
  harness to catch the bug and can no longer trigger it after the fix.
  Resulting code passes all other harness tests as well of course." ]

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Acked-by: Nick Piggin &lt;npiggin@suse.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6</title>
<updated>2006-02-08T00:29:55Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@g5.osdl.org</email>
</author>
<published>2006-02-08T00:29:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=92118c739df879497b8cc5a2eb3a9dc255f01b20'/>
<id>urn:sha1:92118c739df879497b8cc5a2eb3a9dc255f01b20</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[PATCH] Fix spinlock debugging delays to not time out too early</title>
<updated>2006-02-08T00:12:33Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2006-02-07T20:58:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e0a602963485a2f109ae1521c0c55507304c63ed'/>
<id>urn:sha1:e0a602963485a2f109ae1521c0c55507304c63ed</id>
<content type='text'>
The spinlock-debug wait-loop was using loops_per_jiffy to detect too long
spinlock waits - but on fast CPUs this led to a way too fast timeout and false
messages.

The fix is to include a __delay(1) call in the loop, to correctly approximate
the intended delay timeout of 1 second.  The code assumes that every
architecture implements __delay(1) to last around 1/(loops_per_jiffy*HZ)
seconds.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Cc: Andi Kleen &lt;ak@muc.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix uevent buffer overflow in input layer</title>
<updated>2006-02-06T20:17:18Z</updated>
<author>
<name>Benjamin Herrenschmidt</name>
<email>benh@kernel.crashing.org</email>
</author>
<published>2006-01-24T23:21:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d87499ed1a3ba0f6dbcff8d91c96ef132c115d08'/>
<id>urn:sha1:d87499ed1a3ba0f6dbcff8d91c96ef132c115d08</id>
<content type='text'>
The buffer used for kobject uevent is too small for some of the events generated
by the input layer. Bump it to 2k.

Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] kobject: don't oops on null kobject.name</title>
<updated>2006-02-06T20:17:17Z</updated>
<author>
<name>Chuck Ebbert</name>
<email>76306.1226@compuserve.com</email>
</author>
<published>2006-01-13T01:02:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b365b3daf2a9e2a8b002ea9fef877af1c71513fd'/>
<id>urn:sha1:b365b3daf2a9e2a8b002ea9fef877af1c71513fd</id>
<content type='text'>
kobject_get_path() will oops if one of the component names is
NULL.  Fix that by returning NULL instead of oopsing.

Signed-off-by: Chuck Ebbert &lt;76306.1226@compuserve.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] kobject_add() must have a valid name in order to succeed.</title>
<updated>2006-02-06T20:17:17Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2006-01-20T22:08:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c171fef5c8566cf5f57877e7832fa696ecdf5228'/>
<id>urn:sha1:c171fef5c8566cf5f57877e7832fa696ecdf5228</id>
<content type='text'>
So we might as well check to verify this, and let the user know that
something is wrong if they didn't do it correctly, instead of oopsing
later on in kobject_get_name() or somewhere else.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>Merge master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6</title>
<updated>2006-02-03T16:33:06Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@g5.osdl.org</email>
</author>
<published>2006-02-03T16:33:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d6c8f6aaa1d7f68c1e6471ab0839d9047cdd159f'/>
<id>urn:sha1:d6c8f6aaa1d7f68c1e6471ab0839d9047cdd159f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[PATCH] lib: Fix bug in int_sqrt() for 64 bit longs</title>
<updated>2006-02-03T16:32:08Z</updated>
<author>
<name>Peter Williams</name>
<email>pwil3058@bigpond.net.au</email>
</author>
<published>2006-02-03T11:04:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f0c00257d63463fa9d692e632fae037d6c0e67b0'/>
<id>urn:sha1:f0c00257d63463fa9d692e632fae037d6c0e67b0</id>
<content type='text'>
The implementation of int_sqrt() assumes that longs have 32 bits.  On
systems that have 64 bit longs this will result in gross errors when the
argument to the function is greater than 2^32 - 1 on such systems.  I doubt
whether any such use is currently made of int_sqrt() but the attached patch
fixes the problem anyway.

Signed-off-by: Peter Williams &lt;pwil3058@bigpond.com.au&gt;
Cc: Dave Jones &lt;davej@codemonkey.org.uk&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
