linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	Jouni Malinen <jouni@qca.qualcomm.com>
Subject: Re: [RFC] wireless, ipv4, ipv6: drop GTK-protected unicast IP packets
Date: Thu, 21 Nov 2013 15:31:04 +0100	[thread overview]
Message-ID: <1385044264.14273.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1385043867.10637.39.camel@edumazet-glaptop2.roam.corp.google.com> (sfid-20131121_152431_763108_248DD4C9)

On Thu, 2013-11-21 at 06:24 -0800, Eric Dumazet wrote:
> On Thu, 2013-11-21 at 14:08 +0100, Johannes Berg wrote:
> > On Thu, 2013-11-21 at 14:05 +0100, Johannes Berg wrote:
> > 
> > > @@ -498,7 +500,8 @@ struct sk_buff {
> > >  	 * headers if needed
> > >  	 */
> > >  	__u8			encapsulation:1;
> > > -	/* 7/9 bit hole (depending on ndisc_nodetype presence) */
> > > +	__u8			drop_unicast:1;
> > 
> > The obvious question is here, and for IPv4/IPv6 - should the wireless
> > stack be responsible for doing this instead?
> 
> I don't really like the idea of reserving a bit for this in sk_buff,
> and propagate it in every cloning ...
> 
> Someone should replace __copy_skb_header() by a single memset(),
> because copying all these bits one by one is not really clever.
> 
> And then, adding a test in fast path (ip_rcv_finish()) is really not
> nice.

Yeah, that was a concern too. I'll do it entirely in the wireless stack
instead I guess. At least it'll be hidden away inside the if that
already does the group key check etc.

Thanks.

johannes


  reply	other threads:[~2013-11-21 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 13:05 [RFC] wireless, ipv4, ipv6: drop GTK-protected unicast IP packets Johannes Berg
2013-11-21 13:08 ` Johannes Berg
2013-11-21 14:24   ` Eric Dumazet
2013-11-21 14:31     ` Johannes Berg [this message]
2013-11-21 19:14       ` David Miller

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=1385044264.14273.6.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).