These commits included in 2.6.32.12: ea0a09acd81c6d52c77d80f0d4089795df7bcb58 "modules: fix incorrect percpu usage" d150a2b96558a7349cbf3a72a279c37bc67d50fb "module: fix __module_ref_addr()" apparently caused regressions, and have been reverted in SLE 11.1 and Debian unstable. The second has also now been reverted in 2.6.32.14, but the first has not. I'm afraid I don't understand the problems they were trying to solve, or the problems they caused, so could someone explain why the first should or not should not be reverted in 2.6.32-stable? (Matthieu previously asked whether it was really correct for 2.6.32: http://linux.kernel.org/pipermail/stable-review/2010-April/003571.html ) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part