From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216031] forced kernel crash soon after startup exposes XFS growfs race condition
Date: Wed, 12 Nov 2025 02:32:13 +0000 [thread overview]
Message-ID: <bug-216031-201763-4B599n5Z93@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216031-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216031
Eric Sandeen (sandeen@sandeen.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@sandeen.net
--- Comment #1 from Eric Sandeen (sandeen@sandeen.net) ---
I retested the reproducer on 6.15 and saw no errors.
I'm not entirely sure when or how this got fixed, but it seems to be fixed now,
so closing.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-11-12 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 20:36 [Bug 216031] New: forced kernel crash soon after startup exposes XFS growfs race condition bugzilla-daemon
2025-11-12 2:32 ` bugzilla-daemon [this message]
2025-11-12 5:03 ` [Bug 216031] " Nirjhar Roy (IBM)
2025-11-12 2:32 ` bugzilla-daemon
2025-11-12 5:04 ` 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-216031-201763-4B599n5Z93@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@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.