> The sysctl parameters msgmni, shmmni and semmni have an inherent limit > of IPC_MNI (32k). However, users may not be aware of that because they > can write a value much higher than that without getting any error or > notification. Reading the parameters back will show the newly written > values which are not real. > > Enforcing the limit by failing sysctl parameter write, however, may > cause regressions if existing user setup scripts set those parameters > above 32k as those scripts will now fail in this case. I have a serious problem with this approach. Have you made any effort to identify any code that sets these values above 32k? Have you looked to see if these applications actually care if you return an error when a value is set too large? Right now this seems like a lot of work to avoid breaking applications and or users that may or may not exist. If you can find something that will care sure. We need to avoid breaking userspace and causing regressions. However as this stands it looks you are making maintenance of the kernel more difficult to avoid having to look to see if there are monsters under the bed. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
