From: wangyan <wangyan122@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2 2/2] ocfs2: use ocfs2_update_inode_fsync_trans() to access t_tid in handle->h_transaction
Date: Sat, 11 Jan 2020 16:47:56 +0800 [thread overview]
Message-ID: <6ff9a312-5f7d-0e27-fb51-bc4e062fcd97@huawei.com> (raw)
In-Reply-To: <03e750ab-9ade-83aa-b000-b9e81e34e539@huawei.com>
For the uniform format, we use ocfs2_update_inode_fsync_trans()
to access t_tid in handle->h_transaction
Signed-off-by: Yan Wang <wangyan122@huawei.com>
Reviewed-by: Jun Piao <piaojun@huawei.com>
---
fs/ocfs2/namei.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c
index 8ea51cf27b97..da65251ef815 100644
--- a/fs/ocfs2/namei.c
+++ b/fs/ocfs2/namei.c
@@ -586,8 +586,7 @@ static int __ocfs2_mknod_locked(struct inode *dir,
mlog_errno(status);
}
- oi->i_sync_tid = handle->h_transaction->t_tid;
- oi->i_datasync_tid = handle->h_transaction->t_tid;
+ ocfs2_update_inode_fsync_trans(handle, inode, 1);
leave:
if (status < 0) {
--
2.19.1
next prev parent reply other threads:[~2020-01-11 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 8:45 [Ocfs2-devel] [PATCH v2 1/2] ocfs2: fix a NULL pointer dereference when call ocfs2_update_inode_fsync_trans() wangyan
2020-01-11 8:47 ` wangyan [this message]
2020-01-12 1:57 ` [Ocfs2-devel] [PATCH v2 2/2] ocfs2: use ocfs2_update_inode_fsync_trans() to access t_tid in handle->h_transaction Joseph Qi
2020-01-12 1:57 ` [Ocfs2-devel] [PATCH v2 1/2] ocfs2: fix a NULL pointer dereference when call ocfs2_update_inode_fsync_trans() 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=6ff9a312-5f7d-0e27-fb51-bc4e062fcd97@huawei.com \
--to=wangyan122@huawei.com \
--cc=ocfs2-devel@oss.oracle.com \
/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.