From: "dust.li" <dust.li@linux.alibaba.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Karsten Graul <kgraul@linux.ibm.com>,
Tony Lu <tonylu@linux.alibaba.com>,
davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v3] net/smc: fix compile warning for smc_sysctl
Date: Mon, 7 Mar 2022 10:59:21 +0800 [thread overview]
Message-ID: <20220307025921.GE35207@linux.alibaba.com> (raw)
In-Reply-To: <f0aec757-185b-8c78-8c39-dacb3520ce74@infradead.org>
On Sun, Mar 06, 2022 at 06:36:35PM -0800, Randy Dunlap wrote:
>
>
>On 3/6/22 17:54, Dust Li wrote:
>> kernel test robot reports multiple warning for smc_sysctl:
>
>when SYSCTL is not enabled
>(AFAIK)
Right. CONFIG_SMC=m|y and CONFIG_SYSCTL is not enabled.
>
>> In file included from net/smc/smc_sysctl.c:17:
>>>> net/smc/smc_sysctl.h:23:5: warning: no previous prototype \
>> for function 'smc_sysctl_init' [-Wmissing-prototypes]
>> int smc_sysctl_init(void)
>> ^
>> and
>> >> WARNING: modpost: vmlinux.o(.text+0x12ced2d): Section mismatch \
>> in reference from the function smc_sysctl_exit() to the variable
>> .init.data:smc_sysctl_ops
>> The function smc_sysctl_exit() references
>> the variable __initdata smc_sysctl_ops.
>> This is often because smc_sysctl_exit lacks a __initdata
>> annotation or the annotation of smc_sysctl_ops is wrong.
>>
>> and
>> net/smc/smc_sysctl.c: In function 'smc_sysctl_init_net':
>> net/smc/smc_sysctl.c:47:17: error: 'struct netns_smc' has no member named 'smc_hdr'
>> 47 | net->smc.smc_hdr = register_net_sysctl(net, "net/smc", table);
>>
>> Since we don't need global sysctl initialization. To make things
>> clean and simple, remove the global pernet_operations and
>> smc_sysctl_{init|exit}. Call smc_sysctl_net_{init|exit} directly
>> from smc_net_{init|exit}.
>>
>> Also initialized sysctl_autocorking_size if CONFIG_SYSCTL it not
>> set, this make sure SMC autocorking is enabled by default if
>> CONFIG_SYSCTL is not set.
>>
>> Fixes: 462791bbfa35 ("net/smc: add sysctl interface for SMC")
>> Reported-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Dust Li <dust.li@linux.alibaba.com>
>>
>> ---
>> v3: 1. add __net_{init|exit} annotation for smc_sysctl_net_{init|exit}
>> sugguested by Jakub Kicinski
>> 2. Remove static inline for smc_sysctl_net_{init|exit} if
>> CONFIG_SYSCTL not defined
>> v2: 1. Removes pernet_operations and smc_sysctl_{init|exit}
>> 2. Initialize sysctl_autocorking_size if CONFIG_SYSCTL not set
>> ---
>> net/smc/Makefile | 3 ++-
>> net/smc/af_smc.c | 15 ++++++---------
>> net/smc/smc_sysctl.c | 19 ++-----------------
>> net/smc/smc_sysctl.h | 9 +++++----
>> 4 files changed, 15 insertions(+), 31 deletions(-)
>
>Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
Thanks a lot for testing !
>
>thanks.
>
>--
>~Randy
prev parent reply other threads:[~2022-03-07 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 1:54 [PATCH net-next v3] net/smc: fix compile warning for smc_sysctl Dust Li
2022-03-07 2:36 ` Randy Dunlap
2022-03-07 2:59 ` dust.li [this message]
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=20220307025921.GE35207@linux.alibaba.com \
--to=dust.li@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tonylu@linux.alibaba.com \
/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).