From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Erik Flodin <erik@flodin.me>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] can: add a note that RECV_OWN_MSGS frames are subject to filtering
Date: Wed, 21 Apr 2021 08:58:57 +0200 [thread overview]
Message-ID: <20210421065857.rliinkphrzrllkci@pengutronix.de> (raw)
In-Reply-To: <20210420191212.42753-1-erik@flodin.me>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
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@flodin.me>
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-04-21 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 19:12 [PATCH] can: add a note that RECV_OWN_MSGS frames are subject to filtering Erik Flodin
2021-04-21 6:58 ` Marc Kleine-Budde [this message]
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=20210421065857.rliinkphrzrllkci@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=erik@flodin.me \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).