madvise(2) actually returns with error EINVAL for MADV_REMOVE when used
for hugetlb vmas, not EOPNOTSUPP, and this has been the case since
MADV_REMOVE was introduced in commit f6b3ec238d12 ("madvise(MADV_REMOVE):
remove pages from tmpfs shm backing store").
Specify the exact behavior.
Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx>
---
man2/madvise.2 | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/man2/madvise.2 b/man2/madvise.2
index a3d93bb..00db39d 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -184,7 +184,9 @@ any filesystem which supports the
.BR FALLOC_FL_PUNCH_HOLE
mode also supports
.BR MADV_REMOVE .
-Other filesystems fail with the error
+Hugetlbfs will fail with the error
+.BR EINVAL
+and other filesystems fail with the error
.BR EOPNOTSUPP .
.TP
.BR MADV_DONTFORK " (since Linux 2.6.16)"
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>