From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 210723] [Bug report] overlayfs over xfs whiteout operation may cause deadlock
Date: Mon, 04 Jan 2021 19:34:07 +0000 [thread overview]
Message-ID: <bug-210723-201763-4hRnQHA4VI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210723-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210723
--- Comment #2 from bfoster@redhat.com ---
On Mon, Jan 04, 2021 at 03:09:23PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=210723
>
> --- Comment #1 from Dave (chiluk@ubuntu.com) ---
> Has there been any progress on this? We've been regularly hitting what
> appears
> to be an xfs deadlock on 5.8, 5.9, and now 5.10 on our kubernetes nodes that
> also employ containers and overlayfs. I haven't been able to do as much
> digging as wenli yet so I don't have any more detailed information.
>
For whatever reason this bug report has not been synced between bugzilla
and the mailing list. I don't see the initial report on the list at all
and the subsequent replies to the initial thread appear on the list and
not in the bz.
In any event, I believe Darrick root caused and Wenli confirmed a fix
here:
https://lore.kernel.org/linux-xfs/20201217211117.GF38809@magnolia/
... which presumably just needs to be posted/reviewed as a proper patch.
Brian
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are watching the assignee of the 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:[~2021-01-04 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-210723-201763@https.bugzilla.kernel.org/>
2021-01-04 15:09 ` [Bug 210723] [Bug report] overlayfs over xfs whiteout operation may cause deadlock bugzilla-daemon
2021-01-04 19:33 ` Brian Foster
2021-01-04 19:34 ` 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-210723-201763-4hRnQHA4VI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.