Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	Oliver Hartkopp <oliver.hartkopp@volkswagen.de>,
	Urs Thuermann <urs.thuermann@volkswagen.de>,
	socketcan-core@lists.berlios.de,
	Network Development <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.34-rc3 + CAN build problem
Date: Sat, 10 Apr 2010 11:47:31 +0200	[thread overview]
Message-ID: <1270892851.2093.32.camel@edumazet-laptop> (raw)
In-Reply-To: <4BC03340.5020500@freemail.hu>

Le samedi 10 avril 2010 à 10:13 +0200, Németh Márton a écrit :
> Hi,
> 
> I have some problem building Liunux kernel 2.6.34-rc3 with the attached .config:
> 
> $ make clean bzImage modules
> [...]
>   CC      net/socket.o
>   LD      net/802/built-in.o
>   LD      net/can/built-in.o
>   CC [M]  net/can/bcm.o
>   CC [M]  net/can/raw.o
> In file included from /mnt/store/nmarci/src/linux-2.6.34-rc3/arch/x86/include/asm/uaccess.h:571,
>                  from include/net/checksum.h:25,
>                  from include/linux/skbuff.h:28,
>                  from include/linux/if_ether.h:124,
>                  from include/linux/netdevice.h:29,
>                  from net/can/raw.c:48:
> In function ‘copy_from_user’,
>     inlined from ‘raw_setsockopt’ at net/can/raw.c:447:
> /mnt/store/nmarci/src/linux-2.6.34-rc3/arch/x86/include/asm/uaccess_32.h:212: error: call to ‘copy_from_user_overflow’ declared with attribute error:
> copy_from_user() buffer size is not provably correct
> make[2]: *** [net/can/raw.o] Error 1
> make[1]: *** [net/can] Error 2
> make: *** [net] Error 2
> 
> 

Could you give us your compiler version ?

Code is fine, but compiler a bit dumb :(

[PATCH] can: avoids a false warning

At this point optlen == sizeof(sfilter) but some compilers are dumb.

Reported-by: Németh Márton <nm127@freemail.h
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
diff --git a/net/can/raw.c b/net/can/raw.c
index 3a7dffb..da99cf1 100644
--- a/net/can/raw.c
+++ b/net/can/raw.c
@@ -445,7 +445,7 @@ static int raw_setsockopt(struct socket *sock, int level, int optname,
 				return -EFAULT;
 			}
 		} else if (count == 1) {
-			if (copy_from_user(&sfilter, optval, optlen))
+			if (copy_from_user(&sfilter, optval, sizeof(sfilter)))
 				return -EFAULT;
 		}
 



  reply	other threads:[~2010-04-10  9:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10  8:13 Linux 2.6.34-rc3 + CAN build problem Németh Márton
2010-04-10  9:47 ` Eric Dumazet [this message]
2010-04-10 10:36   ` Németh Márton
     [not found]     ` <4BC054AE.7040303-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2010-04-10 12:36       ` Oliver Hartkopp
2010-04-10 22:50         ` David Miller
2010-04-11  5:14           ` Németh Márton
2010-04-11  5:16             ` David Miller
     [not found]           ` <20100410.155009.66184583.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-04-11 18:53             ` Oliver Hartkopp
2010-04-11 20:19               ` David Miller
2010-04-10 22:48   ` David Miller
2010-04-13 10:09   ` 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=1270892851.2093.32.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nm127@freemail.hu \
    --cc=oliver.hartkopp@volkswagen.de \
    --cc=socketcan-core@lists.berlios.de \
    --cc=socketcan@hartkopp.net \
    --cc=urs.thuermann@volkswagen.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