They build from a release tarball on kernel.org with only 4 patches applied (none of which touch scheduling or anything autogroup-related). The only reason I can think of for Arch Linux not crashing and burning here is that their config is different in just the right way to not trigger the issue. For instance:
# CONFIG_PARAVIRT_SPINLOCKS is not set
That might be the reason Arch Linux is unaffected right there!
Stefan, here's the Arch Linux kernel package tree:
http:// projects. archlinux. org/svntogit/ packages. git/tree/ linux/repos/ core-x86_ 64?id=6b8ed4e66 60afe873aef3a20 7b187c5eb124c85 5
They build from a release tarball on kernel.org with only 4 patches applied (none of which touch scheduling or anything autogroup-related). The only reason I can think of for Arch Linux not crashing and burning here is that their config is different in just the right way to not trigger the issue. For instance:
# CONFIG_ PARAVIRT_ SPINLOCKS is not set
That might be the reason Arch Linux is unaffected right there!