Re: [PATCH 0/6] mempolicy memory corruption fixlet
From: KOSAKI Motohiro <hidden>
Date: 2012-06-01 19:38:00
Also in:
lkml, stable
quoted
quoted
quoted
quoted
quoted
Yes, that's right direction, I think. Currently, shmem_set_policy() can't handle nonlinear mapping.I've been mulling for some time to just remove non linear mappings. AFAIK they were only useful on 32bit and are obsolete and could be emulated with VMAs instead.I agree. It is only userful on 32bit and current enterprise users don't use 32bit anymore. So, I don't think emulated by vmas cause user visible issue.I wish this was true, there are a lot of systems out there still running 32 bit linux, even on 64 bit capible hardware. This is especially true in enterprises where they have either homegrown or proprietary software that isn't 64 bit clean.32 bit binaries (and entire distros) run fine under 64 bit kernels.unfortunantly, not quite 100% of the time. It's very good, but the automount bug a month or so ago is an example of how you can run into rare problems. Many "enterprise" systems are not willing to risk it.
Then we can remove a feature safely. Risk not taker continue to uses old distro kernel. And some years after, distros discontinue to support 32bit. And then, problem will vanish automatically. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>