Hi Greg, On 2018/11/22 20:00, Gao Xiang wrote: > Hi Greg, > > On 2018/11/22 19:26, Greg Kroah-Hartman wrote: >> Don't make people rebuild your code with different options for >> debugging. That will never work in the 'real world' when people start >> using the code. You need to have things enabled for people all the >> time, which is why we have dynamic debugging in the kernel now, and not >> a zillion different "DRIVER_DEBUG" build options anymore. > Actually, current erofs handle differently for beta users (in eng mode) > and commercial users. > > CONFIG_EROFS_FS_DEBUG is enable for all beta users, after an observed > expression is false, we could get the whole memorydump as early as possible. > But for commercial users, there are no such observing points to promise > the kernel stability and performance. > > It has helped us to find several bug, and I cannot find some alternative way > to get the the first scene of the accident... I'm about to send v2 of this patchset... I need to get your opinion... I think for the current erofs development state, I tend to leave such a developping switch because the code could be modified frequently, many potential bugs could be avoid when this debugging mode is on and it will be dropped after erofs becomes more stable... Thanks, Gao Xiang > > Thanks, > Gao Xiang _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
