netdev - Re: [wireless-testsing2:master 1/4] drivers/net/netdevsim/bpf.c:130:14: sparse: incompatible types for 'case' statement

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 3 Jan 2018 17:02:37 -0800
From:   Jakub Kicinski <kubakici@...pl>
To:     kbuild test robot <fengguang.wu@...el.com>
Cc:     "David S. Miller" <davem@...emloft.net>, kbuild-all@...org,
        netdev@...r.kernel.org, Bob Copeland <me@...copeland.com>
Subject: Re: [wireless-testsing2:master 1/4]
 drivers/net/netdevsim/bpf.c:130:14: sparse: incompatible types for 'case'
 statement

On Thu, 4 Jan 2018 03:53:20 +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git master
> head:   6b3b30d0c31ddb2f4d8208c90bc2b4adef47204d
> commit: af2cae39f6ab9dc596616d6a28c7772e1dd55e91 [1/4] Merge remote-tracking branch 'wireless-drivers-next/master'
> reproduce:
>         # apt-get install sparse
>         git checkout af2cae39f6ab9dc596616d6a28c7772e1dd55e91
>         make ARCH=x86_64 allmodconfig
>         make C=1 CF=-D__CHECK_ENDIAN__

>    drivers/net/netdevsim/bpf.c: In function 'nsim_bpf_setup_tc_block_cb':
> >> drivers/net/netdevsim/bpf.c:130:7: error: 'TC_CLSBPF_REPLACE' undeclared (first use in this function); did you mean 'TC_RED_REPLACE'?  
>      case TC_CLSBPF_REPLACE:
>           ^~~~~~~~~~~~~~~~~
>           TC_RED_REPLACE

FWIW looks like the tree contains old net-next code and latest net
(linux/master) code.  Pulling from net-next will solve this.

> :::::: TO: Jakub Kicinski <jakub.kicinski@...ronome.com>
> :::::: CC: Daniel Borkmann <daniel@...earbox.net>

Interestingly Daniel and I were not CCed on the report, is this
intentional?