On Wed, Jun 27, 2012 at 12:57:12PM +0400, Glauber Costa wrote: > >I have to disagree with that. Deployment sometimes can be very > >painful. In some cases, even flipping single parameter in sysfs > >depending on kernel version takes considerable effort. The behavior > >has been the contract that we offered userland for quite some time > >now. We shouldn't be changing that underneath them without any clear > >way for them to notice it. > > Yes, and that's why once you deploy, you keep your updates to a > minimum. Because hell, even *perfectly legitimate bug fixes* can > change your behavior in a way you don't want. And you don't expect > people to refrain from fixing bugs because of that. Dude, there are numerous organizations running all types of infrastructures. I personally know some running debian + mainline kernel with regular kernel refresh (no, they aren't small). Silent behavior switches like this will be a big glowing fuck-you to those people and I don't wanna do that. And then there are infrastructures where new machines are continuously deployed and you know what? new machines often require new kernels. What are you gonna tell them? Don't cycle-upgrade your machines once you're in production? Please stop trying to argue that silently switching major behavior like this is okay. It simply isn't. This is breaching one of the most basic assumptions that our direct users make. NONONONONONONO. > That is precisely why people in serious environments tend to run > -stable, distro LTSes, or anything like that. Because they don't > want any change, however minor, to potentially affect their stamped > behavior. I am not proposing this patch to -stable, btw... Yeah, because once an environment is in prod, the only update they need is -stable and we can switch behaviors willy-nilly on any release. Ugh...... -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>