<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git, branch v2.6.29.2</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.29.2</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.29.2'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2009-04-27T17:37:11Z</updated>
<entry>
<title>Linux 2.6.29.2</title>
<updated>2009-04-27T17:37:11Z</updated>
<author>
<name>Chris Wright</name>
<email>chrisw@sous-sol.org</email>
</author>
<published>2009-04-27T17:37:11Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=e34454757fb87ecac1f76e4169cff6b74ba7ec44'/>
<id>urn:sha1:e34454757fb87ecac1f76e4169cff6b74ba7ec44</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bonding: fix zero address hole bug in arp_ip_target list</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Brian Haley</name>
<email>brian.haley@hp.com</email>
</author>
<published>2009-04-13T07:11:30Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=5f9645212515279c4876ff0200fe7fa51dfb57ce'/>
<id>urn:sha1:5f9645212515279c4876ff0200fe7fa51dfb57ce</id>
<content type='text'>
upstream commit: 5a31bec014449dc9ca994e4c1dbf2802b7ca458a

Fix a zero address hole bug in the bonding arp_ip_target list
that was causing the bond to ignore ARP replies (bugz 13006).
Instead of just setting the array entry to zero, we now
copy any additional entries down one slot, putting the
zero entry at the end.  With this change we can now have
all the loops that walk the array stop when they hit a zero
since there will be no addresses after it.

Changes are based in part on code fragment provided in kernel:
bugzilla 13006:

	http://bugzilla.kernel.org/show_bug.cgi?id=13006

by Steve Howard &lt;steve@astutenetworks.com&gt;

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>skge: fix occasional BUG during MTU change</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Michal Schmidt</name>
<email>mschmidt@redhat.com</email>
</author>
<published>2009-04-14T22:16:55Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=9fc79ab9a371b45166d80ef18411ea47cf8e3195'/>
<id>urn:sha1:9fc79ab9a371b45166d80ef18411ea47cf8e3195</id>
<content type='text'>
upstream commit: d119b3927994e3d620d6adb0dd1ea6bf24427875

The BUG_ON(skge-&gt;tx_ring.to_use != skge-&gt;tx_ring.to_clean) in skge_up()
was sometimes observed when setting MTU.

skge_down() disables the TX queue, but then reenables it by mistake via
skge_tx_clean().
Fix it by moving the waking of the queue from skge_tx_clean() to the
other caller. And to make sure start_xmit is not in progress on another
CPU, skge_down() should call netif_tx_disable().

The bug was reported to me by Jiri Jilek whose Debian system sometimes
failed to boot. He tested the patch and the bug did not happen anymore.

Signed-off-by: Michal Schmidt &lt;mschmidt@redhat.com&gt;
Acked-by: Stephen Hemminger &lt;shemminger@vyatta.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>scsi: mpt: suppress debugobjects warning</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@parisplace.org</email>
</author>
<published>2009-04-21T21:20:02Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=24016c735e651f179692432f18176348caeb82b0'/>
<id>urn:sha1:24016c735e651f179692432f18176348caeb82b0</id>
<content type='text'>
upstream commit: b298cecb3deddf76d60022473a57f1cb776cbdcd

Addresses http://bugzilla.kernel.org/show_bug.cgi?id=13133

ODEBUG: object is on stack, but not annotated
------------[ cut here ]------------
WARNING: at lib/debugobjects.c:253 __debug_object_init+0x1f3/0x276()
Hardware name: VMware Virtual Platform
Modules linked in: mptspi(+) mptscsih mptbase scsi_transport_spi ext3 jbd mbcache
Pid: 540, comm: insmod Not tainted 2.6.28-mm1 #2
Call Trace:
 [&lt;c042c51c&gt;] warn_slowpath+0x74/0x8a
 [&lt;c0469600&gt;] ? start_critical_timing+0x96/0xb7
 [&lt;c060c8ea&gt;] ? _spin_unlock_irqrestore+0x2f/0x3c
 [&lt;c0446fad&gt;] ? trace_hardirqs_off_caller+0x18/0xaf
 [&lt;c044704f&gt;] ? trace_hardirqs_off+0xb/0xd
 [&lt;c060c8ea&gt;] ? _spin_unlock_irqrestore+0x2f/0x3c
 [&lt;c042cb84&gt;] ? release_console_sem+0x1a5/0x1ad
 [&lt;c05013e6&gt;] __debug_object_init+0x1f3/0x276
 [&lt;c0501494&gt;] debug_object_init+0x13/0x17
 [&lt;c0433c56&gt;] init_timer+0x10/0x1a
 [&lt;e08e5b54&gt;] mpt_config+0x1c1/0x2b7 [mptbase]
 [&lt;e08e3b82&gt;] ? kmalloc+0x8/0xa [mptbase]
 [&lt;e08e3b82&gt;] ? kmalloc+0x8/0xa [mptbase]
 [&lt;e08e6fa2&gt;] mpt_do_ioc_recovery+0x950/0x1212 [mptbase]
 [&lt;c04496c2&gt;] ? __lock_acquire+0xa69/0xacc
 [&lt;c060c8f1&gt;] ? _spin_unlock_irqrestore+0x36/0x3c
 [&lt;c060c3af&gt;] ? _spin_unlock_irq+0x22/0x26
 [&lt;c04f2d8b&gt;] ? string+0x2b/0x76
 [&lt;c04f310e&gt;] ? vsnprintf+0x338/0x7b3
 [&lt;c04496c2&gt;] ? __lock_acquire+0xa69/0xacc
 [&lt;c060c8ea&gt;] ? _spin_unlock_irqrestore+0x2f/0x3c
 [&lt;c04496c2&gt;] ? __lock_acquire+0xa69/0xacc
 [&lt;c044897d&gt;] ? debug_check_no_locks_freed+0xeb/0x105
 [&lt;c060c8f1&gt;] ? _spin_unlock_irqrestore+0x36/0x3c
 [&lt;c04488bc&gt;] ? debug_check_no_locks_freed+0x2a/0x105
 [&lt;c0446b8c&gt;] ? lock_release_holdtime+0x43/0x48
 [&lt;c043f742&gt;] ? up_read+0x16/0x29
 [&lt;c05076f8&gt;] ? pci_get_slot+0x66/0x72
 [&lt;e08e89ca&gt;] mpt_attach+0x881/0x9b1 [mptbase]
 [&lt;e091c8e5&gt;] mptspi_probe+0x11/0x354 [mptspi]

Noticing that every caller of mpt_config has its CONFIGPARMS struct
declared on the stack and thus the &amp;pCfg-&gt;timer is always on the stack I
changed init_timer() to init_timer_on_stack() and it seems to have shut
up.....

Cc: "Moore, Eric Dean" &lt;Eric.Moore@lsil.com&gt;
Cc: James Bottomley &lt;James.Bottomley@HansenPartnership.com&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Acked-by: "Desai, Kashyap" &lt;Kashyap.Desai@lsi.com&gt;
Cc: &lt;stable@kernel.org&gt;		[2.6.29.x]
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;
</content>
</entry>
<entry>
<title>hugetlbfs: return negative error code for bad mount option</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Akinobu Mita</name>
<email>akinobu.mita@gmail.com</email>
</author>
<published>2009-04-21T21:20:04Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=5a9b5af39e948919f272867516faa61c093124f6'/>
<id>urn:sha1:5a9b5af39e948919f272867516faa61c093124f6</id>
<content type='text'>
upstream commit: c12ddba09394c60e1120e6997794fa6ed52da884

This fixes the following BUG:

  # mount -o size=MM -t hugetlbfs none /huge
  hugetlbfs: Bad value 'MM' for mount option 'size=MM'
  ------------[ cut here ]------------
  kernel BUG at fs/super.c:996!

Due to

	BUG_ON(!mnt-&gt;mnt_sb);

in vfs_kern_mount().

Also, remove unused #include &lt;linux/quotaops.h&gt;

Cc: William Irwin &lt;wli@holomorphy.com&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Akinobu Mita &lt;akinobu.mita@gmail.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;
</content>
</entry>
<entry>
<title>NFS: Fix the XDR iovec calculation in nfs3_xdr_setaclargs</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Trond Myklebust</name>
<email>Trond.Myklebust@netapp.com</email>
</author>
<published>2009-04-21T21:20:08Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=52f8cf35ef8716fbcb00ffe3a680d2a4c54e412d'/>
<id>urn:sha1:52f8cf35ef8716fbcb00ffe3a680d2a4c54e412d</id>
<content type='text'>
upstream commit: 8340437210390676f687633a80e3748c40885dc8

Commit ae46141ff08f1965b17c531b571953c39ce8b9e2 (NFSv3: Fix posix ACL code)
introduces a bug in the calculation of the XDR header iovec. In the case
where we are inlining the acls, we need to adjust the length of the iovec
req-&gt;rq_svec, in addition to adjusting the total buffer length.

Tested-by: Leonardo Chiquitto &lt;leonardo.lists@gmail.com&gt;
Tested-by: Suresh Jayaraman &lt;sjayaraman@suse.de&gt;
Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>gso: Fix support for linear packets</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2009-04-21T11:31:50Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=d6af2381754182d727fb4682e785f56ae8508210'/>
<id>urn:sha1:d6af2381754182d727fb4682e785f56ae8508210</id>
<content type='text'>
upstream commit: 2f181855a0b3c2b39314944add7b41c15647cf86

When GRO/frag_list support was added to GSO, I made an error
which broke the support for segmenting linear GSO packets (GSO
packets are normally non-linear in the payload).

These days most of these packets are constructed by the tun
driver, which prefers to allocate linear memory if possible.
This is fixed in the latest kernel, but for 2.6.29 and earlier
it is still the norm.

Therefore this bug causes failures with GSO when used with tun
in 2.6.29.

Reported-by: James Huang &lt;jamesclhuang@gmail.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>agp: zero pages before sending to userspace</title>
<updated>2009-04-27T17:37:05Z</updated>
<author>
<name>Shaohua Li</name>
<email>shaohua.li@intel.com</email>
</author>
<published>2009-04-20T00:08:35Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=0702b646e5bdc16af64ef6f663e5275a02bf40cd'/>
<id>urn:sha1:0702b646e5bdc16af64ef6f663e5275a02bf40cd</id>
<content type='text'>
upstream commit: 59de2bebabc5027f93df999d59cc65df591c3e6e

CVE-2009-1192

AGP pages might be mapped into userspace finally, so the pages should be
set to zero before userspace can use it. Otherwise there is potential
information leakage.

Signed-off-by: Shaohua Li &lt;shaohua.li@intel.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>virtio: fix suspend when using virtio_balloon</title>
<updated>2009-04-27T17:37:04Z</updated>
<author>
<name>Marcelo Tosatti</name>
<email>mtosatti@redhat.com</email>
</author>
<published>2009-04-19T18:05:04Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=7b0e3850488bbd218b6ea4cc0e5c6e549995a6f7'/>
<id>urn:sha1:7b0e3850488bbd218b6ea4cc0e5c6e549995a6f7</id>
<content type='text'>
upstream commit: 84a139a985300901dfad99bd93c7345d180af860

Break out of wait_event_interruptible() if freezing has been requested,
in the vballoon thread. Without this change vballoon refuses to stop and
the system can't suspend.

Signed-off-by: Marcelo Tosatti &lt;mtosatti@redhat.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: stable@kernel.org
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>Revert "console ASCII glyph 1:1 mapping"</title>
<updated>2009-04-27T17:37:04Z</updated>
<author>
<name>Samuel Thibault</name>
<email>samuel.thibault@ens-lyon.org</email>
</author>
<published>2009-04-19T18:05:02Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=cbe8fe4ae7f8bcc410c105810b263abf24439a53'/>
<id>urn:sha1:cbe8fe4ae7f8bcc410c105810b263abf24439a53</id>
<content type='text'>
upstream commit: c0b7988200a82290287c6f4cd49585007f73175a

This reverts commit 1c55f18717304100a5f624c923f7cb6511b4116d.

Ingo Brueckl was assuming that reverting to 1:1 mapping for chars &gt;= 128
was not useful, but it happens to be: due to the limitations of the
Linux console, when a blind user wants to read BIG5 on it, he has no
other way than loading a font without SFM and let the 1:1 mapping permit
the screen reader to get the BIG5 encoding.

Signed-off-by: Samuel Thibault &lt;samuel.thibault@ens-lyon.org&gt;
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
</feed>
