On Mon, Aug 15, 2022 at 8:46 AM Vishal Verma <vverma@xxxxxxxxxxxxxxxx> wrote: > > Just saw this. I’m trying to understand whether this happens only on md array or individual nvme drives (without any raid) too? > The commit you pointed added REQ_NOWAIT for md based arrays, but if it is happening on individual nvme drives then that could point to something with REQ_NOWAIT I think. Agreed with this analysis. > > > On Aug 15, 2022, at 3:58 AM, Thorsten Leemhuis <regressions@xxxxxxxxxxxxx> wrote: > > > > Hi, this is your Linux kernel regression tracker. Top-posting for once, > > to make this easily accessible to everyone. > > > > [CCing Jens, as the top-level maintainer who in this case also reviewed > > the patch that causes this regression.] > > > > Vishal, Song, what up here? Could you please look into this and at least > > comment on the issue, as it's a regression that was reported more than > > 10 days ago already. Ideally at this point it would be good if the > > regression was fixed already, as explained by "Prioritize work on fixing > > regressions" here: > > https://docs.kernel.org/process/handling-regressions.html#prioritize-work-on-fixing-regressions I am sorry for the delay. [...] > >> > >> Hi, > >> > >> any news on this? Is there anything else you need from me or I can help > >> with? > >> > >> Thanks. > >> > >> > >> -- Regards, Thomas -----Original Message----- From: Thomas Deutschmann > >> <whissi@xxxxxxxxx> Sent: Wednesday, August 3, 2022 4:35 PM To: > >> vverma@xxxxxxxxxxxxxxxx; song@xxxxxxxxxx Cc: stable@xxxxxxxxxxxxxxx; > >> regressions@xxxxxxxxxxxxxxx Subject: [REGRESSION] v5.17-rc1+: FIFREEZE > >> ioctl system call hangs Hi, while trying to backup a Dell R7525 system > >> running Debian bookworm/testing using LVM snapshots I noticed that the > >> system will 'freeze' sometimes (not all the times) when creating the > >> snapshot. First I thought this was related to LVM so I created > >> https://listman.redhat.com/archives/linux-lvm/2022-July/026228.html > >> (continued at > >> https://listman.redhat.com/archives/linux-lvm/2022-August/thread.html#26229) Long story short: I was even able to reproduce with fsfreeze, see last strace lines > >>> [...] > >>> 14471 1659449870.984635 openat(AT_FDCWD, "/var/lib/machines", O_RDONLY) =3 > >>> 14471 1659449870.984658 newfstatat(3, "", > >> {st_mode=S_IFDIR|0700,st_size=4096, ...}, AT_EMPTY_PATH) = 0 > >>> 14471 1659449870.984678 ioctl(3, FIFREEZE > >> so I started to bisect kernel and found the following bad commit: I am not able to reproduce this on 5.19+ kernel. I have: [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 ~]# for x in {1..100} ; do fsfreeze --unfreeze /root/mnt ; fsfreeze --freeze /root/mnt ; done Did I miss something? Thanks, Song [...]
