netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs-iOnpLzIbIdM@public.gmane.org>
To: Linux Netdev List <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: can: expected receive behavior broken
Date: Wed, 28 Jul 2010 09:56:38 +0200	[thread overview]
Message-ID: <201007280956.38957.matthias.fuchs@esd.eu> (raw)

Hi,

I just noticed that the receive behavior of CAN sockets is broken
in current net-next-2.6.
I wrote some simple code that receives messages and echos them back to
the bus. When I now trigger one single message on the bus, I get
this message received and echoed back in an endless loop.

I do not touch the sockopts CAN_RAW_LOOPBACK or CAN_RAW_RECV_OWN_MSGS in my code.
Only (!) setting CAN_RAW_LOOPBACK to 0 helps at the moment. But this behavior
actually has nothing to do with LOOPBACK but more with RECV_OWN_MSGS.

Matthias

             reply	other threads:[~2010-07-28  7:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  7:56 Matthias Fuchs [this message]
     [not found] ` <201007280956.38957.matthias.fuchs-iOnpLzIbIdM@public.gmane.org>
2010-07-28  8:17   ` can: expected receive behavior broken Wolfgang Grandegger
     [not found]     ` <4C4FE7AC.4010806-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-07-28  8:23       ` Matthias Fuchs
     [not found]         ` <201007281023.25039.matthias.fuchs-iOnpLzIbIdM@public.gmane.org>
2010-07-29  9:36           ` Oliver Hartkopp
     [not found]             ` <4C514BAE.4070201-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2010-07-29 11:16               ` Oliver Hartkopp

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=201007280956.38957.matthias.fuchs@esd.eu \
    --to=matthias.fuchs-ionplzibidm@public.gmane.org \
    --cc=Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).