From: Valentine Barshak <vbarshak@ru.mvista.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: posix_fadvise succeeds on FIFO.
Date: Tue, 06 Dec 2005 23:34:12 +0300 [thread overview]
Message-ID: <4395F5C4.8080701@ru.mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
Hello all.
The following issue has been found with posix_fadvise:
the system call succeeds on a pipe or FIFO, although it has to fail with
EINVAL return value on linux.
I've attached a small test for posix_fadvise and a patch for linux
kernel 2.6.14 that fixes the problem.
The patch makes posix_fadvise return ESPIPE on FIFO/pipe in order to be
fully POSIX-compliant.
Please, take a look at these. Is it really a bug in kernel?
Thanks.
[-- Attachment #2: posix_fadvise_test.c --]
[-- Type: text/x-csrc, Size: 792 bytes --]
#define _GNU_SOURCE
#include <stdio.h>
#include <unistd.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/stat.h>
#include <sys/types.h>
#include <errno.h>
int main()
{
int retval, fd;
if (mkfifo("fifo", 0666) < 0) {
printf("create fifo error\n");
return 1;
}
fd = open("fifo", O_RDWR);
if (fd < 0) {
printf("open fifo error\n");
remove("fifo");
return 1;
}
retval = posix_fadvise(fd, 0, 0, POSIX_FADV_NORMAL);
if (retval) {
printf("Expected fail - The fd argument is associated with a pipe or FIFO.\n");
if (retval != ESPIPE)
printf("Unexpected ERRNO %d (Expected %d)\n", retval, ESPIPE);
} else
printf("Unexpected success - The fd argument is associated with a pipe or FIFO.\n");
close(fd);
remove("fifo");
if (retval)
return 0;
return 1;
}
[-- Attachment #3: fadv.patch --]
[-- Type: text/x-patch, Size: 409 bytes --]
--- a/mm/fadvise.c 2005-10-10 22:54:29.000000000 +0400
+++ b/mm/fadvise.c 2005-12-06 23:04:19.980711464 +0300
@@ -37,6 +37,11 @@
if (!file)
return -EBADF;
+ if (S_ISFIFO(file->f_dentry->d_inode->i_mode)) {
+ ret = -ESPIPE;
+ goto out;
+ }
+
mapping = file->f_mapping;
if (!mapping || len < 0) {
ret = -EINVAL;
reply other threads:[~2005-12-06 20:35 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=4395F5C4.8080701@ru.mvista.com \
--to=vbarshak@ru.mvista.com \
--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