From: Dan Carpenter <error27@gmail.com>
To: walter harms <wharms@bfs.de>
Cc: Scott Feldman <scofeldm@cisco.com>,
Vasanthy Kolluri <vkolluri@cisco.com>,
Roopa Prabhu <roprabhu@cisco.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] enic: cleanup vic_provinfo_alloc()
Date: Thu, 10 Jun 2010 11:32:30 +0200 [thread overview]
Message-ID: <20100610093230.GM5483@bicker> (raw)
In-Reply-To: <4C10AEE9.4090804@bfs.de>
On Thu, Jun 10, 2010 at 11:22:49AM +0200, walter harms wrote:
> > + vp = kzalloc(VIC_PROVINFO_MAX_DATA, flags);
> > + if (!vp)
> > return NULL;
> >
> > memcpy(vp->oui, oui, sizeof(vp->oui));
> > --
>
>
> This looks like memdup() ?
>
No. VIC_PROVINFO_MAX_DATA is larger than sizeof(vp->oui).
regards,
dan carpenter
> re,
> wh
next prev parent reply other threads:[~2010-06-10 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 7:59 [patch] enic: cleanup vic_provinfo_alloc() Dan Carpenter
2010-06-10 9:22 ` walter harms
2010-06-10 9:32 ` Dan Carpenter [this message]
2010-06-12 0:05 ` Scott Feldman
2010-06-12 1:37 ` David Miller
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=20100610093230.GM5483@bicker \
--to=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roprabhu@cisco.com \
--cc=scofeldm@cisco.com \
--cc=vkolluri@cisco.com \
--cc=wharms@bfs.de \
/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;
as well as URLs for NNTP newsgroup(s).