Linux XFS filesystem development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 222081] New: xfs stops if link count is to high
Date: Wed, 30 Sep 2026 19:06:32 +0000	[thread overview]
Message-ID: <bug-222081-201763@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 222081
           Summary: xfs stops if link count is to high
           Product: File System
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: sachse@gmx.net
        Regression: No

Created attachment 310977
  --> https://bugzilla.kernel.org/attachment.cgi?id=310977&action=edit
Kernel trace

Environment is an docker on a xfs with overlay.
Inside the docker a bitbake/yocto build is running.

Is link count reaches 552 an allocation error occours and the filesystem is
stopped.

Kernels: 6.18.28 and 6.18.48

-- 
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:[~2026-09-30 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 19:06 bugzilla-daemon [this message]
2026-09-30 19:07 ` [Bug 222081] xfs stops if link count is to high bugzilla-daemon
2026-09-30 19:13 ` bugzilla-daemon
2026-09-30 19:13 ` bugzilla-daemon
2026-09-30 20:24 ` bugzilla-daemon
2026-10-06  4:43   ` Darrick J. Wong
2026-10-06  4:43 ` bugzilla-daemon
2026-10-07  7:50 ` bugzilla-daemon
2026-10-07 15:10   ` Darrick J. Wong
2026-10-07 15:11 ` 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-222081-201763@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox