From: Aurelien Jarno <aurelien@aurel32.net>
To: libc-stable@sourceware.org
Cc: Joseph Myers <joseph@codesourcery.com>
Subject: [COMMITTED 2.24] Fix MIPS n64 readahead (bug 21026).
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <20170409182208.8066-1-aurelien@aurel32.net> (raw)
From: Joseph Myers <joseph@codesourcery.com>
As noted in bug 20126, MIPS n64 uses an incorrect implementation of
readahead intended for 32-bit systems. This patch adds a
syscalls.list entry to fix this. An updated version of the
consolidation patch
<https://sourceware.org/ml/libc-alpha/2016-09/msg00527.html> could
remove this syscalls.list entry again.
Tested with compilation (only) for mips64; the nature of the syscall
doesn't allow for a glibc test to detect this issue.
[BZ #21026]
* sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list
(readahead): New syscall entry.
(cherry picked from commit 30733525c6867c160261db1afade6326000f9f75)
---
ChangeLog | 6 ++++++
sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list | 2 ++
2 files changed, 8 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 6e4696c7df..13f809d26f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2017-01-05 Joseph Myers <joseph@codesourcery.com>
+
+ [BZ #21026]
+ * sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list
+ (readahead): New syscall entry.
+
2017-04-07 H.J. Lu <hongjiu.lu@intel.com>
[BZ #21258]
diff --git a/sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list b/sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list
index 890a74494a..26ab6d0b75 100644
--- a/sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list
+++ b/sysdeps/unix/sysv/linux/mips/mips64/n64/syscalls.list
@@ -4,6 +4,8 @@ mmap - mmap b:aniiii __mmap mmap __mmap64 mmap64
sync_file_range - sync_file_range Ci:iiii sync_file_range
+readahead - readahead i:iii __readahead readahead
+
prlimit EXTRA prlimit64 i:iipp prlimit prlimit64
fanotify_mark EXTRA fanotify_mark i:iiiis fanotify_mark
--
2.11.0
reply other threads:[~2017-04-09 18:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170409182208.8066-1-aurelien@aurel32.net \
--to=aurelien@aurel32.net \
--cc=joseph@codesourcery.com \
--cc=libc-stable@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).