public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Keenan <matthew.keenan@ntlworld.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Bug #3054 madvise(MADV_WILLNEED,...) fix for exceeding rlimit rss
Date: Sun, 19 Jun 2005 17:49:31 +0100	[thread overview]
Message-ID: <42B5A21B.5030300@ntlworld.com> (raw)

Here is an updated patch for 2.6.12, can it be included in -mm for 
testing? I have been banging on the code for an hour or so now; no probs.

Matt

--- linux-2.6.11.7/mm/madvise.c 2005-04-12 15:58:30.000000000 +0100
+++ linux/mm/madvise.c  2005-06-19 17:20:56.000000000 +0100
@@ -61,6 +61,7 @@ static long madvise_willneed(struct vm_a
                             unsigned long start, unsigned long end)
 {
        struct file *file = vma->vm_file;
+       struct task_struct *tsk = current;

        if (!file)
                return -EBADF;
@@ -70,6 +71,28 @@ static long madvise_willneed(struct vm_a
                end = vma->vm_end;
        end = ((end - vma->vm_start) >> PAGE_SHIFT) + vma->vm_pgoff;

+       /*
+        * This code below checks to see if mapping the requested
+        * readahead would make the task's rss exceed the task's
+        * rlimit rss.
+        *
+        * This doesn't account for pages that may already be mapped
+        * due to readahead, but since this is merely a hint to the
+        * kernel no harm should be done, it won't unmap anything
+        * already mapped if it fails. N.B. This won't affect the
+        * kernel's internal automatic readahead which doesn't check
+        * (or honour) rlimit rss.
+        */
+
+       spin_lock(&tsk->mm->page_table_lock);
+       if (((max_sane_readahead(end-start) << PAGE_SHIFT) +
+           tsk->mm->_rss) > tsk->signal->rlim[RLIMIT_RSS].rlim_cur)
+       {
+               spin_unlock(&tsk->mm->page_table_lock);
+               return -EIO;
+       }
+       spin_unlock(&tsk->mm->page_table_lock);
+
        force_page_cache_readahead(file->f_mapping,
                        file, start, max_sane_readahead(end - start));
        return 0;
@@ -170,6 +193,8 @@ static long madvise_vma(struct vm_area_s
  *  -ENOMEM - addresses in the specified range are not currently
  *             mapped, or are outside the AS of the process.
  *  -EIO    - an I/O error occurred while paging in data.
+ *          - MADV_WILLNEED would map in pages that would make the task's
+ *              rss exceed rlimit rss.
  *  -EBADF  - map exists, but area maps something that isn't a file.
  *  -EAGAIN - a kernel resource was temporarily unavailable.
  */


             reply	other threads:[~2005-06-19 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-19 16:49 Matt Keenan [this message]
2005-06-19 20:23 ` [PATCH] Bug #3054 madvise(MADV_WILLNEED,...) fix for exceeding rlimit rss Chris Wright
2005-06-19 21:09   ` Matt Keenan

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=42B5A21B.5030300@ntlworld.com \
    --to=matthew.keenan@ntlworld.com \
    --cc=akpm@osdl.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