On Thu, 26 Apr 2018, James Bottomley wrote: > So you're shifting your argument from "I have to do it as a Kconfig > option because the distros require it" to "distributions will build > separate kernel packages for this, but won't do enabling in a non > kernel package"? To be honest, I think the argument is nuts but I > don't really care. From my point of view it's usually me explaining to > people how to debug stuff and "you have to build your own kernel with > this Kconfig option" compared to "add this to the kernel command line > and reboot" is much more effort for the debugger. > > James If you have to explain to the user that he needs to turn it on, it is already wrong. In order to find the kvmalloc abuses, it should be tested by as many users as possible. And it could be tested by as many users as possible, if it can be enabled in a VISIBLE place (i.e. menuconfig) - or (in my opinion even better) it should be bound to an CONFIG_ option that is already enabled for debugging kernel - then you won't have to explain anything to the user at all. Hardly anyone - except for people who read this thread - will know about the new commandline parameters or debugfs files. I'm not arguing that the commandline parameter or debugfs files are wrong. They are OK to overridde the default settings for advanced users. But they are useless for common users because common users won't know about them. Mikulas
