From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5F1B410E8; Thu, 1 Dec 2022 08:26:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 921A6C433D6; Thu, 1 Dec 2022 08:26:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1669883202; bh=bYN7sFnrzXsqdokyyNjsM57Xzrjedk4SiEcICca4yv8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jBziYPIcz32Zipj7BRwvOAXfBQOI7SAumemnTscF+KrvwpcQ6o6LPYwqi465aB2cN zwgN9DbsD4LMtEgamCL8UVshzL4U0OJeXGgJ5ieVLBX74ESoA+n1jJjJUL6WEDodKw g7R9/qpkKEb7oSxwnYCIWEc0NAyKKq+GpVd5Fd7M= Date: Thu, 1 Dec 2022 08:56:58 +0100 From: Greg Kroah-Hartman To: Nathan Chancellor Cc: Naresh Kamboju , Peter Zijlstra , Daniel Borkmann , stable@vger.kernel.org, patches@lists.linux.dev, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de, bpf , llvm@lists.linux.dev Subject: Re: [PATCH 6.0 000/289] 6.0.11-rc1 review Message-ID: References: <20221130180544.105550592@linuxfoundation.org> Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Nov 30, 2022 at 11:57:24PM -0700, Nathan Chancellor wrote: > On Thu, Dec 01, 2022 at 11:44:53AM +0530, Naresh Kamboju wrote: > > On Thu, 1 Dec 2022 at 00:13, Greg Kroah-Hartman > > wrote: > > > > > > This is the start of the stable review cycle for the 6.0.11 release. > > > There are 289 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Fri, 02 Dec 2022 18:05:05 +0000. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.0.11-rc1.gz > > > or in the git tree and branch at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.0.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > Results from Linaro's test farm. > > Regressions found on x86_64: > > > > - build-clang-15-allmodconfig-x86_64 > > - build-clang-nightly-allmodconfig-x86_64 > > > > Reported-by: Linux Kernel Functional Testing > > > > bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace) > > [ Upstream commit c86df29d11dfba27c0a1f5039cd6fe387fbf4239 ] > > > > Causing the following build warnings / errors with clang-15 allmodconfig > > on x86_64, > > > > Build error: > > make --silent --keep-going --jobs=8 > > O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=1 > > ARCH=x86_64 SRCARCH=x86 CROSS_COMPILE=x86_64-linux-gnu- > > 'HOSTCC=sccache clang' 'CC=sccache clang' > > kernel/bpf/dispatcher.c:126:33: error: pointer type mismatch ('void *' > > and 'unsigned int (*)(const void *, const struct bpf_insn *, > > bpf_func_t)' (aka 'unsigned int (*)(const void *, const struct > > bpf_insn *, unsigned int (*)(const void *, const struct bpf_insn > > *))')) [-Werror,-Wpointer-type-mismatch] > > __BPF_DISPATCHER_UPDATE(d, new ?: &bpf_dispatcher_nop_func); > > ~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~~~ > > include/linux/bpf.h:938:54: note: expanded from macro '__BPF_DISPATCHER_UPDATE' > > __static_call_update((_d)->sc_key, (_d)->sc_tramp, (_new)) > > ^~~~ > > 1 error generated. > > Thanks for the report! This is fixed with upstream commit a679120edfcf > ("bpf: Add explicit cast to 'void *' for __BPF_DISPATCHER_UPDATE()"), > which was marked as a fix for c86df29d11df. Now queued up. I forgot to run my "do we need fixes for the fixes" script on the queues, sorry about that. greg k-h