From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH] backport: handle change in netdevice destructor usage
Date: Wed, 14 Jun 2017 15:26:55 +0200 [thread overview]
Message-ID: <1497446815.9377.0.camel@sipsolutions.net> (raw)
In-Reply-To: <5d265e01-bd12-801b-b604-ef7107e9373c@broadcom.com> (sfid-20170614_152544_312266_545812F3)
On Wed, 2017-06-14 at 15:25 +0200, Arend van Spriel wrote:
> On 13-06-17 22:59, Johannes Berg wrote:
> > On Mon, 2017-06-12 at 10:06 +0100, Arend van Spriel wrote:
> > > This patch deals with changes made in struct net_device by commit
> > > cf124db566e6 ("net: Fix inconsistent teardown and release of
> > > private
> > > netdev state."). This only looks for instances that need
> > > free_netdev() call, ie. struct net_device::needs_free_netdev ==
> > > true.
> >
> > Come to think of it, isn't this missing the part where we now call
> > priv_destructor when registering fails or something?
>
> Ah. I should have studied the patch better to see what behavioral
> changes the commit imposed.
Not sure, tbh. I just think there are issues there.
> So are you still considering the patch
> despite the likely backport of commit cf124db566e6. I can do my
> homework better and resubmit if needed.
Yeah I still think this backports patch makes sense, since I'm not sure
I want to fix mac80211 that way (the bits in unregistering multiple
netdevs are awkward) and brcmfmac would still need it.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-06-14 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 9:06 [PATCH] backport: handle change in netdevice destructor usage Arend van Spriel
2017-06-12 9:11 ` Johannes Berg
2017-06-12 9:15 ` Arend van Spriel
2017-06-12 9:22 ` Johannes Berg
2017-06-13 20:59 ` Johannes Berg
2017-06-14 13:25 ` Arend van Spriel
2017-06-14 13:26 ` Johannes Berg [this message]
2017-06-14 17:28 ` Arend van Spriel
2017-06-14 20:22 ` Johannes Berg
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=1497446815.9377.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@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