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] vfs: fixes for 5.17-rc1
Date: Fri, 4 Feb 2022 18:51:00 -0800 [thread overview]
Message-ID: <20220205025100.GW8313@magnolia> (raw)
Hi Linus,
Please pull this branch of VFS bugfixes for 5.17-rc3. I was auditing
the sync_fs code paths recently and noticed that most callers of
->sync_fs ignore its return value (and many implementations never return
nonzero even if the fs is broken!), which means that internal fs errors
and corruption are not passed up to userspace callers of syncfs(2) or
FIFREEZE. Hence fixing the common code and XFS, and I'll start working
on the ext4/btrfs folks if this is merged.
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 e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/vfs-5.17-fixes-2
for you to fetch changes up to 2d86293c70750e4331e9616aded33ab6b47c299d:
xfs: return errors in xfs_fs_sync_fs (2022-01-30 08:59:47 -0800)
----------------------------------------------------------------
Fixes for 5.17-rc3:
- Fix a bug where callers of ->sync_fs (e.g. sync_filesystem and
syncfs(2)) ignore the return value.
- Fix a bug where callers of sync_filesystem (e.g. fs freeze) ignore
the return value.
- Fix a bug in XFS where xfs_fs_sync_fs never passed back error
returns.
----------------------------------------------------------------
Darrick J. Wong (4):
vfs: make freeze_super abort when sync_filesystem returns error
vfs: make sync_filesystem return errors from ->sync_fs
quota: make dquot_quota_sync return errors from ->sync_fs
xfs: return errors in xfs_fs_sync_fs
fs/quota/dquot.c | 11 ++++++++---
fs/super.c | 19 ++++++++++++-------
fs/sync.c | 18 ++++++++++++------
fs/xfs/xfs_super.c | 6 +++++-
4 files changed, 37 insertions(+), 17 deletions(-)
next reply other threads:[~2022-02-05 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 2:51 Darrick J. Wong [this message]
2022-02-05 17:29 ` [GIT PULL] vfs: fixes for 5.17-rc1 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=20220205025100.GW8313@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 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.