From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: fixes for 5.17-rc6
Date: Fri, 25 Feb 2022 21:04:21 -0800 [thread overview]
Message-ID: <20220226050421.GZ8313@magnolia> (raw)
Hi Linus,
Please pull this branch containing bug fixes for XFS for 5.17-rc6.
There's nothing exciting, just more fixes for not returning
sync_filesystem error values (and eliding it when it's not necessary).
As usual, I did a test-merge with upstream master as of a few minutes
ago, and didn't see any conflicts. Please let me know if you encounter
any problems.
--D
The following changes since commit cea267c235e1b1ec3bfc415f6bd420289bcb3bc9:
xfs: ensure log flush at the end of a synchronous fallocate call (2022-02-01 14:14:48 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.17-fixes-2
for you to fetch changes up to b97cca3ba9098522e5a1c3388764ead42640c1a5:
xfs: only bother with sync_filesystem during readonly remount (2022-02-09 21:07:24 -0800)
----------------------------------------------------------------
Bug fixes for 5.17-rc4:
- Only call sync_filesystem when we're remounting the filesystem
readonly readonly, and actually check its return value.
----------------------------------------------------------------
Darrick J. Wong (1):
xfs: only bother with sync_filesystem during readonly remount
fs/xfs/xfs_super.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2022-02-26 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 5:04 Darrick J. Wong [this message]
2022-02-26 19:08 ` pr-tracker-bot
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=20220226050421.GZ8313@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®