Kernel vanilla

Disponibile versione stabile nuovo kernel rilascio da



Ricordo che questo kernel รจ usabile con attenzione ma che manca di tutte le patch e moduli 3rdparty tipiche dei kernel Mandriva non essendo quello ufficiale di Mandriva.

bsdacct: fix access to invalid filp in acct_on()
    commit df279ca8966c3de83105428e3391ab17690802a9 upstream.
    The file opened in acct_on and freshly stored in the ns->bacct struct can
    be closed in acct_file_reopen by a concurrent call after we release
    acct_lock and before we call mntput(file->f_path.mnt).
    Record file->f_path.mnt in a local variable and use this variable only.

commit 6e9b0f6d101c80eb88a648d6746031ca77043043
Author: Felix Blyakher < This e-mail address is being protected from spambots. You need JavaScript enabled to view it >
Date:   Thu Jun 11 17:07:28 2009 -0500

    xfs: fix freeing memory in xfs_getbmap()
    commit 7747a0b0af5976ba3828796b4f7a7adc3bb76dbd upstream.
    Regression from commit 28e211700a81b0a934b6c7a4b8e7dda843634d2f.
    Need to free temporary buffer allocated in xfs_getbmap().
commit e1b41bb33a93eb3071c27db2c7313d72c5f2500c
    KVM: x86: silence preempt warning on kvm_write_guest_time
    commit 2dea4c84bc936731668b5a7a9fba5b436a422668 upstream.
    This issue just appeared in kvm-84 when running on (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:
    caller is kvm_arch_vcpu_ioctl_run+0x5d1/0xc70 [kvm]
    Pid: 28938, comm: qemu-system-x86
    Call Trace:
    kvm_arch_vcpu_ioctl_run+0x5d1/0xc70 [kvm]
    ? __wake_up+0x4e/0x70
    ? wake_futex+0x27/0x40
    kvm_vcpu_ioctl+0x2e9/0x5a0 [kvm]
    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]
commit 06ea0c9a0bb0d882a436ecf7876a08ace86de9a8

    drm/i915: correct suspend/resume ordering
    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.

Potete scaricarlo da qui,, al solito tasto destro salva destinazione con nome.

Ecco il log dei fix.