netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC 1/1] net: move IFF_LIVE_ADDR_CHANGE to public flag
Date: Wed, 10 Aug 2022 12:35:22 -0700	[thread overview]
Message-ID: <fe56af9da1bcca86ab8750bcadea4da7bfc768e4.camel@gmail.com> (raw)
In-Reply-To: <9ec77cf1ffaa29aedd57c29ac77b525d0e700acf.camel@sipsolutions.net>

Hi Johannes,

On Wed, 2022-08-10 at 19:17 +0200, Johannes Berg wrote:
> On Wed, 2022-08-10 at 09:26 -0700, James Prestwood wrote:
> > 
> > Ok, so this is how I originally did it in those old patches:
> > 
> > https://lore.kernel.org/linux-wireless/20190913195908.7871-2-prestwoj@gmail.com/
> > 
> > i.e. remove_interface, change the mac, add_interface. 
> 
> Hah, I didn't even remember that ... sorry.

No worries, it was a long time ago.

> 
> > But before I revive those I want to make sure a flag can be
> > advertised
> > to userspace e.g. NL80211_EXT_FEATURE_LIVE_ADDRESS_CHANGE. (or
> > POWERED). Since this was the reason the patches got dropped in the
> > first place.
> > 
> 
> Well it seems that my objection then was basically that you have a
> feature flag in nl80211, but it affects an RT netlink operation ...
> which is a bit strange.
> 
> Thinking about that now, maybe it's not _that_ bad? Especially given
> that "live" can mean different things (as discussed here), and for
> wireless that doesn't necessarily mean IFF_UP, but rather something
> like
> "IFF_UP + not active".
> 
> Jakub, what do you think?
> 
> 
> (I'll also note you also have error handling problems in your patch,
> so
> if/when you revive, please take a look at handling errors from add
> and
> remove interface. Also indentation, and a comment on station/p2p-
> client
> might be good, and the scanning check is wrong, can check scan_sdata
> regardless of the iftype.)

Yep, I'll get that fixed up for v2.

Thanks,
James
> 
> johannes



  parent reply	other threads:[~2022-08-10 19:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 17:43 [RFC 0/1] Move IFF_LIVE_ADDR_CHANGE to public flag James Prestwood
2022-08-04 17:43 ` [RFC 1/1] net: move " James Prestwood
2022-08-04 17:59   ` Stephen Hemminger
2022-08-04 19:29     ` James Prestwood
2022-08-04 18:43   ` Jakub Kicinski
2022-08-04 19:23     ` James Prestwood
2022-08-04 19:49       ` James Prestwood
2022-08-09 19:04         ` Johannes Berg
2022-08-10 16:26           ` James Prestwood
2022-08-10 17:17             ` Johannes Berg
2022-08-10 17:36               ` Jakub Kicinski
2022-08-10 19:35               ` James Prestwood [this message]
2022-08-04 20:49 ` [RFC 0/1] Move " Andrew Lunn

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=fe56af9da1bcca86ab8750bcadea4da7bfc768e4.camel@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@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).