On Fri, 20 Apr 2018, Michal Hocko wrote: > On Fri 20-04-18 06:41:36, Matthew Wilcox wrote: > > On Fri, Apr 20, 2018 at 03:08:52PM +0200, Michal Hocko wrote: > > > > In order to detect these bugs reliably I submit this patch that changes > > > > kvmalloc to always use vmalloc if CONFIG_DEBUG_VM is turned on. > > > > > > No way. This is just wrong! First of all, you will explode most likely > > > on many allocations of small sizes. Second, CONFIG_DEBUG_VM tends to be > > > enabled quite often. > > > > I think it'll still suit Mikulas' debugging needs if we always use > > vmalloc for sizes above PAGE_SIZE? > > Even if that was the case then this doesn't sounds like CONFIG_DEBUG_VM > material. We do not want a completely different behavior when the config > > -- > Michal Hocko > SUSE Labs I'm not arguing that it must be turned on exactly by CONFIG_DEBUG_VM. It may be turned on some other option that is enabled in debug kernels (CONFIG_DEBUG_SG may be a better option, because you'll get meaningful stracktraces from DMA API then). > is enabled. If we really need some better fallback testing coverage > then the fault injection, as suggested by Vlastimil, sounds much more > reasonable to me People who test kernels will install the kernel-debug package, reboot to the debug kernel and run their testsuites. They won't turn on magic options in debugfs or use some hideous kernel commandline arguments. If the kvmalloc test isn't in the debug kernel, then the testing crew won't test it - that's it. Mikulas
