All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/2] can: fix multiple delivery of a single CAN frame for overlapping CAN filters
Date: Thu, 19 Mar 2015 00:17:09 +0200	[thread overview]
Message-ID: <20150318221709.GB2602@Darwish.PC> (raw)
In-Reply-To: <1426659036-4628-1-git-send-email-socketcan@hartkopp.net>

Hi!

On Wed, Mar 18, 2015 at 07:10:34AM +0100, Oliver Hartkopp wrote:
> The CAN_RAW socket can set multiple CAN identifier specific filters that lead
> to multiple filters in the af_can.c filter processing. These filters are
> indenpendent from each other which leads to logical OR'ed filters when applied.
> 
> This patch makes sure that every CAN frame which is filtered for a specific
> socket is only delivered once to the user space. This is independent from the
> number of matching CAN filters of this socket.
> 
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> ---
> 
> v2: move simple check to be processed first
> 
>  net/can/raw.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/net/can/raw.c b/net/can/raw.c
> index 00c13ef..0a6abf1 100644
> --- a/net/can/raw.c
> +++ b/net/can/raw.c
> @@ -86,6 +86,8 @@ struct raw_sock {
>  	struct can_filter dfilter; /* default/single filter */
>  	struct can_filter *filter; /* pointer to filter(s) */
>  	can_err_mask_t err_mask;
> +	struct sk_buff *uniq_skb;
> +	ktime_t uniq_tstamp;
>  };
>  

My knowledge of the networking internals are really shallow,
but the `uniq_tstamp' field above feels a little bit redundant?

As seen below:

>  /*
> @@ -123,6 +125,15 @@ static void raw_rcv(struct sk_buff *oskb, void *data)
>  	if (!ro->fd_frames && oskb->len != CAN_MTU)
>  		return;
>  
> +	/* eliminate multiple filter matches for the same skb */
> +	if (ro->uniq_skb == oskb &&
> +	    ktime_equal(ro->uniq_tstamp, oskb->tstamp)){
> +		return;
> +	} else {
> +		ro->uniq_skb = oskb;
> +		ro->uniq_tstamp = oskb->tstamp;
> +	}
> +

The two newly-introduced fields are always set together, and they
are not read anywhere beyond the if check above.

If so, isn't the `uniq_skb' field, on its own, quite sufficient?

>  	/* clone the given skb to be able to enqueue it into the rcv queue */
>  	skb = skb_clone(oskb, GFP_ATOMIC);
>  	if (!skb)
> @@ -296,6 +307,8 @@ static int raw_init(struct sock *sk)
>  	ro->loopback         = 1;
>  	ro->recv_own_msgs    = 0;
>  	ro->fd_frames        = 0;
> +	ro->uniq_skb         = NULL;
> +	ro->uniq_tstamp      = ktime_set(0, 0);
>  
>  	/* set notifier */
>  	ro->notifier.notifier_call = raw_notifier;
>

Thanks,
Darwish

  parent reply	other threads:[~2015-03-18 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  6:10 [PATCH v2 1/2] can: fix multiple delivery of a single CAN frame for overlapping CAN filters Oliver Hartkopp
2015-03-18  6:10 ` [PATCH v2 2/2] can: introduce new raw socket option to join the given " Oliver Hartkopp
2015-03-18 21:47   ` Ahmed S. Darwish
2015-03-18 22:17 ` Ahmed S. Darwish [this message]
2015-03-19  8:06   ` [PATCH v2 1/2] can: fix multiple delivery of a single CAN frame for overlapping " Oliver Hartkopp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150318221709.GB2602@Darwish.PC \
    --to=darwish.07@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.