From: Eric Dumazet <eric.dumazet@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Ben Hutchings <bhutchings@solarflare.com>
Subject: Re: [PATCH net-next-2.6] net: copy_rtnl_link_stats64() simplification
Date: Mon, 23 Aug 2010 20:17:45 +0200 [thread overview]
Message-ID: <1282587465.2378.10.camel@edumazet-laptop> (raw)
In-Reply-To: <1282585624.1879.103.camel@Joe-Laptop>
Le lundi 23 août 2010 à 10:47 -0700, Joe Perches a écrit :
> On Mon, 2010-08-23 at 19:14 +0200, Eric Dumazet wrote:
> > No need to use a temporary struct rtnl_link_stats64 variable,
> > just copy the source to skb buffer.
> >
> > Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
>
> Maybe it's better to use the same argument style as copy_rtnl_link_stats
>
> net/core/rtnetlink.c | 36 ++++--------------------------------
> 1 files changed, 4 insertions(+), 32 deletions(-)
>
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index f78d821..f8781db 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -610,38 +610,10 @@ static void copy_rtnl_link_stats(struct rtnl_link_stats *a,
> a->tx_compressed = b->tx_compressed;
> }
>
> -static void copy_rtnl_link_stats64(void *v, const struct rtnl_link_stats64 *b)
> +static void copy_rtnl_link_stats64(struct rtnl_link_stats64 *a,
> + const struct rtnl_link_stats64 *b)
> {
Nope, we have no quarantee of v being aligned on a u64
If you tell compiler first argument is a pointer to rtnl_link_stats64,
it might use 64bit stores and trap.
prev parent reply other threads:[~2010-08-23 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 17:14 [PATCH net-next-2.6] net: copy_rtnl_link_stats64() simplification Eric Dumazet
2010-08-23 17:21 ` Ben Hutchings
2010-08-24 3:45 ` David Miller
2010-08-23 17:47 ` Joe Perches
2010-08-23 18:14 ` Ben Hutchings
2010-08-24 3:44 ` David Miller
2010-08-23 18:17 ` Eric Dumazet [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=1282587465.2378.10.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox