On Wed, Jul 04, 2018 at 08:01:11PM +0800, Qu Wenruo wrote: > > > On 2018年07月04日 19:58, David Sterba wrote: > > On Tue, Jul 03, 2018 at 09:40:40PM +0800, Qu Wenruo wrote: > >> Don't panic for btrfs_read_chunk_tree() if one device or chunk is > >> corrupted. > >> Caller can already handle it pretty well. > >> > >> Link: https://bugzilla.kernel.org/show_bug.cgi?id=199839 > >> Signed-off-by: Qu Wenruo <w...@suse.com> > > > > Applied, thanks. > > > > In case there's a fuzzed image, please send it too. There are example > > commits how to name, format and document it. Thanks. > > Sorry for forgetting the image. > > However, I'm puzzled by the fact that, even for some fuzzed image which > is originally designed to detect kernel misbehavior, it's still added > into btrfs-progs test cases.
The kernel tests of the fuzzed images are considered dangerous and the mount test is intentionally missing from the progs for now. As the testsuite can be exported and used outside of the git repository, the actual mount tests can be run in an environment where the crashes don't matter. We'd need to add the script and some way to skip it by default. The fuzzed images should also pass the userspace tools, for better testing coverage eg. for the error handling so they're kept in one place. -- 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
