From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@rothwell.id.au>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Stefano Brivio <sbrivio@redhat.com>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: mmotm 2021-05-19-23-58 uploaded (net/netfilter/nft_set_pipapo_avx2.c)
Date: Thu, 20 May 2021 18:04:15 -0700 [thread overview]
Message-ID: <6eb826b6-4279-8cf8-1c27-01aab0f83843@infradead.org> (raw)
In-Reply-To: <20210521090751.51afa10f@elm.ozlabs.ibm.com>
On 5/20/21 4:07 PM, Stephen Rothwell wrote:
> Hi Randy,
>
> On Thu, 20 May 2021 15:40:54 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> on x86_64:
>> (from linux-next, not mmotm)
>
> Yeah, this is caused by a bad merge resolution by me.
>
>> ../net/netfilter/nft_set_pipapo_avx2.c: In function ‘nft_pipapo_avx2_lookup’:
>> ../net/netfilter/nft_set_pipapo_avx2.c:1135:10: error: implicit declaration of function ‘nft_pipapo_lookup’; did you mean ‘nft_pipapo_avx2_lookup’? [-Werror=implicit-function-declaration]
>> return nft_pipapo_lookup(net, set, key, ext);
>> ^~~~~~~~~~~~~~~~~
>
> I have added this to the merge resolution today:
>
> diff --git a/include/net/netfilter/nf_tables_core.h b/include/net/netfilter/nf_tables_core.h
> index 789e9eadd76d..8652b2514e57 100644
> --- a/include/net/netfilter/nf_tables_core.h
> +++ b/include/net/netfilter/nf_tables_core.h
> @@ -89,6 +89,8 @@ extern const struct nft_set_type nft_set_bitmap_type;
> extern const struct nft_set_type nft_set_pipapo_type;
> extern const struct nft_set_type nft_set_pipapo_avx2_type;
>
> +bool nft_pipapo_lookup(const struct net *net, const struct nft_set *set,
> + const u32 *key, const struct nft_set_ext **ext);
> #ifdef CONFIG_RETPOLINE
> bool nft_rhash_lookup(const struct net *net, const struct nft_set *set,
> const u32 *key, const struct nft_set_ext **ext);
> @@ -101,8 +103,6 @@ bool nft_hash_lookup_fast(const struct net *net,
> const u32 *key, const struct nft_set_ext **ext);
> bool nft_hash_lookup(const struct net *net, const struct nft_set *set,
> const u32 *key, const struct nft_set_ext **ext);
> -bool nft_pipapo_lookup(const struct net *net, const struct nft_set *set,
> - const u32 *key, const struct nft_set_ext **ext);
> bool nft_set_do_lookup(const struct net *net, const struct nft_set *set,
> const u32 *key, const struct nft_set_ext **ext);
> #else
> diff --git a/net/netfilter/nft_set_pipapo.c b/net/netfilter/nft_set_pipapo.c
> index 9addc0b447f7..dce866d93fee 100644
> --- a/net/netfilter/nft_set_pipapo.c
> +++ b/net/netfilter/nft_set_pipapo.c
> @@ -408,7 +408,6 @@ int pipapo_refill(unsigned long *map, int len, int rules, unsigned long *dst,
> *
> * Return: true on match, false otherwise.
> */
> -INDIRECT_CALLABLE_SCOPE
> bool nft_pipapo_lookup(const struct net *net, const struct nft_set *set,
> const u32 *key, const struct nft_set_ext **ext)
> {
>
> It should apply on top of next-20210520 if you want to test it (I
> haven't tested it yet, but will later today).
Yes, that builds. Thanks.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-05-21 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 6:59 mmotm 2021-05-19-23-58 uploaded akpm
2021-05-20 22:21 ` mmotm 2021-05-19-23-58 uploaded (mm/migrate.c) Randy Dunlap
2021-05-21 2:22 ` [External] " Muchun Song
2021-05-20 22:40 ` mmotm 2021-05-19-23-58 uploaded (net/netfilter/nft_set_pipapo_avx2.c) Randy Dunlap
2021-05-20 23:07 ` Stephen Rothwell
2021-05-21 1:04 ` Randy Dunlap [this message]
2021-05-20 22:53 ` mmotm 2021-05-19-23-58 uploaded (drivers/iio/accel/fxls8962af-core.o) Randy Dunlap
2021-05-21 9:00 ` Sean Nyekjaer
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=6eb826b6-4279-8cf8-1c27-01aab0f83843@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=coreteam@netfilter.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=sfr@rothwell.id.au \
/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).