On Mon, 30 Apr 2018, John Stoffel wrote: > >>>>> "Mikulas" == Mikulas Patocka <mpatocka@xxxxxxxxxx> writes: > > Mikulas> On Thu, 26 Apr 2018, John Stoffel wrote: > > Mikulas> I see your point - and I think the misunderstanding is this. > > Thanks. > > Mikulas> This patch is not really helping people to debug existing crashes. It is > Mikulas> not like "you get a crash" - "you google for some keywords" - "you get a > Mikulas> page that suggests to turn this option on" - "you turn it on and solve the > Mikulas> crash". > > Mikulas> What this patch really does is that - it makes the kernel deliberately > Mikulas> crash in a situation when the code violates the specification, but it > Mikulas> would not crash otherwise or it would crash very rarely. It helps to > Mikulas> detect specification violations. > > Mikulas> If the kernel developer (or tester) doesn't use this option, his buggy > Mikulas> code won't crash - and if it won't crash, he won't fix the bug or report > Mikulas> it. How is the user or developer supposed to learn about this option, if > Mikulas> he gets no crash at all? > > So why do we make this a KConfig option at all? Because other people see the KConfig option (so, they may enable it) and they don't see the kernel parameter (so, they won't enable it). Close your eyes and say how many kernel parameters do you remember :-) > Just turn it on and let it rip. I can't test if all the networking drivers use kvmalloc properly, because I don't have the hardware. You can't test it neither. No one has all the hardware that is supported by Linux. Driver issues can only be tested by a mass of users. And if the users don't know about the debugging option, they won't enable it. > >> I agree with James here. Looking at the SLAB vs SLUB Kconfig entries > >> tells me *nothing* about why I should pick one or the other, as an > >> example. BTW. You can enable slub debugging either with CONFIG_SLUB_DEBUG_ON or with the kernel parameter "slub_debug" - and most users who compile their own kernel use CONFIG_SLUB_DEBUG_ON - just because it is visible. > Now I also think that Linus has the right idea to not just sprinkle > BUG_ONs into the code, just dump and oops and keep going if you can. > If it's a filesystem or a device, turn it read only so that people > notice right away. This vmalloc fallback is similar to CONFIG_DEBUG_KOBJECT_RELEASE. CONFIG_DEBUG_KOBJECT_RELEASE changes the behavior of kobject_put in order to cause deliberate crashes (that wouldn't happen otherwise) in drivers that misuse kobject_put. In the same sense, we want to cause deliberate crashes (that wouldn't happen otherwise) in drivers that misuse kvmalloc. The crashes will only happen in debugging kernels, not in production kernels. Mikulas
