Re: [REGRESSION] v5.17-rc1+: FIFREEZE ioctl system call hangs

[Song Liu <song@kernel.org>]

On Mon, Aug 22, 2022 at 3:44 PM Thomas Deutschmann <whissi@whissi.de> wrote:
>
> On 2022-08-22 23:52, Song Liu wrote:
> > Hmm.. I still cannot repro the hang in my test. I have:
> >
> > [root@eth50-1 ~]# mount | grep mnt
> > /dev/md0 on /root/mnt type ext4 (rw,relatime,stripe=384)
> > [root@eth50-1 ~]# lsblk
> > NAME    MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
> > sr0      11:0    1 1024M  0 rom
> > vda     253:0    0   32G  0 disk
> > ├─vda1  253:1    0    2G  0 part  /boot
> > └─vda2  253:2    0   30G  0 part  /
> > nvme0n1 259:0    0    4G  0 disk
> > └─md0     9:0    0   12G  0 raid5 /root/mnt
> > nvme2n1 259:1    0    4G  0 disk
> > └─md0     9:0    0   12G  0 raid5 /root/mnt
> > nvme3n1 259:2    0    4G  0 disk
> > └─md0     9:0    0   12G  0 raid5 /root/mnt
> > nvme1n1 259:3    0    4G  0 disk
> > └─md0     9:0    0   12G  0 raid5 /root/mnt
> >
> > [root@eth50-1 ~]# history
> >    381  fio iou/repro.fio
> >    382  fsfreeze --freeze /root/mnt
> >    383  fsfreeze --unfreeze /root/mnt
> >    384  fio iou/repro.fio
> >    385  fsfreeze --freeze /root/mnt
> >    386  fsfreeze --unfreeze /root/mnt
> > ^^^^^^^^^^^^^^ all works fine.
> >
> > Did I miss something?
>
> No :(
>
> I am currently not testing against the mdraid but this shouldn't matter.
>
> However, it looks like you don't test on bare metal, do you?
>
> I tried to test on VMware Workstation 16 myself but VMware's nvme
> implementation is currently broken
> (https://github.com/vmware/open-vm-tools/issues/579).

I am testing with QEMU emulator version 6.2.0. I can also test with
bare metal.

Thanks,
Song