[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE5jQCeFs0_NS9AZwfw+U60jKU5RRPD56THEhCq_jLJkiFy0=A@mail.gmail.com>
Date: Sun, 4 Nov 2018 10:37:34 +0300
From: Anatoly Trosinenko <anatoly.trosinenko@...il.com>
To: Mark Fasheh <mark@...heh.com>, Joel Becker <jlbec@...lplan.org>
Cc: ocfs2-devel@....oracle.com, linux-kernel@...r.kernel.org
Subject: OCFS2: [ocfs2_rename:1688 ERROR: status = -39] with four syscalls on
fresh FS image
Hello,
When fuzzing OCFS2, I got an ERROR message in dmesg output with
several syscalls on completely fresh, uncrafted FS image. From this
https://oss.oracle.com/pipermail/ocfs2-devel/2012-August/008683.html
it looks like ERROR messages are indicating some unexpected conditions
in the driver code, is it right? If so, here it how to reproduce it
with kvm-xfstests:
1) Checkout latest torvalds/master (tested with commit 71e56028), copy
x86_64-config-4.14 from fstests to .config, `make olddefconfig`,
enable CONFIG_FS then OCFS2 and compile
2) Create fresh OCFS2 image:
$ fallocate -l 256M ocfs2
$ mkfs.ocfs2 -L test --fs-features=local ./ocfs2
$ mv ocfs2 /tmp/kvm-xfstests-$USER/ # mkfs.ocfs2 seems to not operate
on tmpfs that can be mounted on /tmp
3) gcc --static ocfs2.c -o /tmp/kvm-xfstests-$USER/repro
4) Inside the ./kvm-xfstests shell
root@...-xfstests:~# mount /vtmp
root@...-xfstests:~# mount /vtmp/ocfs2 /mnt
[ 17.168634] JBD2: Ignoring recovery information on journal
[ 17.173903] ocfs2: Mounting device (7,0) on (node local, slot 0)
with ordered data mode.
root@...-xfstests:~# /vtmp/repro
[ 20.597145] (repro,368,1):ocfs2_rename:1688 ERROR: status = -39
root@...-xfstests:~#
Best regards
Anatoly
View attachment "ocfs2.c" of type "text/x-csrc" (223 bytes)
Powered by blists - more mailing lists