On 20.04.2021 21:12:00, Erik Flodin wrote: > 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. > > Signed-off-by: Erik Flodin <erik@xxxxxxxxx> Applied to linux-can-next/testing Thanks, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Embedded Linux | https://www.pengutronix.de | Vertretung West/Dortmund | Phone: +49-231-2826-924 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Attachment:
signature.asc
Description: PGP signature
