[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190709151333.GD14859@sirena.co.uk>
Date: Tue, 9 Jul 2019 16:13:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Lecopzer Chen <lecopzer.chen@...iatek.com>,
Mark-PK Tsai <Mark-PK.Tsai@...iatek.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Pavel Tatashin <pasha.tatashin@...cle.com>,
Oscar Salvador <osalvador@...e.de>,
Michal Hocko <mhocko@...e.com>,
Mike Rapoport <rppt@...ux.ibm.com>
Cc: kernel-build-reports@...ts.linaro.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: next/master build: 230 builds: 3 failed, 227 passed, 391
warnings (next-20190709)
On Tue, Jul 09, 2019 at 07:37:50AM -0700, kernelci.org bot wrote:
Today's -next fails to build tinyconfig on arm64 and x86_64:
> arm64:
> tinyconfig: (clang-8) FAIL
> tinyconfig: (gcc-8) FAIL
>
> x86_64:
> tinyconfig: (gcc-8) FAIL
due to:
> tinyconfig (arm64, gcc-8) — FAIL, 0 errors, 0 warnings, 0 section mismatches
>
> Section mismatches:
> WARNING: vmlinux.o(.meminit.text+0x430): Section mismatch in reference from the function sparse_buffer_alloc() to the function .init.text:sparse_buffer_free()
> FATAL: modpost: Section mismatches detected.
(same error for all of them, the warning appears non-fatally in
other configs). This is caused by f13d13caa6ef2 (mm/sparse.c:
fix memory leak of sparsemap_buf in aliged memory) which adds a
reference from the __meminit annotated sparse_buffer_alloc() to
the newly added __init annotated sparse_buffer_free().
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists