netdev - Re: [Internet]linux-next: build warning after merge of the net-next tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 25 Aug 2022 10:42:08 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     "imagedong董梦龙)" 
        <imagedong@...cent.com>, linux-doc@...r.kernel.org
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "Linux Next Mailing List" <linux-next@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        Networking <netdev@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>
Subject: Re: [Internet]linux-next: build warning after merge of the net-next
 tree

On Thu, 25 Aug 2022 07:55:36 +0000 imagedong(董梦龙) wrote:
> > After merging the net-next tree, today's linux-next build (htmldocs)
> > produced this warning:
> > 
> > Documentation/networking/kapi:26: net/core/skbuff.c:780: WARNING: Error in declarator or parameters
> > Invalid C declaration: Expecting "(" in parameters. [error at 19]
> >   void __fix_address kfree_skb_reason (struct sk_buff *skb, enum skb_drop_reason reason)
> >   -------------------^
> > 
> > Introduced by commit
> > 
> >   c205cc7534a9 ("net: skb: prevent the split of kfree_skb_reason() by gcc")
> >   
> 
> Yeah, I commited this patch. May I ask what command did you use to
> produce this warning? I tried the following command, but not success:
> 
>   make V=2 SPHINXDIRS="networking" htmldocs
> 
> Hmm.......what does this warning means? Does it don't like this
> function attribute?

It popped up for me on a clean build of

	make htmldocs

There's a lot of other warnings but you should see this one, too.

I think you need to add the new keyword to one of the tables in
Documentation/conf.py