<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include, branch v2.6.21.6</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include?h=v2.6.21.6</id>
<link rel='self' href='https://git.amat.us/linux/atom/include?h=v2.6.21.6'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2007-06-11T18:36:53Z</updated>
<entry>
<title>[PATCH] SPARC64: Fix two bugs wrt. kernel 4MB TSB.</title>
<updated>2007-06-11T18:36:53Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@sunset.davemloft.net</email>
</author>
<published>2007-06-07T05:52:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b426a33edd9a3f2254cd89faefbadab9671c742a'/>
<id>urn:sha1:b426a33edd9a3f2254cd89faefbadab9671c742a</id>
<content type='text'>
1) The TSB lookup was not using the correct hash mask.

2) It was not aligned on a boundary equal to it's size,
   which is required by the sun4v Hypervisor.

wasn't having it's return value checked, and that bug will be fixed up
as well in a subsequent changeset.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] NET: Fix BMSR_100{HALF,FULL}2 defines in linux/mii.h</title>
<updated>2007-06-11T18:36:52Z</updated>
<author>
<name>David Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2007-06-07T05:44:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d4e9e959836ba3e5e754f04424ee5feb6bc16650'/>
<id>urn:sha1:d4e9e959836ba3e5e754f04424ee5feb6bc16650</id>
<content type='text'>
Noticed by Matvejchikov Ilya.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix AF_UNIX OOPS</title>
<updated>2007-06-11T18:36:50Z</updated>
<author>
<name>David Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2007-06-07T05:28:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0b4e7af9ed68fca1a19fdc3181bf077679d4ef22'/>
<id>urn:sha1:0b4e7af9ed68fca1a19fdc3181bf077679d4ef22</id>
<content type='text'>
This combines two upstream commits to fix an OOPS with
AF_UNIX and SELINUX.

Basically, sk-&gt;sk_socket can become NULL because we access
a peer socket without any locking, so it can be shut down and
released in another thread.

Commit: d410b81b4eef2e4409f9c38ef201253fbbcc7d94
[AF_UNIX]: Make socket locking much less confusing.

The unix_state_*() locking macros imply that there is some
rwlock kind of thing going on, but the implementation is
actually a spinlock which makes the code more confusing than
it needs to be.

So use plain unix_state_lock and unix_state_unlock.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

Commit: 19fec3e807a487415e77113cb9dbdaa2da739836
[AF_UNIX]: Fix datagram connect race causing an OOPS.

Based upon an excellent bug report and initial patch by
Frederik Deweerdt.

The UNIX datagram connect code blindly dereferences other-&gt;sk_socket
via the call down to the security_unix_may_send() function.

Without locking 'other' that pointer can go NULL via unix_release_sock()
which does sock_orphan() which also marks the socket SOCK_DEAD.

So we have to lock both 'sk' and 'other' yet avoid all kinds of
potential deadlocks (connect to self is OK for datagram sockets and it
is possible for two datagram sockets to perform a simultaneous connect
to each other).  So what we do is have a "double lock" function similar
to how we handle this situation in other areas of the kernel.  We take
the lock of the socket pointer with the smallest address first in
order to avoid ABBA style deadlocks.

Once we have them both locked, we check to see if SOCK_DEAD is set
for 'other' and if so, drop everything and retry the lookup.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] acpi: fix potential call to a freed memory section.</title>
<updated>2007-06-11T18:36:50Z</updated>
<author>
<name>Aaron Durbin</name>
<email>adurbin@google.com</email>
</author>
<published>2007-05-17T05:11:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ee54ea2565da4d6ed9b33cae9a14681affe8dc3f'/>
<id>urn:sha1:ee54ea2565da4d6ed9b33cae9a14681affe8dc3f</id>
<content type='text'>
Strip __cpuinit[data] from Node &lt;-&gt; PXM routines and supporting data
structures.  Also make pxm_to_node_map and node_to_pxm_map local to the
numa acpi module.

This fixes a bug triggered by the following conditions:
- boot on a machine with a SLIT table defined
- kernel is configured w/ CONFIG_HOTPLUG_CPU=n
- cat /sys/devices/system/node/node*/distance
This will cause an oops by calling into a freed memory section.

In particular, on x86_64, __node_distance calls node_to_pxm().

Signed-off-by: Aaron Durbin &lt;adurbin@google.com&gt;
Cc: Len Brown &lt;lenb@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] x86_64: allocate sparsemem memmap above 4G</title>
<updated>2007-06-11T18:36:48Z</updated>
<author>
<name>Zou Nan hai</name>
<email>nanhai.zou@intel.com</email>
</author>
<published>2007-06-01T07:46:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ed556debe2d3409491283b1a037d9b4417ba97c1'/>
<id>urn:sha1:ed556debe2d3409491283b1a037d9b4417ba97c1</id>
<content type='text'>
On systems with huge amount of physical memory, VFS cache and memory memmap
may eat all available system memory under 4G, then the system may fail to
allocate swiotlb bounce buffer.

There was a fix for this issue in arch/x86_64/mm/numa.c, but that fix dose
not cover sparsemem model.

This patch add fix to sparsemem model by first try to allocate memmap above
4G.

Signed-off-by: Zou Nan hai &lt;nanhai.zou@intel.com&gt;
Acked-by: Suresh Siddha &lt;suresh.b.siddha@intel.com&gt;
Cc: Andi Kleen &lt;ak@suse.de&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
[chrisw: trivial backport]
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] pci_ids: update patch for Intel ICH9M</title>
<updated>2007-06-11T18:36:48Z</updated>
<author>
<name>Jason Gaston</name>
<email>jason.d.gaston@intel.com</email>
</author>
<published>2007-06-01T07:46:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6f554bd3f4b0aa6d7d0116fe993bd2516783f872'/>
<id>urn:sha1:6f554bd3f4b0aa6d7d0116fe993bd2516783f872</id>
<content type='text'>
This patch updates the Intel ICH9M LPC Controller DID's, due to a
specification change.

Signed-off-by: Jason Gaston &lt;jason.d.gaston@intel.com&gt;
Cc: &lt;stable@kernel.org&gt;
Cc: Greg KH &lt;greg@kroah.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: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] PCI: quirk disable MSI on via vt3351</title>
<updated>2007-06-11T18:36:47Z</updated>
<author>
<name>Jay Cliburn</name>
<email>jacliburn@bellsouth.net</email>
</author>
<published>2007-05-26T22:01:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f3eeb487a026e25cc00aed0ae4892c7eeb7955d6'/>
<id>urn:sha1:f3eeb487a026e25cc00aed0ae4892c7eeb7955d6</id>
<content type='text'>
The Via VT3351 APIC does not play well with MSI and unleashes a flood
of APIC errors when MSI is used to deliver interrupts.  The problem
was recently exposed when the atl1 network device driver, which enables
MSI by default, stimulated APIC errors on an Asus M2V mainboard, which
employs the Via VT3351.
See http://bugzilla.kernel.org/show_bug.cgi?id=8472 for additional
details on this bug.

Signed-off-by: Jay Cliburn &lt;jacliburn@bellsouth.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] make freezeable workqueues singlethread</title>
<updated>2007-06-11T18:36:45Z</updated>
<author>
<name>Oleg Nesterov</name>
<email>oleg@tv-sign.ru</email>
</author>
<published>2007-05-21T20:51:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=aa2112f41c593ea73d7b99ecaa8d4cb60fe37404'/>
<id>urn:sha1:aa2112f41c593ea73d7b99ecaa8d4cb60fe37404</id>
<content type='text'>
It is a known fact that freezeable multithreaded workqueues doesn't like
CPU_DEAD. We keep them only for the incoming CPU-hotplug rework.

Sadly, we can't just kill create_freezeable_workqueue() right now, make
them singlethread.

Signed-off-by: Oleg Nesterov &lt;oleg@tv-sign.ru&gt;
Cc: "Rafael J. Wysocki" &lt;rjw@sisk.pl&gt;
Cc: Gautham R Shenoy &lt;ego@in.ibm.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: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: Don't write more than is required of the last page of a bitmap</title>
<updated>2007-06-11T18:36:44Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2007-05-21T01:33:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ae9e80bd6e189ce3947df348a06d6178fc323f9d'/>
<id>urn:sha1:ae9e80bd6e189ce3947df348a06d6178fc323f9d</id>
<content type='text'>
It is possible that real data or metadata follows the bitmap
without full page alignment.
So limit the last write to be only the required number of bytes,
rounded up to the hard sector size of the device.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] SPARC64: Bump PROMINTR_MAX to 32.</title>
<updated>2007-05-23T21:32:52Z</updated>
<author>
<name>David Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2007-05-15T08:42:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8492a8ba651bff5fdba0b0a4c8dadde6909bd72d'/>
<id>urn:sha1:8492a8ba651bff5fdba0b0a4c8dadde6909bd72d</id>
<content type='text'>
Some devices have more than 15 which was the previous
setting.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
</feed>
