From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
"backports@vger.kernel.org" <backports@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: cfg80211: Unknown symbol get_net_ns_by_fd (err 0)
Date: Tue, 27 Jan 2015 08:39:29 +0100 [thread overview]
Message-ID: <1422344369.1890.43.camel@sipsolutions.net> (raw)
In-Reply-To: <54C6A717.5050804@broadcom.com> (sfid-20150126_214412_608526_308C1470)
On Mon, 2015-01-26 at 21:44 +0100, Arend van Spriel wrote:
> Hi Hauke,
>
> The commit below causes the error mentioned in the Subject: field. I
> would like to fix this, but could use a bit of help here how to do this
> type of things.
>
> commit 4b681c82d2f9bef121c912ffcaac89a004af3f2c
> Author: Vadim Kochan <vadim4j@gmail.com>
> Date: Mon Jan 12 16:34:05 2015 +0200
>
> nl80211: Allow set network namespace by fd
I don't think you can fix it in backports - it required exporting the
get_net_ns_by_fd() function, which cannot be gotten to otherwise and
cannot be backported since it internally uses a number of non-exported
symbols.
You'll probably just have to provide a backported version of
get_net_ns_by_fd() that always returns ERR_PTR(-EOPNOTSUPP) or so.
johannes
next prev parent reply other threads:[~2015-01-27 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 20:44 cfg80211: Unknown symbol get_net_ns_by_fd (err 0) Arend van Spriel
2015-01-26 21:04 ` Vadim Kochan
2015-01-27 7:39 ` Johannes Berg [this message]
2015-01-30 18:18 ` Arend van Spriel
2015-01-30 18:32 ` Hauke Mehrtens
2015-01-30 18:38 ` Arend van Spriel
2015-01-30 19:41 ` 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=1422344369.1890.43.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@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).