SocketCAN stops read after RX overflow, is it normal?

From: Guillaume Picquet <guillaume@picquet.fr>
To: linux-can@vger.kernel.org
Subject: SocketCAN stops read after RX overflow, is it normal?
Date: Wed, 2 Sep 2015 12:17:44 +0200	[thread overview]
Message-ID: <55E6CCC8.7010908@picquet.fr> (raw)

Hi every one.

I’m not sure to post to the correct list, if so please correct me.

I’m doing tests on embedded hardware with integrated CAN bus interface 
(based on AT91). The driver provides Linux Socket API and I try to see 
the limits:
I have one transmitter that writes CAN frames (CAN_RAW) as fast as 
possible and a receiver that reads continuously.
After a moment the receiver gets an error frame signalling RX overflow. 
I have no problem with that, it's normal and expected.
But question is why at this point no more frame is received ?

read() do not return, I've tested also with select() which return timeout.
(The restart-ms option is set)

I expected some dropped frames and others RX buffer errors but not the 
end of reception.

The only way to recover the interface is to set it down and up again.

Thanks in advance.

Regards.