Re: XFS: Hang and dmesg flood on mounting invalid FS image

2018-10-29 Thread Dave Chinner
On Mon, Oct 29, 2018 at 09:57:20AM +0300, Anatoly Trosinenko wrote: > > How did the corruption occur? > > It is a fuzzed image. Most probably, it was artificially "patched" by > fuzzer. Or do you mean "what particular bytes were changed"? I wondered how this specific corruption occurred in the re

Re: XFS: Hang and dmesg flood on mounting invalid FS image

2018-10-28 Thread Anatoly Trosinenko
> How did the corruption occur? It is a fuzzed image. Most probably, it was artificially "patched" by fuzzer. Or do you mean "what particular bytes were changed"? Best regards Anatoly пн, 29 окт. 2018 г. в 4:32, Dave Chinner : > > On Sun, Oct 28, 2018 at 08:50:46PM +0300, Anatoly Trosinenko wrote

Re: XFS: Hang and dmesg flood on mounting invalid FS image

2018-10-28 Thread Dave Chinner
On Sun, Oct 28, 2018 at 08:50:46PM +0300, Anatoly Trosinenko wrote: > Hello, > > When mounting a broken XFS image, the kernel hangs and floods dmesg > with stack traces. How did the corruption occur? $ sudo xfs_logprint -d /dev/vdc xfs_logprint: data device: 0xfd20 log device: 0xfd20 dad

XFS: Hang and dmesg flood on mounting invalid FS image

2018-10-28 Thread Anatoly Trosinenko
Hello, When mounting a broken XFS image, the kernel hangs and floods dmesg with stack traces. How to reproduce with kvm-xfstests: 1) Checkout v4.19, copy x86_64-config-4.14 to .config, `make olddefconfig` and compile 2) Unpack the attached image (128 Mb uncompressed) to /tmp/kvm-xfstests-$USER 3)