All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: "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: Fri, 30 Jan 2015 19:32:58 +0100	[thread overview]
Message-ID: <54CBCE5A.9080404@hauke-m.de> (raw)
In-Reply-To: <54CBCADA.4050801@broadcom.com>



On 01/30/2015 07:18 PM, Arend van Spriel wrote:
> On 01/26/15 21:44, 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
> 
> Hi Hauke,
> 
> I looked into my issue a bit more. So my target kernel is
> 3.11.1-200.fc19.x86_64 and checking lxr found that 3.11 has this
> function, but it does not have EXPORT_SYMBOL(). That was added by the
> same commit above. Any clues how to fix this?

Hi Arend

As Johannes said it is probably not possible to backport
get_net_ns_by_fd() correctly. You can not access any symbols which are
not exported in a kernel. To backport it we have to access
netns_operations which is also not exported.

We could  copy this function it into backports and remove this check
from the original function:
if (ei->ns_ops == &netns_operations)
..


Or we just backport this version every time:

struct net *get_net_ns_by_fd(int fd)
{
	return ERR_PTR(-EINVAL);
}

Hauke

  reply	other threads:[~2015-01-30 18:33 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
2015-01-30 18:18 ` Arend van Spriel
2015-01-30 18:32   ` Hauke Mehrtens [this message]
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=54CBCE5A.9080404@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.