summaryrefslogtreecommitdiffstats
path: root/Documentation/networking/can.rst
diff options
context:
space:
mode:
authorErik Flodin <erik@flodin.me>2021-04-20 21:12:00 +0200
committerMarc Kleine-Budde <mkl@pengutronix.de>2021-04-24 14:36:51 +0200
commit924e464f4a8a0bb9e011ed37342e7c23c1670dc2 (patch)
tree312372bbc28a8fd85e7a399aade25b2e788732e5 /Documentation/networking/can.rst
parentcan: etas_es58x: Fix a couple of spelling mistakes (diff)
downloadlinux-924e464f4a8a0bb9e011ed37342e7c23c1670dc2.tar.xz
linux-924e464f4a8a0bb9e011ed37342e7c23c1670dc2.zip
can: add a note that RECV_OWN_MSGS frames are subject to filtering
Some parts of the documentation may lead the reader to think that the socket's own frames are always received when CAN_RAW_RECV_OWN_MSGS is enabled, but all frames are subject to filtering. As explained by Marc Kleine-Budde: On TX complete of a CAN frame it's pushed into the RX path of the networking stack, along with the information of the originating socket. Then the CAN frame is delivered into AF_CAN, where it is passed on to all registered receivers depending on filters. One receiver is the sending socket in CAN_RAW. Then in CAN_RAW the it is checked if the sending socket has RECV_OWN_MSGS enabled. Link: https://lore.kernel.org/r/20210420191212.42753-1-erik@flodin.me Signed-off-by: Erik Flodin <erik@flodin.me> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'Documentation/networking/can.rst')
-rw-r--r--Documentation/networking/can.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/networking/can.rst b/Documentation/networking/can.rst
index f8dae662e454..f34cb0e4460e 100644
--- a/Documentation/networking/can.rst
+++ b/Documentation/networking/can.rst
@@ -608,6 +608,8 @@ demand:
setsockopt(s, SOL_CAN_RAW, CAN_RAW_RECV_OWN_MSGS,
&recv_own_msgs, sizeof(recv_own_msgs));
+Note that reception of a socket's own CAN frames are subject to the same
+filtering as other CAN frames (see :ref:`socketcan-rawfilter`).
.. _socketcan-rawfd: