commit d253eee20195b25e298bf162a6e72f14bf4803e5
author Oliver Hartkopp <oliver@hartkopp.net> Wed Dec 03 15:52:35 2008 -0800
committer David S. Miller <davem@davemloft.net> Wed Dec 03 15:52:35 2008 -0800
tree 4fd5fef75d52ecae3f41dbd9ae62436e917e1699
parent bd7df219202f44e71e2e975a0fb5f76f946c1aef

can: Fix CAN_(EFF|RTR)_FLAG handling in can_filter

Due to a wrong safety check in af_can.c it was not possible to filter
for SFF frames with a specific CAN identifier without getting the
same selected CAN identifier from a received EFF frame also.

This fix has a minimum (but user visible) impact on the CAN filter
API and therefore the CAN version is set to a new date.

Indeed the 'old' API is still working as-is. But when now setting
CAN_(EFF|RTR)_FLAG in can_filter.can_mask you might get less traffic
than before - but still the stuff that you expected to get for your
defined filter ...

Thanks to Kurt Van Dijck for pointing at this issue and for the review.

Signed-off-by: Oliver Hartkopp <oliver@hartkopp.net>
Acked-by: Kurt Van Dijck <kurt.van.dijck@eia.be>
Signed-off-by: David S. Miller <davem@davemloft.net>