All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220818] New: kernel 6.8.0-88: General Protection Fault (GPF) in ext4 while running 'umount': RIP: 0010:dentry_unlink_inode+0x52/0x150
Date: Mon, 01 Dec 2025 00:39:22 +0000	[thread overview]
Message-ID: <bug-220818-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220818

            Bug ID: 220818
           Summary: kernel 6.8.0-88: General Protection Fault (GPF) in
                    ext4 while running 'umount': RIP:
                    0010:dentry_unlink_inode+0x52/0x150
           Product: File System
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: ubuntu@yendor.com
        Regression: No

Created attachment 308991
  --> https://bugzilla.kernel.org/attachment.cgi?id=308991&action=edit
Relevant lines from syslog of crash

Getting a reproducible GPF in ext4 filesystem dentry_unlink_inode while running
userland 'sudo umount /media/some-mountpoint' after a large backup where many
modifications are waiting to be flushed to disk.


System is amdgpu multicore if that is relevant.

Kernel is: 6.8.0-88-generic.


Full kernel GPF report in the attachment.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2025-12-01  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  0:39 bugzilla-daemon [this message]
2025-12-01  0:40 ` [Bug 220818] kernel 6.8.0-88: General Protection Fault (GPF) in ext4 while running 'umount': RIP: 0010:dentry_unlink_inode+0x52/0x150 bugzilla-daemon
2025-12-01 11:30 ` bugzilla-daemon

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=bug-220818-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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.