<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include, branch v2.6.16.52</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include?h=v2.6.16.52</id>
<link rel='self' href='https://git.amat.us/linux/atom/include?h=v2.6.16.52'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2007-05-22T22:41:22Z</updated>
<entry>
<title>[NETPOLL]: Fix TX queue overflow in trapped mode.</title>
<updated>2007-05-22T22:41:22Z</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2007-05-22T22:41:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eb9c87a4768bd759c80026e41fa5540ee110131e'/>
<id>urn:sha1:eb9c87a4768bd759c80026e41fa5540ee110131e</id>
<content type='text'>
CONFIG_NETPOLL_TRAP causes the TX queue controls to be completely bypassed in
the netpoll's "trapped" mode which easily causes overflows in the drivers with
short TX queues (most notably, in 8139too with its 4-deep queue).  So, make
this option more sensible by making it only bypass the TX softirq wakeup.

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Acked-by: Jeff Garzik &lt;jgarzik@pobox.com&gt;
Acked-by: Tom Rini &lt;trini@kernel.crashing.org&gt;
Acked-by: Matt Mackall &lt;mpm@selenic.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>[NETFILTER]: ip_nat_proto_gre: do not modify/corrupt GREv0 packets through NAT</title>
<updated>2007-05-03T23:00:32Z</updated>
<author>
<name>Jorge Boncompte</name>
<email>jorge@dti2.net</email>
</author>
<published>2007-05-03T23:00:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c5807ace66d5085ed94608a7e9a084085ea57ede'/>
<id>urn:sha1:c5807ace66d5085ed94608a7e9a084085ea57ede</id>
<content type='text'>
While porting some changes of the 2.6.21-rc7 pptp/proto_gre conntrack
and nat modules to a 2.4.32 kernel I noticed that the gre_key function
returns a wrong pointer to the GRE key of a version 0 packet thus
corrupting the packet payload.

The intended behaviour for GREv0 packets is to act like
ip_conntrack_proto_generic/ip_nat_proto_unknown so I have ripped the
offending functions (not used anymore) and modified the
ip_nat_proto_gre modules to not touch version 0 (non PPTP) packets.

Signed-off-by: Jorge Boncompte &lt;jorge@dti2.net&gt;
Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>[IPV6]: Disallow RH0 by default (CVE-2007-2242)</title>
<updated>2007-04-30T23:31:47Z</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@stusta.de</email>
</author>
<published>2007-04-30T23:31:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5225791117b564cd8b5683cf82d9eea45b0f0d59'/>
<id>urn:sha1:5225791117b564cd8b5683cf82d9eea45b0f0d59</id>
<content type='text'>
A security issue is emerging.  Disallow Routing Header Type 0 by default
as we have been doing for IPv4.

This version already includes a fix for the original patch.

Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>V4L: saa7146: Fix allocation of clipping memory</title>
<updated>2007-04-13T20:58:25Z</updated>
<author>
<name>Oliver Endriss</name>
<email>o.endriss@gmx.de</email>
</author>
<published>2007-04-13T19:23:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2d51ccdd501e620b3c323f4df3f07a6e5d03ea6d'/>
<id>urn:sha1:2d51ccdd501e620b3c323f4df3f07a6e5d03ea6d</id>
<content type='text'>
Olaf Hering pointed out that SAA7146_CLIPPING_MEM would become
very large for PAGE_SIZE &gt; 4K.

In fact, the number of clipping windows is limited to 16,
and calculate_clipping_registers_rect() does not use more
than 256 bytes. SAA7146_CLIPPING_MEM adjusted accordingly.

(cherry picked from commit 7a7cd1920969dd9da4e0d99aab573b3eba24c799)

Thanks-to: Olaf Hering &lt;olaf@aepfle.de&gt;
Signed-off-by: Oliver Endriss &lt;o.endriss@gmx.de&gt;
Signed-off-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>fix MTIME_SEC_MAX on 32-bit</title>
<updated>2007-04-08T22:54:30Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2007-04-08T22:54:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=19b5054d01f856a189659a59b24c8497b038cb43'/>
<id>urn:sha1:19b5054d01f856a189659a59b24c8497b038cb43</id>
<content type='text'>
The maximum seconds value we can handle on 32bit is LONG_MAX.

Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>prevent timespec/timeval to ktime_t overflow</title>
<updated>2007-04-08T22:03:30Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2007-04-08T22:03:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=812b03dc31229847825989f5e35359a7c4dff6f4'/>
<id>urn:sha1:812b03dc31229847825989f5e35359a7c4dff6f4</id>
<content type='text'>
Frank v.  Waveren pointed out that on 64bit machines the timespec to
ktime_t conversion might overflow.  This is also true for timeval to
time_t conversions.  This breaks a "sleep inf" on 64bit machines.

While a timespec/timeval with tx.sec = MAX_LONG is valid by specification
the internal representation of ktime_t is based on nanoseconds.  The
conversion of seconds to nanoseconds overflows for seconds values &gt;=
(MAX_LONG / NSEC_PER_SEC).

Check the seconds argument to the conversion and limit it to the maximum
time which can be represented by ktime_t.

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>[IFB]: Fix crash on input device removal</title>
<updated>2007-04-03T02:03:55Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2007-04-03T02:03:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5f4a9d1b7a413d6aac382c51692ac0df785068c5'/>
<id>urn:sha1:5f4a9d1b7a413d6aac382c51692ac0df785068c5</id>
<content type='text'>
The input_device pointer is not refcounted, which means the device may
disappear while packets are queued, causing a crash when ifb passes packets
with a stale skb-&gt;dev pointer to netif_rx().

Fix by storing the interface index instead and do a lookup where neccessary.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>[ALSA] Fix invalid assignment of PCI revision</title>
<updated>2007-03-28T20:32:32Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2007-03-28T20:32:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8e617c8834fe2dde4e88ea9c2dcd9530c5b30839'/>
<id>urn:sha1:8e617c8834fe2dde4e88ea9c2dcd9530c5b30839</id>
<content type='text'>
Fix the type of PCI revision to char from int and avoid invalid
assignment with pointer cast.

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>[NET_SCHED]: Fix endless loops caused by inaccurate qlen counters</title>
<updated>2007-03-28T19:31:36Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2007-03-28T19:31:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=39740872332b2dd28b479d9d8333c42c32465953'/>
<id>urn:sha1:39740872332b2dd28b479d9d8333c42c32465953</id>
<content type='text'>
There are multiple problems related to qlen adjustment that can lead
to an upper qdisc getting out of sync with the real number of packets
queued, leading to endless dequeueing attempts by the upper layer code.

All qdiscs must maintain an accurate q.qlen counter. There are basically
two groups of operations affecting the qlen: operations that propagate
down the tree (enqueue, dequeue, requeue, drop, reset) beginning at the
root qdisc and operations only affecting a subtree or single qdisc
(change, graft, delete class). Since qlen changes during operations from
the second group don't propagate to ancestor qdiscs, their qlen values
become desynchronized.

This patch adds a function to propagate qlen changes up the qdisc tree,
optionally calling a callback function to perform qdisc-internal
maintenance when the child qdisc is deactivated, and converts all
qdiscs to use this where necessary.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
<entry>
<title>[SERIAL] Fix oops when removing suspended serial port</title>
<updated>2007-03-28T19:28:32Z</updated>
<author>
<name>Russell King</name>
<email>rmk+kernel@arm.linux.org.uk</email>
</author>
<published>2007-03-28T19:28:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ef1136fb7497e0ad6b419add0b463c9a770c42ee'/>
<id>urn:sha1:ef1136fb7497e0ad6b419add0b463c9a770c42ee</id>
<content type='text'>
A serial card might have been removed when the system is resumed.
This results in a suspended port being shut down, which results in
the ports shutdown method being called twice in a row.  This causes
BUGs.  Avoid this by tracking the suspended state separately from
the initialised state.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
</content>
</entry>
</feed>
