From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 205833] fsfreeze blocks close(fd) on xfs sometimes
Date: Mon, 09 Oct 2023 15:37:06 +0000 [thread overview]
Message-ID: <bug-205833-201763-gRWgxmYuFQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205833-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205833
Коренберг Марк (socketpair@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |socketpair@gmail.com
--- Comment #5 from Коренберг Марк (socketpair@gmail.com) ---
https://bugzilla.redhat.com/show_bug.cgi?id=1474726 the same bug
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2023-10-09 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:03 [Bug 205833] New: fsfreeze blocks close(fd) on xfs sometimes bugzilla-daemon
2019-12-12 18:01 ` Brian Foster
2019-12-12 18:01 ` [Bug 205833] " bugzilla-daemon
2019-12-17 9:34 ` bugzilla-daemon
2019-12-17 12:03 ` Brian Foster
2019-12-17 12:03 ` bugzilla-daemon
2022-09-05 14:29 ` bugzilla-daemon
2023-10-09 15:37 ` 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-205833-201763-gRWgxmYuFQ@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).