linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: [PATCH] ath10k: add dynamic vlan support
Date: Fri, 18 May 2018 11:54:30 +0200	[thread overview]
Message-ID: <1526637270.3805.15.camel@sipsolutions.net> (raw)
In-Reply-To: <f8d6d13943ccac22f363d7d4f53d645c@codeaurora.org>

On Fri, 2018-05-04 at 12:20 +0530, Manikanta Pubbisetty wrote:
> Johannes,
> 
> It seems like commit db3bdcb9c3ff ("mac80211: allow AP_VLAN operation on 
> crypto controlled devices") has broken 4-addr operation on crypto 
> controlled devices as reported by sebastian.
> The commit was mainly focused in addressing the problem in supporting 
> VLANs on crypto controlled devices but since 4-addr mode is also 
> dependent on AP_VLAN interface, this commit breaks the 4-addr AP mode.

Ok.

Do you know why it actually broke it? I mean, we should've turned off
the strict requirement for sw crypto control only for the GTK, and that
shouldn't matter so much?

> I have couple of ideas on how to address the problem,
> 
> 1) Add a new hw_flag and based on the hardware flag, allow/disallow the 
> creation of AP_VLAN interface.
> 
> + * @IEEE80211_HW_SUPPORTS_SW_ENCRYPT: Device is capable of transmitting
> + *     frames encrypted in software, only valid when SW_CRYPTO_CONTROL
> + *     is enabled. Based on this flag, mac80211 can allow/disallow VLAN
> + *     operations in the BSS.

Based on the name and initial description, this sounds equivalent to
just turning off SW_CRYPTO_CONTROL. I think that's not the intent, but
would need some renaming.

> 2) Allow mac80211 to call set_key for GTKs on AP_VLAN interfaces for 
> crypto controlled devices, let the driver decide whether to return '1' 
> or some error code based on their support for transmitting sw encrypted 
> frames. I am little skeptical with this approach as drivers are totally 
> unaware of AP_VLAN interfaces.

No, that won't work.

I'm unsure how 4-addr VLAN can work with ath10k either way?

Maybe it just doesn't normally need a GTK, so nothing broke before, but
your other patch changed things to remove VLAN and then of course it's
no longer available?

But then I don't understand the complaint that 

So maybe the solution should be to add a separate flag for whether or
not 4-addr VLAN is supported?

johannes

  parent reply	other threads:[~2018-05-18  9:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 13:57 [PATCH] ath10k: add dynamic vlan support Manikanta Pubbisetty
2018-04-23 19:18 ` Sebastian Gottschall
2018-05-18  9:53   ` Johannes Berg
2018-05-18 10:40     ` Sebastian Gottschall
2018-04-24  8:09 ` Kalle Valo
2018-04-24  9:09   ` Sebastian Gottschall
2018-04-24  9:18     ` Manikanta Pubbisetty
2018-04-24  9:52     ` Kalle Valo
2018-04-24  9:55       ` Sebastian Gottschall
2018-05-04  6:50     ` Manikanta Pubbisetty
2018-05-05  9:50       ` Sebastian Gottschall
2018-05-18  9:54       ` Johannes Berg [this message]
2018-05-18 10:52         ` Sebastian Gottschall
2018-05-21  6:42         ` Manikanta Pubbisetty
2018-05-23  9:50           ` Johannes Berg
2018-05-23 10:39             ` Manikanta Pubbisetty
2018-05-23 10:39               ` Johannes Berg
2018-05-23 10:50                 ` Manikanta Pubbisetty
2018-05-24  4:41                 ` Sebastian Gottschall
2018-06-18 20:49                   ` Johannes Berg
2018-08-14 12:53             ` Manikanta Pubbisetty
2018-08-16  8:27               ` Johannes Berg
2018-08-24  5:50                 ` Manikanta Pubbisetty
2018-09-03 10:39                   ` Johannes Berg
2018-09-05  6:03                     ` Manikanta Pubbisetty
     [not found]                 ` <15ca06c2-0d43-99c1-8f31-19e73629ab70@codeaurora.org>
2018-08-24  8:14                   ` Kalle Valo

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=1526637270.3805.15.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpubbise@codeaurora.org \
    --cc=s.gottschall@dd-wrt.com \
    /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).