public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: suzuki <suzuki@in.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [RFC] [PATCH] madvise() does not always return -EBADF on non-file mapped area
Date: Fri, 01 Jul 2005 16:25:07 +0530	[thread overview]
Message-ID: <42C5210B.8080806@in.ibm.com> (raw)

hi,

madvise() system call returns -EBADF for areas which does not map to 
files, only for *behaviour* request MADV_WILLNEED.

Is it the intended behaviour of madvise() ?

According to man pages, madvise returns :

EBADF - the map exists, but the area maps something that isn’t a file.

I have attached a patch which could resolve the issue.

-- 
regards,

Suzuki K P
Linux Technology Centre,
IBM Software Labs,
India.



Patch to fix madvise() to return -EBADF for non-file mapped area on any 
requested behaviour.

Signed Off by : Suzuki K P <suzuki@in.ibm.com>
================================================

--- mm/madvise.c        2005-07-01 16:08:26.000000000 +0530
+++ mm/madvise.c.new    2005-07-01 16:07:45.000000000 +0530
@@ -62,9 +62,6 @@ static long madvise_willneed(struct vm_a
  {
         struct file *file = vma->vm_file;

-       if (!file)
-               return -EBADF;
-
         start = ((start - vma->vm_start) >> PAGE_SHIFT) + vma->vm_pgoff;
         if (end > vma->vm_end)
                 end = vma->vm_end;
@@ -114,8 +111,12 @@ static long madvise_dontneed(struct vm_a
  static long madvise_vma(struct vm_area_struct * vma, unsigned long start,
                         unsigned long end, int behavior)
  {
+       struct file* filp = vma->vm_file;
         long error = -EBADF;

+       if(!filp)
+               goto  out;
+
         switch (behavior) {
         case MADV_NORMAL:
         case MADV_SEQUENTIAL:
@@ -136,6 +137,7 @@ static long madvise_vma(struct vm_area_s
                 break;
         }

+out:
         return error;
  }


                 reply	other threads:[~2005-07-01 10:48 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=42C5210B.8080806@in.ibm.com \
    --to=suzuki@in.ibm.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