Re: CAN: TX frames marked as RX after the sending socket is closed | netdev | Ratatoskr

CAN: TX frames marked as RX after the sending socket is closed · Torin Cooper-Bennun <hidden> · 2021-05-10
Re: CAN: TX frames marked as RX after the sending socket is closed · Marc Kleine-Budde <mkl@pengutronix.de> · 2021-05-10
Re: CAN: TX frames marked as RX after the sending socket is closed · Torin Cooper-Bennun <hidden> · 2021-05-11
Re: CAN: TX frames marked as RX after the sending socket is closed · Marc Kleine-Budde <mkl@pengutronix.de> · 2021-05-10
Re: CAN: TX frames marked as RX after the sending socket is closed · Torin Cooper-Bennun <hidden> · 2021-05-11
Re: CAN: TX frames marked as RX after the sending socket is closed · Marc Kleine-Budde <mkl@pengutronix.de> · 2021-05-11

Re: CAN: TX frames marked as RX after the sending socket is closed

From: Torin Cooper-Bennun <hidden>
Date: 2021-05-11 09:20:21
Also in: linux-can

On Mon, May 10, 2021 at 05:35:40PM +0200, Marc Kleine-Budde wrote:

Can you provide the program to reproduce the issue?

See attached below this email (tx only, rx done with candump).

Have you increased the CAN interface's txqueuelen?

Yup, qlen is 1000.

--
Regards,

Torin Cooper-Bennun
Software Engineer | maxiluxsystems.com

Attachments

tx_rx_bug.c [text/x-csrc] 1042 bytes · preview