From: Shuah Khan <skhan@linuxfoundation.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
Cc: 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,
stable@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 5.15 00/72] 5.15.13-rc2 review
Date: Wed, 5 Jan 2022 08:17:43 -0700 [thread overview]
Message-ID: <b7a7543d-2e18-93fb-7a7d-791a8030d347@linuxfoundation.org> (raw)
In-Reply-To: <YdWxh/OR0dQDeS9E@kroah.com>
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
next prev parent reply other threads:[~2022-01-05 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 7:41 Greg Kroah-Hartman
2022-01-04 17:08 ` Sudip Mukherjee
2022-01-04 18:48 ` Florian Fainelli
2022-01-05 1:29 ` Guenter Roeck
2022-01-05 2:16 ` Shuah Khan
2022-01-05 3:52 ` Naresh Kamboju
2022-01-05 3:58 ` Zan Aziz
2022-01-05 13:02 ` Jeffrin Jose T
2022-01-05 14:56 ` Greg Kroah-Hartman
2022-01-05 15:17 ` Shuah Khan [this message]
2022-01-05 18:15 ` Jeffrin Jose T
2022-01-05 14:55 ` Fox Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7a7543d-2e18-93fb-7a7d-791a8030d347@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffrin@rajagiritech.edu.in \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome