Hi Eric,
On Fri, Oct 08, 2021 at 01:33:05PM -0400, Eric Whitney wrote:
> Hi, Boris - thanks very much for your report.
sure, np.
> Was your kernel configured with the CONFIG_FS_ENCRYPTION option?
$ grep CONFIG_FS_ENCRYPTION /boot/config-5.15.0-rc4+
# CONFIG_FS_ENCRYPTION is not set
> Could you please provide the output of the mount command for the affected
> file system?
Well, I can't figure out from dmesg - it's all I have from that run -
which fs it was. So lemme give you all ext4 ones:
$ mount | grep ext4
/dev/nvme0n1p2 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sdc1 on /home type ext4 (rw,noatime)
/dev/sda1 on /mnt/oldhome type ext4 (rw,noatime)
/dev/sdb1 on /mnt/smr type ext4 (rw,noatime)
/dev/nvme1n1p1 on /mnt/kernel type ext4 (rw,nosuid,nodev,noatime,user)
> Do you recall what sort of code might have been running on this system at
> the time of failure (for example, kernel build, desktop apps, etc.)?
Good question. I'm not sure. Kernel build is likely as I do those on
that workstation constantly.
Unfortunately, I don't have an exact reproducer. And I can't debug stuff
on that box since it is my workstation and I've reverted it to 5.14.
What I can do is, I can slap 5.15-rc4 or whichever version you'd want me
to, on a test box and try running kernel builds or some other load to
see whether it would fire. I have a similar box to my workstation.
Or if you have a better idea...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
