Re: CrashMonkey: A Framework to Systematically Test File-System Crash Consistency

2017-08-16 Thread Vijay Chidambaram
Amir, That's a fair response. I certainly did not mean to add more work on your end :) Using dm-log-writes for now is a reasonable approach. Like I mentioned before, I think there is further work involved in getting CrashMonkey to a useful point (where it finds at least known bugs). Once this is

Re: CrashMonkey: A Framework to Systematically Test File-System Crash Consistency

2017-08-16 Thread Amir Goldstein
On Wed, Aug 16, 2017 at 10:06 PM, Vijay Chidambaram wrote: > Hi Josef, > > Thank you for the detailed reply -- I think it provides several > pointers for our future work. It sounds like we have a similar vision > for where we want this to go, though we may disagree about how to > implement this :)

Re: CrashMonkey: A Framework to Systematically Test File-System Crash Consistency

2017-08-16 Thread Vijay Chidambaram
Hi Josef, Thank you for the detailed reply -- I think it provides several pointers for our future work. It sounds like we have a similar vision for where we want this to go, though we may disagree about how to implement this :) This is exciting! I agree that we should be building off existing wor

Re: CrashMonkey: A Framework to Systematically Test File-System Crash Consistency

2017-08-16 Thread Josef Bacik
On Tue, Aug 15, 2017 at 08:44:16PM -0500, Vijay Chidambaram wrote: > Hi Amir, > > I neglected to mention this earlier: CrashMonkey does not require > recompiling the kernel (it is a stand-alone kernel module), and has > been tested with the kernel 4.4. It should work with future kernel > versions