From: Andrew Morton <akpm@linux-foundation.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Paul Menage <menage@google.com>,
David Rientjes <rientjes@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 4/4] oom: fix oom_adjust_write() input sanity check.
Date: Wed, 5 Aug 2009 16:33:25 -0700 [thread overview]
Message-ID: <20090805163325.14a4a77f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090804192721.6A49.A69D9226@jp.fujitsu.com>
On Tue, 4 Aug 2009 19:28:03 +0900 (JST) KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Subject: [PATCH] oom: fix oom_adjust_write() input sanity check.
>
> Andrew Morton pointed out oom_adjust_write() has very strange EIO
> and new line handling. this patch fixes it.
>
>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Cc: Paul Menage <menage@google.com>
> Cc: David Rientjes <rientjes@google.com>
> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Cc: Rik van Riel <riel@redhat.com>,
> Cc: Andrew Morton <akpm@linux-foundation.org>,
> ---
> fs/proc/base.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> Index: b/fs/proc/base.c
> ===================================================================
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -1033,12 +1033,15 @@ static ssize_t oom_adjust_write(struct f
> count = sizeof(buffer) - 1;
> if (copy_from_user(buffer, buf, count))
> return -EFAULT;
> +
> + strstrip(buffer);
+1 for using strstrip()
-1 for using it wrongly. If it strips leading whitespace it will
return a new address for the caller to use.
We could mark it __must_check() to prevent reoccurences of this error.
How does this look?
--- a/fs/proc/base.c~oom-fix-oom_adjust_write-input-sanity-check-fix
+++ a/fs/proc/base.c
@@ -1033,8 +1033,7 @@ static ssize_t oom_adjust_write(struct f
if (copy_from_user(buffer, buf, count))
return -EFAULT;
- strstrip(buffer);
- oom_adjust = simple_strtol(buffer, &end, 0);
+ oom_adjust = simple_strtol(strstrip(buffer), &end, 0);
if (*end)
return -EINVAL;
if ((oom_adjust < OOM_ADJUST_MIN || oom_adjust > OOM_ADJUST_MAX) &&
> oom_adjust = simple_strtol(buffer, &end, 0);
That should've used strict_strtoul() but it's too late to fix it now.
> + if (*end)
> + return -EINVAL;
> if ((oom_adjust < OOM_ADJUST_MIN || oom_adjust > OOM_ADJUST_MAX) &&
> oom_adjust != OOM_DISABLE)
> return -EINVAL;
> - if (*end == '\n')
> - end++;
> +
> task = get_proc_task(file->f_path.dentry->d_inode);
> if (!task)
> return -ESRCH;
> @@ -1057,9 +1060,8 @@ static ssize_t oom_adjust_write(struct f
> task->signal->oom_adj = oom_adjust;
> unlock_task_sighand(task, &flags);
> put_task_struct(task);
> - if (end - buffer == 0)
> - return -EIO;
> - return end - buffer;
> +
> + return count;
> }
>
> static const struct file_operations proc_oom_adjust_operations = {
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-05 23:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 10:25 [PATCH for 2.6.31 0/4] fix oom_adj regression v2 KOSAKI Motohiro
2009-08-04 10:25 ` [PATCH 1/4] oom: move oom_adj to signal_struct KOSAKI Motohiro
2009-08-05 0:45 ` Minchan Kim
2009-08-05 2:29 ` KOSAKI Motohiro
2009-08-05 2:40 ` Minchan Kim
2009-08-05 2:51 ` KOSAKI Motohiro
2009-08-05 5:55 ` Minchan Kim
2009-08-05 6:03 ` KAMEZAWA Hiroyuki
2009-08-05 6:37 ` Minchan Kim
2009-08-05 6:53 ` KOSAKI Motohiro
2009-08-05 7:20 ` Minchan Kim
2009-08-05 6:55 ` KAMEZAWA Hiroyuki
2009-08-05 6:04 ` KOSAKI Motohiro
2009-08-05 6:29 ` Minchan Kim
2009-08-05 6:47 ` KOSAKI Motohiro
2009-08-06 1:34 ` Oleg Nesterov
2009-08-06 5:16 ` KOSAKI Motohiro
2009-08-04 10:26 ` [PATCH 2/4] oom: make oom_score to per-process value KOSAKI Motohiro
2009-08-04 10:27 ` [PATCH 3/4] oom: oom_kill doesn't kill vfork parent(or child) KOSAKI Motohiro
2009-08-04 10:28 ` [PATCH 4/4] oom: fix oom_adjust_write() input sanity check KOSAKI Motohiro
2009-08-05 23:33 ` Andrew Morton [this message]
2009-08-06 5:06 ` KOSAKI Motohiro
2009-08-05 23:39 ` [PATCH for 2.6.31 0/4] fix oom_adj regression v2 Andrew Morton
2009-08-06 5:13 ` KOSAKI Motohiro
2009-08-06 8:07 ` Minchan Kim
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=20090805163325.14a4a77f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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