<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux, branch v2.6.30.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/?h=v2.6.30.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/?h=v2.6.30.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-07-02T23:52:38Z</updated>
<entry>
<title>Linux 2.6.30.1</title>
<updated>2009-07-02T23:52:38Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2009-07-02T23:52:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b44866e34ce96cdec2e848ab57808381df871ac8'/>
<id>urn:sha1:b44866e34ce96cdec2e848ab57808381df871ac8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>bsdacct: fix access to invalid filp in acct_on()</title>
<updated>2009-07-02T23:51:07Z</updated>
<author>
<name>Renaud Lottiaux</name>
<email>renaud.lottiaux@kerlabs.com</email>
</author>
<published>2009-06-30T18:41:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=114612139b431f6e908dc3c4f78f4dde62310155'/>
<id>urn:sha1:114612139b431f6e908dc3c4f78f4dde62310155</id>
<content type='text'>
commit df279ca8966c3de83105428e3391ab17690802a9 upstream.

The file opened in acct_on and freshly stored in the ns-&gt;bacct struct can
be closed in acct_file_reopen by a concurrent call after we release
acct_lock and before we call mntput(file-&gt;f_path.mnt).

Record file-&gt;f_path.mnt in a local variable and use this variable only.

Signed-off-by: Renaud Lottiaux &lt;renaud.lottiaux@kerlabs.com&gt;
Signed-off-by: Louis Rilling &lt;louis.rilling@kerlabs.com&gt;
Cc: Al Viro &lt;viro@zeniv.linux.org.uk&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>xfs: fix freeing memory in xfs_getbmap()</title>
<updated>2009-07-02T23:51:07Z</updated>
<author>
<name>Felix Blyakher</name>
<email>felixb@sgi.com</email>
</author>
<published>2009-06-11T22:07:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6e9b0f6d101c80eb88a648d6746031ca77043043'/>
<id>urn:sha1:6e9b0f6d101c80eb88a648d6746031ca77043043</id>
<content type='text'>
commit 7747a0b0af5976ba3828796b4f7a7adc3bb76dbd upstream.

Regression from commit 28e211700a81b0a934b6c7a4b8e7dda843634d2f.
Need to free temporary buffer allocated in xfs_getbmap().

Signed-off-by: Felix Blyakher &lt;felixb@sgi.com&gt;
Signed-off-by: Hedi Berriche &lt;hedi@sgi.com&gt;
Reported-by: Justin Piszcz &lt;jpiszcz@lucidpixels.com&gt;
Reviewed-by: Eric Sandeen &lt;sandeen@sandeen.net&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>KVM: x86: silence preempt warning on kvm_write_guest_time</title>
<updated>2009-07-02T23:51:06Z</updated>
<author>
<name>Matt T. Yourst</name>
<email>yourst@users.sourceforge.net</email>
</author>
<published>2009-02-24T18:28:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e1b41bb33a93eb3071c27db2c7313d72c5f2500c'/>
<id>urn:sha1:e1b41bb33a93eb3071c27db2c7313d72c5f2500c</id>
<content type='text'>
commit 2dea4c84bc936731668b5a7a9fba5b436a422668 upstream.

This issue just appeared in kvm-84 when running on 2.6.28.7 (x86-64)
with PREEMPT enabled.

We're getting syslog warnings like this many (but not all) times qemu
tells KVM to run the VCPU:

BUG: using smp_processor_id() in preemptible [00000000] code:
qemu-system-x86/28938
caller is kvm_arch_vcpu_ioctl_run+0x5d1/0xc70 [kvm]
Pid: 28938, comm: qemu-system-x86 2.6.28.7-mtyrel-64bit
Call Trace:
debug_smp_processor_id+0xf7/0x100
kvm_arch_vcpu_ioctl_run+0x5d1/0xc70 [kvm]
? __wake_up+0x4e/0x70
? wake_futex+0x27/0x40
kvm_vcpu_ioctl+0x2e9/0x5a0 [kvm]
enqueue_hrtimer+0x8a/0x110
_spin_unlock_irqrestore+0x27/0x50
vfs_ioctl+0x31/0xa0
do_vfs_ioctl+0x74/0x480
sys_futex+0xb4/0x140
sys_ioctl+0x99/0xa0
system_call_fastpath+0x16/0x1b

As it turns out, the call trace is messed up due to gcc's inlining, but
I isolated the problem anyway: kvm_write_guest_time() is being used in a
non-thread-safe manner on preemptable kernels.

Basically kvm_write_guest_time()'s body needs to be surrounded by
preempt_disable() and preempt_enable(), since the kernel won't let us
query any per-CPU data (indirectly using smp_processor_id()) without
preemption disabled. The attached patch fixes this issue by disabling
preemption inside kvm_write_guest_time().

[marcelo: surround only __get_cpu_var calls since the warning
is harmless]

Signed-off-by: Marcelo Tosatti &lt;mtosatti@redhat.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: correct suspend/resume ordering</title>
<updated>2009-07-02T23:51:06Z</updated>
<author>
<name>Jesse Barnes</name>
<email>jbarnes@virtuousgeek.org</email>
</author>
<published>2009-06-23T01:05:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=06ea0c9a0bb0d882a436ecf7876a08ace86de9a8'/>
<id>urn:sha1:06ea0c9a0bb0d882a436ecf7876a08ace86de9a8</id>
<content type='text'>
commit 9e06dd39f2b6d7e35981e0d7aded618686b32ccb upstream.

We need to save register state *after* idling GEM, clearing the ring,
and uninstalling the IRQ handler, or we might end up saving bogus
fence regs, for one.  Our restore ordering should already be correct,
since we do GEM, ring and IRQ init after restoring the last register
state, which prevents us from clobbering things.

I put this together to potentially address a bug, but I haven't heard
back if it fixes it yet.  However I think it stands on its own, so I'm
sending it in.

Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Cc: Jie Luo &lt;clotho67@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ide-cd: prevent null pointer deref via cdrom_newpc_intr</title>
<updated>2009-07-02T23:51:05Z</updated>
<author>
<name>Rainer Weikusat</name>
<email>rweikusat@mssgmbh.com</email>
</author>
<published>2009-06-18T15:04:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2547a3000f19e677ab5eb7e1a9c01164f5bd7922'/>
<id>urn:sha1:2547a3000f19e677ab5eb7e1a9c01164f5bd7922</id>
<content type='text'>
commit 39c58f37a10198054c656c28202fb1e6d22fd505 upstream.

With 2.6.30, the error handling code in cdrom_newpc_intr was changed
to deal with partial request failures by normally completing the 'good'
parts of a request and only 'error' the last (and presumably,
incompletely transferred) bio associated with a particular
request. In order to do this, ide_complete_rq is called over
ide_cd_error_cmd() to partially complete the rq. The block layer
does partial completion only for requests with bio's and if the
rq doesn't have one (eg 'GPCMD_READ_DISC_INFO') the request is
completed as a whole and the drive-&gt;hwif-&gt;rq pointer set to NULL
afterwards. When calling ide_complete_rq again to report
the error, this null pointer is derefenced, resulting in a kernel
crash.

This fixes http://bugzilla.kernel.org/show_bug.cgi?id=13399.

Signed-off-by: Rainer Weikusat &lt;rweikusat@mssgmbh.com&gt;
Signed-off-by: Borislav Petkov &lt;petkovbb@gmail.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ocfs2: Fix ocfs2_osb_dump()</title>
<updated>2009-07-02T23:51:04Z</updated>
<author>
<name>Sunil Mushran</name>
<email>sunil.mushran@oracle.com</email>
</author>
<published>2009-06-19T21:45:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=86f1152e3428d3515ebaabb542fb1ca750db79c9'/>
<id>urn:sha1:86f1152e3428d3515ebaabb542fb1ca750db79c9</id>
<content type='text'>
commit c3d38840abaa45c1c5a5fabbb8ffc9a0d1a764d1 upstream.

Skip printing information that is not valid for local mounts.

Signed-off-by: Sunil Mushran &lt;sunil.mushran@oracle.com&gt;
Signed-off-by: Joel Becker &lt;joel.becker@oracle.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>serial: bfin_5xx: fix building as module when early printk is enabled</title>
<updated>2009-07-02T23:51:03Z</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@gentoo.org</email>
</author>
<published>2009-06-22T17:41:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fc9744973531a87a2d3d6c573d5fae3bb8fd414e'/>
<id>urn:sha1:fc9744973531a87a2d3d6c573d5fae3bb8fd414e</id>
<content type='text'>
commit 607c268ef9a4675287e77f732071e426e62c2d86 upstream.

Since early printk only makes sense/works when the serial driver is built
into the kernel, disable the option for this driver when it is going to be
built as a module.  Otherwise we get build failures due to the ifdef
handling.

Signed-off-by: Mike Frysinger &lt;vapier@gentoo.org&gt;
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&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>CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK</title>
<updated>2009-07-02T23:51:01Z</updated>
<author>
<name>Tomas Szepe</name>
<email>szepe@pinerecords.com</email>
</author>
<published>2009-06-16T22:33:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4d794ad7062fe1c862db70ebb696aa0332a83dc0'/>
<id>urn:sha1:4d794ad7062fe1c862db70ebb696aa0332a83dc0</id>
<content type='text'>
commit 69050eee8e08a6234f29fe71a56f8c7c7d4d7186 upstream.

CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK.

This makes it possible to run complete systems out of a CONFIG_BLOCK=n
initramfs on current kernels again (this last worked on 2.6.27.*).

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>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://git.amat.us/linux/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>
</feed>
