On Wed, Mar 29, 2017 at 4:57 PM, Jan Tulak <jtulak@xxxxxxxxxx> wrote: > > And I'm adding a validating function to spot this kind of errors > before the program does anything else. I made a first quick fire on this and even the half-baked version that can only find if a conflict is missing its counterpart has found two issues (L_AGNUM doesn't have an entry about L_NAME, but L_NAME points at L_AGNUM. Ditto for L_INTERNAL and L_NAME.) Let's see what it finds out when it also compares if the values are set accordingly. Also, I have published my git tree on github. It is in middle of changes according to things reported here in mailing list and you already have it locally, but if it is any help to you or Luis (CCed)... I will update it once I send updated patchset, and maybe few times before that (if I will find it helpful). https://github.com/jtulak/xfsprogs-dev (Ah, and ignore the name of the last commit, it is just a note for me what to pick on tomorrow - I'm ending for today.) Jan -- Jan Tulak jtulak@xxxxxxxxxx / jan@xxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
