On Tue, Sep 26, 2017 at 08:49:55PM +0800, Qu Wenruo wrote: > > Yeah something like that. And also make it a function, unless we're > > going to use some macro magic (I'm not sure about that yet). > > > > Schematically: > > > > btrfs_report_corruption(fs_info, EXTENT_ITEM, "file item type is unknown: > > %d", fi->type); > > > > implemented as: > > > > btrfs_err(fs_info, > > "corruption detected for item %d: " > > "file item type is unknown: %d", > > EXTENT_ITEM > > fi->type); > > > > Here comes the magic: as btrfs_err will print the arguments on one line > > and adds the \n, we have to merge the string and the argument list into > > one. > > > > But if adding a separate helper similar to btrfs_err would be more > > suitable, then ok. > > > I'll try to implement it, but I'm a little afraid that it may turn out > to little common routine for the error report and we may need to > manually craft the output for each member. > > But I'll keep this point in mind when updating the patchset.
Ok, let's see how far we can make it. Please send only updates on top of this patches for now, I've merged them to misc-next (ie. "for 4.15"). > BTW, what about moving these checkers and error reporting mechanism to > its own C file? > The code will definitely get larger and larger, I think moving them to > one separate file at the very beginning will save us more time. Good point, please proceed. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
