From: Dan Carpenter <error27@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] cifs: writing past the end of the array
Date: Tue, 08 Mar 2011 11:05:12 +0000 [thread overview]
Message-ID: <20110308110512.GB3416@bicker> (raw)
In-Reply-To: <20110306132621.GN3416@bicker>
On Tue, Mar 08, 2011 at 09:25:36AM +0100, walter harms wrote:
> >>> --- a/fs/cifs/smbencrypt.c
> >>> +++ b/fs/cifs/smbencrypt.c
> >>> @@ -353,7 +353,7 @@ SMBNTencrypt(unsigned char *passwd, unsigned char *c8, unsigned char *p24)
> >>> int rc;
> >>> unsigned char p16[16], p21[21];
> >>>
> >>> - memset(p16, '\0', 21);
> >>> + memset(p16, '\0', 16);
> >>> memset(p21, '\0', 21);
> >>>
> >>> rc = E_md4hash(passwd, p16);
> >>
> >>
> >> perhaps ARRAY_SIZE() instead of a magic number is a better choice ?
> >>
> >
> > Agreed. Care to propose a patch? There are almost certainly other
> > places in the code that could use a similar cleanup.
> >
>
> Dan, i think he is sending to you :)
>
Nah, man. He's talking to you. :P
The 16 can't change. It's built into the name. Also you should
probably use sizeof() instead of ARRAY_SIZE(). They're the same in this
case because it's type char but sizeof is more standard.
regards,
dan carpenter
prev parent reply other threads:[~2011-03-08 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 13:26 [patch] cifs: writing past the end of the array Dan Carpenter
2011-03-06 13:26 ` Dan Carpenter
2011-03-06 14:56 ` Shirish Pargaonkar
2011-03-06 14:56 ` Shirish Pargaonkar
2011-03-06 17:11 ` walter harms
2011-03-06 17:11 ` walter harms
[not found] ` <4D73C03B.1050905-fPG8STNUNVg@public.gmane.org>
2011-03-07 16:09 ` Jeff Layton
2011-03-07 16:09 ` Jeff Layton
2011-03-07 0:41 ` Steve French
2011-03-08 8:25 ` walter harms
2011-03-08 11:05 ` Dan Carpenter [this message]
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=20110308110512.GB3416@bicker \
--to=error27@gmail.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.