Message-ID: <74534ab8-a397-ac4f-dd02-9b3618d7c4cd@infradead.org>
Date:   Fri, 28 Jun 2019 13:52:47 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Daniel Mack <zonque@...il.com>
Subject: Re: linux-next: Tree for Jun 28 (kernel/bpf/cgroup.c)

On 6/28/19 3:38 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20190627:
> 
> New tree: arm-soc-fixes
> 
> The net-next tree lost its build failure.  It also gained a conflict
> against the net tree.
> 
> The battery tree gained conflicts against the mfd and pci trees.  It also
> gained a build failure for which I reverted a commit.
> 
> The devicetree tree gained a conflict against the net-next tree.
> 
> The gpio tree gained a conflict against the mfd tree.
> 
> Non-merge commits (relative to Linus' tree): 9592
>  9480 files changed, 782342 insertions(+), 283272 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.
> 
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log
> files in the Next directory.  Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig. And finally, a simple boot test of the powerpc
> pseries_le_defconfig kernel in qemu (with and without kvm enabled).
> 
> Below is a summary of the state of the merge.
> 
> I am currently merging 297 trees (counting Linus' and 72 trees of bug
> fix patches pending for the current merge release).
> 
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
> 
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
> 
> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
> Gortmaker for triage and bug fixes.
> 

on i386:

ld: kernel/bpf/cgroup.o: in function `cg_sockopt_func_proto':
cgroup.c:(.text+0x2906): undefined reference to `bpf_sk_storage_delete_proto'
ld: cgroup.c:(.text+0x2939): undefined reference to `bpf_sk_storage_get_proto'
ld: kernel/bpf/cgroup.o: in function `__cgroup_bpf_run_filter_setsockopt':
cgroup.c:(.text+0x85e4): undefined reference to `lock_sock_nested'
ld: cgroup.c:(.text+0x8af2): undefined reference to `release_sock'
ld: kernel/bpf/cgroup.o: in function `__cgroup_bpf_run_filter_getsockopt':
cgroup.c:(.text+0x8fd6): undefined reference to `lock_sock_nested'
ld: cgroup.c:(.text+0x94e4): undefined reference to `release_sock'


Full randconfig file is attached.

-- 
~Randy

View attachment "config-r6021" of type "text/plain" (77582 bytes)

Powered by blists - more mailing lists