[PATCH 0/2] can: mcp251xfd: fix TEF vs TX race condition introduced in UINC improvements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: kernel@xxxxxxxxxxxxxx, linux-can@xxxxxxxxxxxxxxx
Subject: [PATCH 0/2] can: mcp251xfd: fix TEF vs TX race condition introduced in UINC improvements
From: Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx>
Date: Tue, 5 Jan 2021 22:41:36 +0100
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx>, Thomas Kopp <thomas.kopp@xxxxxxxxxxxxx>

Hello,

during the TEF readout UINC improvements, I introduced a TEF vs TX race
condition to the driver. The first patch fixes the problem. The second patch
fixes the same issue in the RX-path, which causes no problem, but now the code
path look the same.

regards,
Marc

Follow-Ups:
- [PATCH 2/2] can: mcp251xfd: mcp251xfd_handle_rxif_ring(): first increment RX tail pointer in HW, then in driver
  - From: Marc Kleine-Budde
- [PATCH 1/2] can: mcp251xfd: mcp251xfd_handle_tefif(): fix TEF vs. TX race condition
  - From: Marc Kleine-Budde

Prev by Date: [PATCH 1/2] can: mcp251xfd: mcp251xfd_handle_tefif(): fix TEF vs. TX race condition
Next by Date: [PATCH 2/2] can: mcp251xfd: mcp251xfd_handle_rxif_ring(): first increment RX tail pointer in HW, then in driver
Previous by thread: [PATCH] MAINTAINERS: Update MCAN MMIO device driver maintainer
Next by thread: [PATCH 1/2] can: mcp251xfd: mcp251xfd_handle_tefif(): fix TEF vs. TX race condition
Index(es):
- Date
- Thread

[Index of Archives] [Automotive Discussions] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [CAN Bus]

Powered by Linux