[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.00.0908121642300.22028@mail.selltech.ca>
Date: Wed, 12 Aug 2009 16:46:15 -0700 (PDT)
From: "Li, Ming Chun" <macli@....ubc.ca>
To: David Rientjes <rientjes@...gle.com>
Cc: Vincent Li <macli@....ubc.ca>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] fs/proc/task_mmu.c: fix clear_refs_write() input sanity
check
On Wed, 12 Aug 2009, David Rientjes wrote:
> On Wed, 12 Aug 2009, Vincent Li wrote:
>
> > diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> > index 2079969..026b532 100644
> > --- a/fs/proc/task_mmu.c
> > +++ b/fs/proc/task_mmu.c
> > @@ -494,18 +494,17 @@ static ssize_t clear_refs_write(struct file *file, const char __user *buf,
> > char buffer[PROC_NUMBUF], *end;
> > struct mm_struct *mm;
> > struct vm_area_struct *vma;
> > - int type;
> > + long res;
> >
>
> What does `res' mean? Why can't it just be left as `type'?
res mean the result parsed from userspace input, I can keep it as name
'type'.
>
> > memset(buffer, 0, sizeof(buffer));
> > if (count > sizeof(buffer) - 1)
> > count = sizeof(buffer) - 1;
> > if (copy_from_user(buffer, buf, count))
> > return -EFAULT;
> > - type = simple_strtol(buffer, &end, 0);
> > - if (type < CLEAR_REFS_ALL || type > CLEAR_REFS_MAPPED)
> > + if (strict_strtol(strstrip(buffer), 10, &res)
> > + return -EINVAL;
>
> Please test your patch submissions (which would require that the above
> actually compiles).
>
I did get compiling error and warnings, I will resend the patch with
varible name 'type' left and no compiling errors.
Vincent Li
Biomedical Research Center
University of British Columbia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists