|
From: David S. <ds...@su...> - 2022-10-17 12:03:17
|
On Mon, Oct 17, 2022 at 10:31:03AM +0200, Dmitry Vyukov wrote: > On Fri, 14 Oct 2022 at 11:15, David Sterba <ds...@su...> wrote: > > On Fri, Oct 14, 2022 at 08:48:30AM +0000, Hrutvik Kanabar wrote: > > > From: Hrutvik Kanabar <hr...@go...> > > I think the build-time option inflexible, but I see the point when > > you're testing several filesystems that it's one place to set up the > > environment. Alternatively I suggest to add sysfs knob available in > > debuging builds to enable/disable checksum verification per filesystem. > > What usage scenarios do you have in mind for runtime changing of this option? > I see this option intended only for very narrow use cases which > require a specially built kernel in a number of other ways (lots of > which are not tunable at runtime, e.g. debugging configs). For my own development and testing usecase I'd like to build the kernel from the same config all the time, then start a VM and run random tests that do not skip the checksum verification. Then as the last also run fuzzing with checksums skipped. The debugging (lockdep, various sanity checks, ...) config options are enabled. We both have a narrow usecase, what I'm suggesting is a common way to enable them. |
