From: Roel Kluin <12o3l@tiscali.nl>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: drivers/net/niu.c: memcpy(dev->dev_addr, dev->perm_addr, dev->addr_len)?
Date: Fri, 21 Mar 2008 00:01:11 +0100 [thread overview]
Message-ID: <47E2ECB7.5030304@tiscali.nl> (raw)
In-Reply-To: <20080320.142510.148381731.davem@davemloft.net>
David Miller wrote:
> From: Roel Kluin <12o3l@tiscali.nl>
> Date: Thu, 20 Mar 2008 22:01:02 +0100
>
>> in drivers/net/niu.c, line 6406, 6286 and 7173:
>>
>> memcpy(dev->dev_addr, dev->perm_addr, dev->addr_len);
>>
>> I noticed that "
>>
>> memcpy(dev->perm_addr, dev->dev_addr, dev->addr_len)
>>
>> occurs much more often (15x). could it be that the first two arguments
>> are swapped in niu.c?
>
> No, these calls are correct. We are probing the device's permanent
> ethernet address, we first place it into dev->dev_addr and then we
> copy it into dev->perm_addr.
>
> Please try to actually understand the pieces of strcpy and memcpy code
> you are "finding bugs" in before posting to the list as these analysis
> on false positives are going to eat up a lot of developer time.
Sorry for the noise (also for sound/sparc/dbri.c) and thanks for your
answers, It takes a lot more time for me to understand the code than it
will do for someone with more knowledge and experience with this driver,
If drivers/net/niu.c copies in opposite direction compared to 80% of the
other memcpy calls - using these same variable names - and it is not
directly transparent why, My opinion is that either the naming is bad or
there is a lack of comment.
> I notice you posting several of these kinds of things.
Only 2 with the above conditions and patches or not where I was able to
figure it out myself. I don't really understand why you are opposed to
these questions.
next prev parent reply other threads:[~2008-03-20 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 21:01 drivers/net/niu.c: memcpy(dev->dev_addr, dev->perm_addr, dev->addr_len)? Roel Kluin
2008-03-20 21:25 ` David Miller
2008-03-20 23:01 ` Roel Kluin [this message]
2008-03-21 13:07 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2008-03-20 21:01 Roel Kluin
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=47E2ECB7.5030304@tiscali.nl \
--to=12o3l@tiscali.nl \
--cc=davem@davemloft.net \
--cc=netdev@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.