Requires a way to reset socket state about can-isotp HOT 4 CLOSED

I am closing this as I am still unsure if this problem is really related to the module. I think I had a race conditions where 2 sockets were temporarily opened at the same time in different threads. I remember having similar issues in the past; I will reopen if I ever get concrete evidences that this issue is present.

from can-isotp.

Basically, I try to create a new socket using the same txid and rxid

This does not work by design!
Every endpoint needs a unique txid/rxid pair. If you open two sockets with the same txid/rxid pair (on the same host/interface) you get two identical state machines acting for the same point-to-point connection.

E.g. you send two FC frames to the sender (who will pick the first one an go for it).

from can-isotp.

I understand that this can't work. The goal here is to delete the previous socket before opening the new one. Seems that in some case, I can't do that. But as I said, I can't tell exactly how I get in this situation, so I believe this should be closed.

rmmod return "module is busy", which let me believe something is hanging in a undefined state.

Will provide details once I do have them

from can-isotp.

"module is busy" would only occur when there's still an open socket handled by that module.
Closing this issue for now. Tnx!

from can-isotp.