<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 19, 2013 at 5:35 AM, Jeff Darcy <span dir="ltr"><<a href="mailto:jdarcy@redhat.com" target="_blank">jdarcy@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 11/18/2013 11:32 PM, Anand Avati wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It might be interesting to build a test harness using libgfapi<br>
(specially the handle based APIs) to load a graph with the xlator to be<br>
test (on top of posix) and using gfapi calls to bombard fops and<br>
notifications and callbacks from multiple threads spawned by the testing<br>
app/framework.<br>
<br>
Along with a fault injection, we also need a "pedantic verifier"<br>
translator (loaded both on top and blow the testing xlator) which<br>
inspects all params of all calls and callbacks coming out of the xlator<br>
to "conform" by the rules (e.g lookup_cbk op_ret is either -1 or 0 ONLY,<br>
op_errno is one of the known standard values ONLY, struct stat does not<br>
have mtime/ctime/atime from too far ahead into the future, mkdir_cbk's<br>
struct stat has ia_type to be IA_IFDIR ONLY etc.)<br>
</blockquote>
<br></div>
Sounds like we have another volunteer. ;)<br>
<br></blockquote><div><br></div><div>Certainly. I have a half-done "pedantic" translator (few years ago) lying around somewhere and trying to dig it out..</div><div><br></div><div>Avati</div><div> </div></div><br>
</div></div>