From: Daniel Gollub <dgollub@suse.de>
To: linux-kernel@vger.kernel.org
Cc: linux-api@vger.kernel.org
Cc: linux-man@vger.kernel.org
Cc: ltp-list@lists.sourceforge.net
Subject: [patch 2/3] [man-pages] Remove "bufsize is not positive" from readlink(2) error section
Date: Thu, 23 Oct 2008 16:50:57 +0200 [thread overview]
Message-ID: <20081023150549.038994457@marvin.suse.de> (raw)
In-Reply-To: <20081023145054.998439866@marvin.suse.de>
[-- Attachment #1: man-pages-readlink-2.diff --]
[-- Type: text/plain, Size: 778 bytes --]
The error statement "bufsize is not positive" is obsolete, if this proposed
syscall interface change get accepted.
Note: Kernel 2.6.27 and older shipped sys_readlink with a signed "bufsiz"
argument. Man-page document the readlink syscall always as unsigend (size_t).
Signed-off-by: Daniel Gollub <dgollub@suse.de>
---
man2/readlink.2 | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/man2/readlink.2 b/man2/readlink.2
index b94db21..470c222 100644
--- a/man2/readlink.2
+++ b/man2/readlink.2
@@ -86,10 +86,6 @@ Search permission is denied for a component of the path prefix.
extends outside the process's allocated address space.
.TP
.B EINVAL
-.I bufsiz
-is not positive.
-.TP
-.B EINVAL
The named file is not a symbolic link.
.TP
.B EIO
next prev parent reply other threads:[~2008-10-23 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 14:50 [patch 0/3] [RFC] kernel/glibc mismatch of "readlink" syscall? Daniel Gollub
2008-10-23 14:50 ` [patch 1/3] [RFC] Change sys_readlink/sys_readlinkat buffer size parameter to size_t (POSIX mismatch) Daniel Gollub
2008-10-23 14:50 ` Daniel Gollub [this message]
2008-10-23 14:50 ` [patch 3/3] [ltp] Remove testcase for "Buffer size is not positive" in kernel/syscalls/readlink/readlink03 Daniel Gollub
2008-10-24 22:53 ` [patch 0/3] [RFC] kernel/glibc mismatch of "readlink" syscall? Michael Kerrisk
2008-10-28 9:11 ` Andries E. Brouwer
2008-10-31 15:02 ` Kai Henningsen
2008-10-31 15:37 ` Daniel Gollub
2008-11-04 16:20 ` Michael Kerrisk
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=20081023150549.038994457@marvin.suse.de \
--to=dgollub@suse.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome