From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next-2.6] can-raw: add msg_flags to distinguish local traffic Date: Thu, 21 Oct 2010 04:32:33 -0700 (PDT) Message-ID: <20101021.043233.123993885.davem@davemloft.net> References: <4CBDF234.9000509@hartkopp.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org Return-path: In-Reply-To: <4CBDF234.9000509-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: socketcan-core-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org Errors-To: socketcan-core-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org List-Id: netdev.vger.kernel.org From: Oliver Hartkopp Date: Tue, 19 Oct 2010 21:32:04 +0200 > CAN has no addressing scheme. It is currently impossible for userspace > to tell is a received CAN frame comes from another process on the local > host, or from a remote CAN device. > > This patch add support for userspace applications to distinguish between > 'own', 'local' and 'remote' CAN traffic. The distinction is made by returning > flags in msg->msg_flags in the call to recvmsg(). > > The added documentation explains the introduced flags. > > Signed-off-by: Kurt Van Dijck > Signed-off-by: Oliver Hartkopp Applied.