From: Kyle Evans <kev...@freebsd.org>

Lack of SHM_GROW_ON_WRITE is actively breaking Python's memfd_create tests,
so go ahead and implement it. A future change will make memfd_create always
set SHM_GROW_ON_WRITE, to match Linux behavior and unbreak Python's tests
on -CURRENT.

Reviewed by:    kib
Differential Revision:  https://reviews.freebsd.org/D25502
---
 newlib/libc/sys/rtems/include/sys/mman.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/newlib/libc/sys/rtems/include/sys/mman.h 
b/newlib/libc/sys/rtems/include/sys/mman.h
index 7a9b49429..99c1eb8b3 100644
--- a/newlib/libc/sys/rtems/include/sys/mman.h
+++ b/newlib/libc/sys/rtems/include/sys/mman.h
@@ -190,6 +190,7 @@
  * shmflags for shm_open2()
  */
 #define        SHM_ALLOW_SEALING               0x00000001
+#define        SHM_GROW_ON_WRITE               0x00000002
 
 /*
  * Flags for memfd_create().
-- 
2.35.3

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to