All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
To: Kurt Van Dijck <kurt.van.dijck-/BeEPy95v10@public.gmane.org>
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] can: test size of struct sockaddr
Date: Sat, 15 Jan 2011 18:08:54 +0100	[thread overview]
Message-ID: <4D31D4A6.4040701@hartkopp.net> (raw)
In-Reply-To: <20110114172321.GB331-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>

On 14.01.2011 18:23, Kurt Van Dijck wrote:
> I think this patch makes the CAN socket code comform to the
> manpages of sendmsg & recvmsg.

Hello Kurt,

if you check similar code sniplets in the kernel you would see, that in
recvmsg()-cases the given namelen is not used from userspace.

If msg->msg_name is not NULL the msg_namelen is just set by the kernel. E.g.
see af_packet.c, af_econet.c, etc.

So the code in candump.c setting the msg_namelen before recvmsg() is obviously
obsolete ...

Btw. your two patches below for bcm_sendmsg() and raw_sendmesg() look good.

If you would like to resubmit these two patches, you may add my Acked-by

Thanks,
Oliver



> diff --git a/net/can/bcm.c b/net/can/bcm.c
> index 6faa825..dc0d5d6 100644
> --- a/net/can/bcm.c
> +++ b/net/can/bcm.c
> @@ -1256,6 +1256,9 @@ static int bcm_sendmsg(struct kiocb *iocb, struct socket *sock,
>  		struct sockaddr_can *addr =
>  			(struct sockaddr_can *)msg->msg_name;
>  
> +		if (msg->msg_namelen < sizeof(*addr))
> +			return -EINVAL;
> +
>  		if (addr->can_family != AF_CAN)
>  			return -EINVAL;
>  


> diff --git a/net/can/raw.c b/net/can/raw.c
> index e88f610..e68a6d3 100644
> --- a/net/can/raw.c
> +++ b/net/can/raw.c
> @@ -649,6 +649,9 @@ static int raw_sendmsg(struct kiocb *iocb, struct socket *sock,
>  		struct sockaddr_can *addr =
>  			(struct sockaddr_can *)msg->msg_name;
>  
> +		if (msg->msg_namelen < sizeof(*addr))
> +			return -EINVAL;
> +
>  		if (addr->can_family != AF_CAN)
>  			return -EINVAL;
>  

  parent reply	other threads:[~2011-01-15 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 17:23 [PATCH] can: test size of struct sockaddr Kurt Van Dijck
     [not found] ` <20110114172321.GB331-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-01-15 17:08   ` Oliver Hartkopp [this message]
     [not found]     ` <4D31D4A6.4040701-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-01-15 19:35       ` Kurt Van Dijck

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=4D31D4A6.4040701@hartkopp.net \
    --to=socketcan-fj+pqtutwrtk1umjsbkqmq@public.gmane.org \
    --cc=kurt.van.dijck-/BeEPy95v10@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.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.