[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <49340DAE.5060603@hartkopp.net>
Date: Mon, 01 Dec 2008 17:15:42 +0100
From: Oliver Hartkopp <oliver@...tkopp.net>
To: David Miller <davem@...emloft.net>, Greg KH <greg@...ah.com>
CC: Kurt Van Dijck <kurt.van.dijck@....be>,
Linux Netdev List <netdev@...r.kernel.org>, stable@...nel.org
Subject: [PATCH] can: Fix CAN_(EFF|RTR)_FLAG handling in can_filter
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@...tkopp.net>
Acked-by: Kurt Van Dijck <kurt.van.dijck@....be>
---
Hello Dave & Greg,
this patch fixes an issue when running with mixed CAN frame formats.
It should go into 2.6.28 before the bug fix window closes.
Additionally the patch applies excellent down to 2.6.26. Greg please
consider this patch for stable .26 and .27 also.
Thanks & best regards,
Oliver
View attachment "can_filter.patch" of type "text/x-patch" (4465 bytes)
Powered by blists - more mailing lists