All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216981] Online file system resize stuck for ext3
Date: Tue, 31 Jan 2023 16:01:41 +0000	[thread overview]
Message-ID: <bug-216981-13602-ChatvmM31I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216981-13602@https.bugzilla.kernel.org/>

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

Theodore Tso (tytso@mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
               Tree|Mainline                    |Fedora
                 CC|                            |tytso@mit.edu
         Resolution|---                         |INVALID

--- Comment #1 from Theodore Tso (tytso@mit.edu) ---
This is a bug report for a Red Hat kernel, not mainstream.  It's also as a
result, an absolutely antique, antedeluvian kernel from an upstream kernel. 
Please report this problem to Red Hat, and they will provide support --- not
upstream maintainers.

Alternatively, please try to see if the problem can be replicated on the latest
upstream kernel.  If it can be, feel free to open a new bug and specify an
upstream kernel version in the bug report.

-- 
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:[~2023-01-31 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 15:23 [Bug 216981] New: Online resize of ext3 file system stuck bugzilla-daemon
2023-01-31 15:27 ` [Bug 216981] Online file system resize stuck for ext3 bugzilla-daemon
2023-01-31 16:01 ` bugzilla-daemon [this message]

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-216981-13602-ChatvmM31I@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.