From: David Ahern <dsahern@gmail.com>
To: Matteo Croce <mcroce@redhat.com>,
netdev@vger.kernel.org, linux-next@vger.kernel.org,
akpm@linux-foundation.org, Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH linux-next v2] mpls: don't build sysctl related code when sysctl is disabled
Date: Fri, 7 Jun 2019 11:14:41 -0600 [thread overview]
Message-ID: <ea97df59-481b-3f05-476c-33e733b5c4ba@gmail.com> (raw)
In-Reply-To: <20190607003646.10411-1-mcroce@redhat.com>
On 6/6/19 6:36 PM, Matteo Croce wrote:
> Some sysctl related code and data structures is never referenced
> when CONFIG_SYSCTL is not set.
> While this is usually harmless, it produces a build failure since sysctl
> shared variables exists, due to missing sysctl_vals symbol:
>
> ld: net/mpls/af_mpls.o: in function `mpls_platform_labels':
> af_mpls.c:(.text+0x162a): undefined reference to `sysctl_vals'
> ld: net/mpls/af_mpls.o:(.rodata+0x830): undefined reference to `sysctl_vals'
> ld: net/mpls/af_mpls.o:(.rodata+0x838): undefined reference to `sysctl_vals'
> ld: net/mpls/af_mpls.o:(.rodata+0x870): undefined reference to `sysctl_vals'
>
> Fix this by moving all sysctl related code under #ifdef CONFIG_SYSCTL
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Matteo Croce <mcroce@redhat.com>
> ---
>
> v1 -> v2: fix a crash on netns destroy
>
> net/mpls/af_mpls.c | 393 ++++++++++++++++++++++++---------------------
> 1 file changed, 207 insertions(+), 186 deletions(-)
>
As I recall you need to set platform_labels for the mpls code to even
work, so building mpls_router without sysctl is pointless.
next prev parent reply other threads:[~2019-06-07 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 0:36 [PATCH linux-next v2] mpls: don't build sysctl related code when sysctl is disabled Matteo Croce
2019-06-07 17:14 ` David Ahern [this message]
2019-06-07 18:20 ` Matteo Croce
2019-06-07 18:46 ` David Ahern
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=ea97df59-481b-3f05-476c-33e733b5c4ba@gmail.com \
--to=dsahern@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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).