From: Borislav Petkov <bp@alien8.de>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: kernel BUG at fs/ext4/inode.c:1721!
Date: Fri, 8 Oct 2021 20:20:08 +0200 [thread overview]
Message-ID: <YWCL2OXaz8/OnBiF@zn.tnic> (raw)
In-Reply-To: <20211008173305.GA28198@localhost.localdomain>
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
next prev parent reply other threads:[~2021-10-08 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 9:19 kernel BUG at fs/ext4/inode.c:1721! Borislav Petkov
2021-10-08 17:33 ` Eric Whitney
2021-10-08 18:20 ` Borislav Petkov [this message]
2021-10-11 23:11 ` Eric Whitney
2021-10-12 18:39 ` Borislav Petkov
2021-10-20 16:38 ` Jan Kara
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=YWCL2OXaz8/OnBiF@zn.tnic \
--to=bp@alien8.de \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.