aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdhemerval Zanella <adhemerval.zanella@linaro.org>2018-07-10 09:24:40 -0300
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2018-07-10 10:28:39 -0300
commitb444e8f7cc40265c9a20ce5de5f3f6795b7f5028 (patch)
tree440690b09fe22481ad1a6acb59cac784a50cbc2f
parent7b2f4cedf044ea83f53f6b43a5bf6871eb9ce969 (diff)
downloadglibc-b444e8f7cc40265c9a20ce5de5f3f6795b7f5028.tar
glibc-b444e8f7cc40265c9a20ce5de5f3f6795b7f5028.tar.gz
glibc-b444e8f7cc40265c9a20ce5de5f3f6795b7f5028.tar.bz2
glibc-b444e8f7cc40265c9a20ce5de5f3f6795b7f5028.zip
Comment tst-ofdlocks-compat expected failure in some Linux releases
As pointed out in a libc-alpha thread [1], the misc/tst-ofdlocks-compat may fail in some specific Linux releases. This patch adds a comment along with a link to discussion in the test source code. No changes are expected. * sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c: Add a comment about a kernel issue which lead to test failure in some cases. [1] https://sourceware.org/ml/libc-alpha/2018-07/msg00243.html
-rw-r--r--ChangeLog5
-rw-r--r--sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c8
2 files changed, 13 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index d18c24453f..f21b5ad6ff 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2018-07-10 Adhemerval Zanella <adhemerval.zanella@linaro.org>
+
+ * sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c: Add a comment about
+ a kernel issue which lead to test failure in some cases.
+
2018-07-10 Florian Weimer <fweimer@redhat.com>
[BZ #23036]
diff --git a/sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c b/sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c
index d1d00eb3fb..03c4abfeff 100644
--- a/sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c
+++ b/sysdeps/unix/sysv/linux/tst-ofdlocks-compat.c
@@ -40,6 +40,14 @@ do_prepare (int argc, char **argv)
#define PREPARE do_prepare
+/* Linux between 4.13 and 4.15 return EOVERFLOW for LFS OFD locks usage
+ in compat mode (non-LFS ABI running on a LFS default kernel, such as
+ i386 on a x86_64 kernel or s390-32 on a s390-64 kernel) [1]. This is
+ a kernel issue because __NR_fcntl64 is the expected way to use OFD locks
+ (used on GLIBC for both fcntl and fcntl64).
+
+ [1] https://sourceware.org/ml/libc-alpha/2018-07/msg00243.html */
+
static int
do_test (void)
{