<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/lib, branch linux-2.6.30.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-2.6.30.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-2.6.30.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2009-09-09T03:33:14Z</updated>
<entry>
<title>Make bitmask 'and' operators return a result code</title>
<updated>2009-09-09T03:33:14Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2009-08-21T16:26:15Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a2e92be0bd1e4b4c34b52e413dee30efa204d1d6'/>
<id>urn:sha1:a2e92be0bd1e4b4c34b52e413dee30efa204d1d6</id>
<content type='text'>
commit f4b0373b26567cafd421d91101852ed7a34e9e94 upstream.

When 'and'ing two bitmasks (where 'andnot' is a variation on it), some
cases want to know whether the result is the empty set or not.  In
particular, the TLB IPI sending code wants to do cpumask operations and
determine if there are any CPU's left in the final set.

So this just makes the bitmask (and cpumask) functions return a boolean
for whether the result has any bits set.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>dma-debug: fix off-by-one error in overlap function</title>
<updated>2009-07-20T03:38:51Z</updated>
<author>
<name>Joerg Roedel</name>
<email>joerg.roedel@amd.com</email>
</author>
<published>2009-06-16T10:23:58Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=1d13d53f580ce84783fc7de8a25a978b47c53757'/>
<id>urn:sha1:1d13d53f580ce84783fc7de8a25a978b47c53757</id>
<content type='text'>
commit c79ee4e466dd12347f112e2af306dca35198458f upstream.

This patch fixes a bug in the overlap function which returned true if
one region ends exactly before the second region begins. This is no
overlap but the function returned true in that case.

Reported-by: Andrew Randrianasulu &lt;randrik@mail.ru&gt;
Signed-off-by: Joerg Roedel &lt;joerg.roedel@amd.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>lib/genalloc.c: remove unmatched write_lock() in gen_pool_destroy</title>
<updated>2009-07-02T23:50:59Z</updated>
<author>
<name>Zygo Blaxell</name>
<email>zygo.blaxell@xandros.com</email>
</author>
<published>2009-06-16T22:33:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5fbba42ae4b30f9eb2a4fd87d4599e3c4cde2137'/>
<id>urn:sha1:5fbba42ae4b30f9eb2a4fd87d4599e3c4cde2137</id>
<content type='text'>
commit 8e8a2dea0ca91fe2cb7de7ea212124cfe8c82c35 upstream.

There is a call to write_lock() in gen_pool_destroy which is not balanced
by any corresponding write_unlock().  This causes problems with preemption
because the preemption-disable counter is incremented in the write_lock()
call, but never decremented by any call to write_unlock().  This bug is
gen_pool_destroy, and one of them is non-x86 arch-specific code.

Signed-off-by: Zygo Blaxell &lt;zygo.blaxell@xandros.com&gt;
Cc: Jiri Kosina &lt;trivial@kernel.org&gt;
Cc: Steve Wise &lt;swise@opengridcomputing.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>lockdep: Select frame pointers on x86</title>
<updated>2009-07-02T23:50:06Z</updated>
<author>
<name>Peter Zijlstra</name>
<email>a.p.zijlstra@chello.nl</email>
</author>
<published>2009-06-12T08:04:01Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6724112eff28f789566b8de3897607d108f3c08c'/>
<id>urn:sha1:6724112eff28f789566b8de3897607d108f3c08c</id>
<content type='text'>
commit 00540e5d54be972a94a3b2ce6da8621bebe731a2 upstream.

x86 stack traces are a piece of crap without frame pointers, and its not
like the 'performance gain' of not having stack pointers matters when you
selected lockdep.

Reported-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
LKML-Reference: &lt;new-submission&gt;
Signed-off-by: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>dma-debug: change hash_bucket_find from first-fit to best-fit</title>
<updated>2009-07-02T23:49:44Z</updated>
<author>
<name>Joerg Roedel</name>
<email>joerg.roedel@amd.com</email>
</author>
<published>2009-06-05T10:01:35Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=dfea2509864378e13b790278e6cec448342c3261'/>
<id>urn:sha1:dfea2509864378e13b790278e6cec448342c3261</id>
<content type='text'>
commit 7caf6a49bb17d0377210693af5737563b31aa5ee upstream.

Some device drivers map the same physical address multiple times to a
dma address. Without an IOMMU this results in the same dma address being
put into the dma-debug hash multiple times. With a first-fit match in
hash_bucket_find() this function may return the wrong dma_debug_entry.

This can result in false positive warnings. This patch fixes it by
changing the first-fit behavior of hash_bucket_find() into a best-fit
algorithm.

Reported-by: Torsten Kaiser &lt;just.for.lkml@googlemail.com&gt;
Reported-by: FUJITA Tomonori &lt;fujita.tomonori@lab.ntt.co.jp&gt;
Signed-off-by: Joerg Roedel &lt;joerg.roedel@amd.com&gt;
Cc: lethal@linux-sh.org
Cc: just.for.lkml@googlemail.com
Cc: hancockrwd@gmail.com
Cc: jens.axboe@oracle.com
Cc: bharrosh@panasas.com
Cc: FUJITA Tomonori &lt;fujita.tomonori@lab.ntt.co.jp&gt;
Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
LKML-Reference: &lt;20090605104132.GE24836@amd.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>cpumask: introduce zalloc_cpumask_var</title>
<updated>2009-06-09T13:00:26Z</updated>
<author>
<name>Yinghai Lu</name>
<email>yinghai@kernel.org</email>
</author>
<published>2009-06-06T21:50:36Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0281b5dc0350cbf6dd21ed558a33cccce77abc02'/>
<id>urn:sha1:0281b5dc0350cbf6dd21ed558a33cccce77abc02</id>
<content type='text'>
So can get cpumask_var with cpumask_clear

Signed-off-by: Yinghai Lu &lt;yinghai@kernel.org&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>Remove old PRINTK_DEBUG config item</title>
<updated>2009-05-09T02:22:21Z</updated>
<author>
<name>Jason Baron</name>
<email>jbaron@redhat.com</email>
</author>
<published>2009-04-22T19:49:31Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=fe0e2bb9b3ca55b78e637b1260faeaa951523959'/>
<id>urn:sha1:fe0e2bb9b3ca55b78e637b1260faeaa951523959</id>
<content type='text'>
On Tue, Apr 21, 2009 at 01:55:53PM +0200, Stefan Richter wrote:
&gt; Robert P. J. Day wrote:
&gt; &gt;   lib/Kconfig.debug:      select PRINTK_DEBUG
&gt; &gt; 
&gt; &gt; should that perhaps refer to "DYNAMIC_PRINTK_DEBUG"?  since there is
&gt; &gt; no such thing as a PRINTK_DEBUG Kconfig variable.
&gt; 
&gt; Looks like a rudiment from an earlier version of Jason's "driver core:
&gt; basic infrastructure for per-module dynamic debug messages",
&gt; http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=346e15beb5343c2eb8216d820f2ed8f150822b08
&gt; Search an LKML archive for '+#ifdef CONFIG_PRINTK_DEBUG'.
&gt; 
&gt; Jason, should it be deleted or replaced by something?

We re-named 'DYNAMIC_PRINTK_DEBUG' to 'DYNAMIC_DEBUG' in 2.6.30....
'PRINTK_DEBUG' as pointed out never existed. So, it appears to be
extraneous, and should be removed. thanks for pointing it out.

Signed-off-by: Jason Baron &lt;jbaron@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Merge branch 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip</title>
<updated>2009-05-05T19:08:20Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2009-05-05T19:08:20Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=da87bbd14299ef43848742c44dfe05fa1da5a21f'/>
<id>urn:sha1:da87bbd14299ef43848742c44dfe05fa1da5a21f</id>
<content type='text'>
* 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
  kernel/posix-cpu-timers.c: fix sparse warning
  dma-debug: remove broken dma memory leak detection for 2.6.30
  locking: Documentation: lockdep-design.txt, fix note of state bits
</content>
</entry>
<entry>
<title>dma-debug: remove broken dma memory leak detection for 2.6.30</title>
<updated>2009-04-26T16:23:56Z</updated>
<author>
<name>Joerg Roedel</name>
<email>joerg.roedel@amd.com</email>
</author>
<published>2009-04-24T12:35:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=314eeac9e35d8b934dd7a09ed3a8e00d41977b84'/>
<id>urn:sha1:314eeac9e35d8b934dd7a09ed3a8e00d41977b84</id>
<content type='text'>
The feature needs some more work because the notfier which is used to
check for pending allocations is called before the device drivers
-&gt;remove() function. Therefore this feature reports false positives.

A real fix for this issue is to introduce a new notifier event which sent
_after_ the driver has deinitialized itself. That will done for the next
kernel version.

[ Impact: reduce the scope of CONFIG_DMA_API_DEBUG=y checks ]

Signed-off-by: Joerg Roedel &lt;joerg.roedel@amd.com&gt;
Cc: iommu@lists.linux-foundation.org
LKML-Reference: &lt;1240576557-22442-1-git-send-email-joerg.roedel@amd.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>lib: find_last_bit.o needed by a module only, move it from lib to obj</title>
<updated>2009-04-24T20:28:31Z</updated>
<author>
<name>Fred Isaman</name>
<email>iisaman@citi.umich.edu</email>
</author>
<published>2009-04-23T13:40:32Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a5422a5111811401f7756345e4c237ff06cf6d1e'/>
<id>urn:sha1:a5422a5111811401f7756345e4c237ff06cf6d1e</id>
<content type='text'>
Currently, although find_last_bit is EXPORTed, it is statically linked
with the kernel and is referenced only under CONFIG_SMP.

When CONFIG_SMP is undefined and find_last_bit is referenced only by
modules, linking fails with:

  ERROR: "find_last_bit" [fs/nfs/nfs.ko] undefined!

Cc: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
Signed-off-by: Fred Isaman &lt;iisaman@citi.umich.edu&gt;
Signed-off-by: Benny Halevy &lt;bhalevy@panasas.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
