linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216110] rmdir sub directory cause i_nlink of parent directory down from 0 to 0xffffffff
Date: Wed, 22 Jun 2022 23:39:10 +0000	[thread overview]
Message-ID: <bug-216110-201763-qG72xa3PnS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216110-201763@https.bugzilla.kernel.org/>

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

Eric Sandeen (sandeen@sandeen.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |sandeen@sandeen.net
         Resolution|---                         |INVALID

--- Comment #5 from Eric Sandeen (sandeen@sandeen.net) ---
I agree with Darrick here, this is the upstream bug tracker, and upstream can't
help users with distribution kernels, especially on older distributions.

-Eric

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

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

  parent reply	other threads:[~2022-06-22 23:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  8:27 [Bug 216110] New: rmdir sub directory cause i_nlink of parent directory down from 0 to 0xffffffff bugzilla-daemon
2022-06-10  8:30 ` [Bug 216110] " bugzilla-daemon
2022-06-10  8:31 ` bugzilla-daemon
2022-06-10 14:44 ` bugzilla-daemon
2022-06-22 23:08 ` [Bug 216110] New: " Darrick J. Wong
2022-06-22 23:08 ` [Bug 216110] " bugzilla-daemon
2022-06-22 23:39 ` bugzilla-daemon [this message]
2023-06-15  3:35 ` 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-216110-201763-qG72xa3PnS@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;
as well as URLs for NNTP newsgroup(s).