On Mon, Nov 21, 2016 at 4:37 PM, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > On Mon, 7 Nov 2016 11:38:20 +0100 > Cyril Hrubis <chrubis@xxxxxxx> wrote: > > >> I'm not sure if something like this is really doable or in the scope of >> this project, but it may be worth a try. >> > > Looking ahead into the future, I was also thinking that if this becomes > robust, we could also start an integration specification, that could > describe how different system calls interact with each other. Like > open() to read(), write() and close(). > > But this is just an idea that popped in my head while reading this > thread. We want to start small first, but still could keep this in the > back of our minds for future enhancements. FWIW syzkaller does something along these lines. It has notion of 'resources' and of input/output arguments. Then it can figure out that e.g. open creates fd's, so it should be called before any reads/writes (provided that we want to pass in valid fd's). It does not have notion of "destructors" for resources (e.g. close destroys the passed in resource). But it should be easy to describe. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
