From 0230e4fda217b5e72edd95e109a29955d45efc1c Mon Sep 17 00:00:00 2001
From: Leo Yuriev <leo@yuriev.ru>
Date: Thu, 19 Nov 2015 13:56:54 +0300
Subject: [PATCH] mdbx: clarify fsync/fdatasync comment.

Change-Id: I2209b5e65ca8c04ff2de9b1b789f1993f24ab454
---
 mdb.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/mdb.c b/mdb.c
index 1e435187..31cc7c48 100644
--- a/mdb.c
+++ b/mdb.c
@@ -4054,7 +4054,8 @@ mdb_env_sync0(MDB_env *env, unsigned flags, MDB_meta *pending)
 			if (unlikely(prev_mapsize != pending->mm_mapsize)) {
 				/* LY: It is no reason to use fdatasync() here, even in case
 				 * no such bug in a kernel. Because "no-bug" mean that a kernel
-				 * internally do nearly the same.
+				 * internally do nearly the same, e.g. fdatasync() == fsync()
+				 * when no-kernel-bug and file size was changed.
 				 *
 				 * So, this code is always safe and without appreciable
 				 * performance degradation.