netdev - at91_can: errata "Contents of Mailbox 0 can be sent"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4D250191.80600@pengutronix.de>
Date:	Thu, 06 Jan 2011 00:41:05 +0100
From:	Marc Kleine-Budde <mkl@...gutronix.de>
To:	SocketCAN Core Mailing List <socketcan-core@...ts.berlios.de>
CC:	Netdev@...r.kernel.org
Subject: at91_can: errata "Contents of Mailbox 0 can be sent"

Moin,

the at91_can core has the following problem:
"50.3.5.3 CAN: Contents of Mailbox 0 can be sent Even if Mailbox is
Disabled"

This means under high bus load it can happen that the mailbox 0 is send
to the bus. And it does happen, even with the mainline driver where
Mailbox 0 is a receive mailbox. The errata proposes not to use mailbox 0
and load it with a unused can_id that will not disturb the bus.

I'm going to implement the workaround. As the unused identifier is
probably application specific my question is: What's the best way to
configure this identifier?

- sysfs
- netlink
- ioctl
- ethtool
- peek/poke :P

What will be a good default can_id?

regards, Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

Download attachment "signature.asc" of type "application/pgp-signature" (263 bytes)