From: Conor Dooley <conor@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Björn Töpel" <bjorn@kernel.org>,
linux-fsdevel@vger.kernel.org,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Christian Brauner" <brauner@kernel.org>,
"Jan Kara" <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
"Andreas Dilger" <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: riscv32 EXT4 splat, 6.8 regression?
Date: Sat, 13 Apr 2024 11:01:08 +0100 [thread overview]
Message-ID: <20240413-ranging-uselessly-4b1de2210593@spud> (raw)
In-Reply-To: <20240413043542.GE187181@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 3506 bytes --]
On Sat, Apr 13, 2024 at 12:35:42AM -0400, Theodore Ts'o wrote:
> On Fri, Apr 12, 2024 at 06:59:19PM +0200, Björn Töpel wrote:
> >
> > $ pipx install tuxrun
> >
> > if you're on Debian.
> >
> > Then you can get the splat by running:
> >
> > $ tuxrun --runtime docker --device qemu-riscv32 --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2esMBaAMQJpcmczj0aL94fp4QnP/Image.gz --parameters SKIPFILE=skipfile-lkft.yaml --parameters SHARD_NUMBER=10 --parameters SHARD_INDEX=1 --image docker.io/linaro/tuxrun-dispatcher:v0.66.1 --tests ltp-controllers
>
> Yeah, what I was hoping for was a shell script or a .c file hich was
> the reproducer, because that way I can run the test in my test infrastructure [1]
>
> [1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-xfstests.md
>
> I'm sure there are plenty of nice things about tuxrun, but with
> kvm-xfstests I can easily get a shell so I can run the test sccript by
> hand, perhaps with strace so I can see what is going on. Or I attach
> gdb to the kernel via "gdb /path/to/vmlinux" and "target remote
> localhost:7499".
>
> I'm guessing that "ltp-controllers" means that the test might be from
> the Linux Test Project? If so, that's great because I've added ltp
> support to my test infrastructure (which also supports blktests,
> phoronix test suite, and can be run on gce and on android devices in
> addition to qemu, and on the arm64, i386, and x86_64 architectures).
>
> > Build with "make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu-", and make
> > sure to have the riscv64 cross-compilation support (yes, same toolchain
> > for rv32!).
> >
> > It's when the rootfs is mounted, and the kernel is looking an init.
>
> Hmm, so this happening as soon as the VM starts, before actually
> starting to run any tests? Is it possible for you to send me the
> rootfs as a downloading image, as opposed to my trying to paw through
> the docker image?
>
> > I'll keep debugging -- it was more if anyone had seen it before. I'll
> > try to reproduce on some other 32b platform as well.
>
> Well, it's not happening on my rootfs on i386 using my test infrastructure:
>
> % cd /usr/projects/linux/ext4
> % git checkout v6.8
> % install-kconfig --arch i386
> % kbuild --arch i386
> % kvm-xfstests shell
> ...
> root@kvm-xfstests:~# cd ltp
> root@kvm-xfstests:~# ./runltp
>
> (I don't have ltp support fully automated the way I can run blktests
> using "kvm-xfstests --blktests" or run xfstests via "gce-xfstests -c
> ext4/all -g auto". The main missing is teaching ltp to create an
> junit xml results file so that the test results can be summarized and
> so the test results can be more easily summarized and compared against
> past runs on different kernel versions.)
>
> Anyway, if you can send me your rootfs, I can try to take a look at it.
I think this should be the rootfs here:
https://drive.google.com/file/d/1HIo8EkAKY0xpTIIlwd9fXjRzmIdD7BUA/view?usp=sharing
I also attempted to bisect this and ended up at a slightly different
commit to Bjorn: 8c9440fea774 ("Merge tag 'vfs-6.8.mount' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs")
That's a merge of 3f6984e7301f & 5bd3cf8cbc8a, both of which booted for
me. I also tried to bisect in reverse to find the fix a la syzbot, since it
is not broken in 6.9, but that's pretty error prone and I ended up down
branches based on 6.7 and was not able to find the fix.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Björn Töpel" <bjorn@kernel.org>,
linux-fsdevel@vger.kernel.org,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Christian Brauner" <brauner@kernel.org>,
"Jan Kara" <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
"Andreas Dilger" <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: riscv32 EXT4 splat, 6.8 regression?
Date: Sat, 13 Apr 2024 11:01:08 +0100 [thread overview]
Message-ID: <20240413-ranging-uselessly-4b1de2210593@spud> (raw)
In-Reply-To: <20240413043542.GE187181@mit.edu>
[-- Attachment #1.1: Type: text/plain, Size: 3506 bytes --]
On Sat, Apr 13, 2024 at 12:35:42AM -0400, Theodore Ts'o wrote:
> On Fri, Apr 12, 2024 at 06:59:19PM +0200, Björn Töpel wrote:
> >
> > $ pipx install tuxrun
> >
> > if you're on Debian.
> >
> > Then you can get the splat by running:
> >
> > $ tuxrun --runtime docker --device qemu-riscv32 --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2esMBaAMQJpcmczj0aL94fp4QnP/Image.gz --parameters SKIPFILE=skipfile-lkft.yaml --parameters SHARD_NUMBER=10 --parameters SHARD_INDEX=1 --image docker.io/linaro/tuxrun-dispatcher:v0.66.1 --tests ltp-controllers
>
> Yeah, what I was hoping for was a shell script or a .c file hich was
> the reproducer, because that way I can run the test in my test infrastructure [1]
>
> [1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-xfstests.md
>
> I'm sure there are plenty of nice things about tuxrun, but with
> kvm-xfstests I can easily get a shell so I can run the test sccript by
> hand, perhaps with strace so I can see what is going on. Or I attach
> gdb to the kernel via "gdb /path/to/vmlinux" and "target remote
> localhost:7499".
>
> I'm guessing that "ltp-controllers" means that the test might be from
> the Linux Test Project? If so, that's great because I've added ltp
> support to my test infrastructure (which also supports blktests,
> phoronix test suite, and can be run on gce and on android devices in
> addition to qemu, and on the arm64, i386, and x86_64 architectures).
>
> > Build with "make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu-", and make
> > sure to have the riscv64 cross-compilation support (yes, same toolchain
> > for rv32!).
> >
> > It's when the rootfs is mounted, and the kernel is looking an init.
>
> Hmm, so this happening as soon as the VM starts, before actually
> starting to run any tests? Is it possible for you to send me the
> rootfs as a downloading image, as opposed to my trying to paw through
> the docker image?
>
> > I'll keep debugging -- it was more if anyone had seen it before. I'll
> > try to reproduce on some other 32b platform as well.
>
> Well, it's not happening on my rootfs on i386 using my test infrastructure:
>
> % cd /usr/projects/linux/ext4
> % git checkout v6.8
> % install-kconfig --arch i386
> % kbuild --arch i386
> % kvm-xfstests shell
> ...
> root@kvm-xfstests:~# cd ltp
> root@kvm-xfstests:~# ./runltp
>
> (I don't have ltp support fully automated the way I can run blktests
> using "kvm-xfstests --blktests" or run xfstests via "gce-xfstests -c
> ext4/all -g auto". The main missing is teaching ltp to create an
> junit xml results file so that the test results can be summarized and
> so the test results can be more easily summarized and compared against
> past runs on different kernel versions.)
>
> Anyway, if you can send me your rootfs, I can try to take a look at it.
I think this should be the rootfs here:
https://drive.google.com/file/d/1HIo8EkAKY0xpTIIlwd9fXjRzmIdD7BUA/view?usp=sharing
I also attempted to bisect this and ended up at a slightly different
commit to Bjorn: 8c9440fea774 ("Merge tag 'vfs-6.8.mount' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs")
That's a merge of 3f6984e7301f & 5bd3cf8cbc8a, both of which booted for
me. I also tried to bisect in reverse to find the fix a la syzbot, since it
is not broken in 6.9, but that's pretty error prone and I ended up down
branches based on 6.7 and was not able to find the fix.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-13 10:01 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 14:57 riscv32 EXT4 splat, 6.8 regression? Björn Töpel
2024-04-12 14:57 ` Björn Töpel
2024-04-12 15:43 ` Theodore Ts'o
2024-04-12 15:43 ` Theodore Ts'o
2024-04-12 16:59 ` Björn Töpel
2024-04-12 16:59 ` Björn Töpel
2024-04-13 4:35 ` Theodore Ts'o
2024-04-13 4:35 ` Theodore Ts'o
2024-04-13 10:01 ` Conor Dooley [this message]
2024-04-13 10:01 ` Conor Dooley
2024-04-13 14:43 ` Nam Cao
2024-04-13 14:43 ` Nam Cao
2024-04-14 0:24 ` Theodore Ts'o
2024-04-14 0:24 ` Theodore Ts'o
2024-04-14 1:46 ` Andreas Dilger
2024-04-14 1:46 ` Andreas Dilger
2024-04-14 2:04 ` Theodore Ts'o
2024-04-14 2:04 ` Theodore Ts'o
2024-04-14 2:18 ` Al Viro
2024-04-14 2:18 ` Al Viro
2024-04-14 2:15 ` Al Viro
2024-04-14 2:15 ` Al Viro
2024-04-14 4:16 ` Andreas Dilger
2024-04-14 4:16 ` Andreas Dilger
2024-04-14 14:08 ` Björn Töpel
2024-04-14 14:08 ` Björn Töpel
2024-04-15 13:04 ` Christian Brauner
2024-04-15 13:04 ` Christian Brauner
2024-04-15 16:04 ` Björn Töpel
2024-04-15 16:04 ` Björn Töpel
2024-04-16 6:44 ` Nam Cao
2024-04-16 6:44 ` Nam Cao
2024-04-16 8:25 ` Christian Brauner
2024-04-16 8:25 ` Christian Brauner
2024-04-16 11:02 ` Björn Töpel
2024-04-16 11:02 ` Björn Töpel
2024-04-16 14:24 ` Mike Rapoport
2024-04-16 14:24 ` Mike Rapoport
2024-04-16 15:17 ` Nam Cao
2024-04-16 15:17 ` Nam Cao
2024-04-16 15:30 ` Nam Cao
2024-04-16 15:30 ` Nam Cao
2024-04-16 15:56 ` Björn Töpel
2024-04-16 15:56 ` Björn Töpel
2024-04-16 16:19 ` Nam Cao
2024-04-16 16:19 ` Nam Cao
2024-04-16 16:31 ` Mike Rapoport
2024-04-16 16:31 ` Mike Rapoport
2024-04-16 17:00 ` Matthew Wilcox
2024-04-16 17:00 ` Matthew Wilcox
2024-04-16 18:34 ` Mike Rapoport
2024-04-16 18:34 ` Mike Rapoport
2024-04-16 22:36 ` Nam Cao
2024-04-16 22:36 ` Nam Cao
2024-04-17 15:31 ` Theodore Ts'o
2024-04-17 15:31 ` Theodore Ts'o
2024-04-17 18:06 ` Nam Cao
2024-04-17 18:06 ` Nam Cao
2024-04-17 19:34 ` Mike Rapoport
2024-04-17 19:34 ` Mike Rapoport
2024-04-17 22:09 ` Andreas Dilger
2024-04-17 22:09 ` Andreas Dilger
2024-04-18 9:17 ` Nam Cao
2024-04-18 9:17 ` Nam Cao
2024-04-16 18:05 ` Björn Töpel
2024-04-16 18:05 ` Björn Töpel
2024-04-16 18:09 ` Nam Cao
2024-04-16 18:09 ` Nam Cao
2024-04-16 16:19 ` Mike Rapoport
2024-04-16 16:19 ` Mike Rapoport
2024-04-16 16:31 ` Matthew Wilcox
2024-04-16 16:31 ` Matthew Wilcox
2024-04-16 18:18 ` Mike Rapoport
2024-04-16 18:18 ` Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240413-ranging-uselessly-4b1de2210593@spud \
--to=conor@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=anders.roxell@linaro.org \
--cc=bjorn@kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.