On 1/5/22 7:56 AM, Greg Kroah-Hartman wrote:
On Wed, Jan 05, 2022 at 06:32:43PM +0530, Jeffrin Jose T wrote:
On Tue, 2022-01-04 at 08:41 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.13 release.
There are 72 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 Thu, 06 Jan 2022 07:38:29 +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/v5.x/stable-review/patch-5.15.13-rc2.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable-rc.git linux-5.15.y
and the diffstat can be found below.
thanks,
greg k-h
hello,
There was a compilation error....
-----------x--------------x------------------x--
MODPOST vmlinux.symvers
MODINFO modules.builtin.modinfo
GEN modules.builtin
BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
Failed to generate BTF for vmlinux
Try to disable CONFIG_DEBUG_INFO_BTF
make: *** [Makefile:1183: vmlinux] Error 1
Is this a regression? If so, what commit caused this?
i did CONFIG_DEBUG_INFO_BTF=n in .config and then compilation was
success.
Or you can install pahole, right? That's a requirement for that build
option I think.
Looks like some distros enabled this option - either disable the
option or install pahole. Not a regression.
Keep in mind that CONFIG_DEBUG_INFO_BTF is a dependency to build
bpf tests. bpf build pulls kernel defines from BTF to generate a
header file. Not desirable to generate header that conflicts with
standard libgcc defines which is not relevant to this conversation.
thanks,
-- Shuah
