From: Su Yue <glass.su@suse.com>
To: ocfs2-devel@lists.linux.dev
Cc: joseph.qi@linux.alibaba.com, Su Yue <glass.su@suse.com>
Subject: [PATCH 0/4] ocfs2 bugs fixes exposed by fstests
Date: Sun, 31 Mar 2024 19:17:40 +0800 [thread overview]
Message-ID: <20240331111744.7224-1-l@damenly.org> (raw)
From: Su Yue <glass.su@suse.com>
The patchset is to fix some wrong behavior of ocfs2 exposed
by fstests.
Patch 1,2 are about aio+dio vs hole punching. generic/300
Patch 3 fixes inode link count mismatch after power failure.
tests/generic/040,041,104,107,336
patch fixes wrong atime with mount option realtime. tests/generic/192
Su Yue (4):
ocfs2: return real error code in ocfs2_dio_wr_get_block
ocfs2: fix races between hole punching and AIO+DIO
ocfs2: update inode fsync transaction id in ocfs2_unlink and
ocfs2_link
ocfs2: use coarse time for new created files
fs/ocfs2/aops.c | 2 --
fs/ocfs2/file.c | 2 ++
fs/ocfs2/namei.c | 4 +++-
3 files changed, 5 insertions(+), 3 deletions(-)
--
2.44.0
next reply other threads:[~2024-03-31 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 11:17 Su Yue [this message]
2024-03-31 11:17 ` [PATCH 1/4] ocfs2: return real error code in ocfs2_dio_wr_get_block Su Yue
2024-04-01 1:44 ` Joseph Qi
2024-04-01 3:51 ` Su Yue
2024-03-31 11:17 ` [PATCH 2/4] ocfs2: fix races between hole punching and AIO+DIO Su Yue
2024-04-01 1:52 ` Joseph Qi
2024-03-31 11:17 ` [PATCH 3/4] ocfs2: update inode fsync transaction id in ocfs2_unlink and ocfs2_link Su Yue
2024-04-01 1:55 ` Joseph Qi
2024-03-31 11:17 ` [PATCH 4/4] ocfs2: use coarse time for new created files Su Yue
2024-04-01 2:02 ` Joseph Qi
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=20240331111744.7224-1-l@damenly.org \
--to=glass.su@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=ocfs2-devel@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).