From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Cc: djwong@kernel.org
Subject: [ANNOUNCE] xfs: for-next updated to 9419092fb263
Date: Thu, 27 Apr 2023 09:11:12 +1000 [thread overview]
Message-ID: <20230426231112.GK3223426@dread.disaster.area> (raw)
Hi folks,
I just merged the fix for the ENOSPC delayed allocation regression
into the for-next branch. I did this because I don't really want to
expose what appears to be (now that we know about it) an easily
triggered livelock as a result of stripe aligned allocation fallback
issues. I'll let this got through a linux-next cycle and then send a
pull request to Linus as the tree stands.
-Dave.
----------------------------------------------------------------
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
Head Commit: 9419092fb2630c30e4ffeb9ef61007ef0c61827a
xfs: fix livelock in delayed allocation at ENOSPC (2023-04-27 09:02:11 +1000)
----------------------------------------------------------------
Dave Chinner (1):
xfs: fix livelock in delayed allocation at ENOSPC
fs/xfs/libxfs/xfs_bmap.c | 1 -
1 file changed, 1 deletion(-)
--
Dave Chinner
david@fromorbit.com
reply other threads:[~2023-04-26 23:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230426231112.GK3223426@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@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