public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org
Subject: Re: [PATCH 5.4 000/367] 5.4.257-rc1 review
Date: Wed, 20 Sep 2023 10:21:18 -0700	[thread overview]
Message-ID: <166b5b43-adab-7d00-e3f6-c9a1dfd29f52@gmail.com> (raw)
In-Reply-To: <20230920112858.471730572@linuxfoundation.org>

On 9/20/23 04:26, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.257 release.
> There are 367 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, 22 Sep 2023 11:28:09 +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.4.257-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-5.4.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

perf does not build with:

libbpf.c: In function 'bpf_object__close':
libbpf.c:4205:15: error: 'struct bpf_object' has no member named 
'btf_vmlinux'
   btf__free(obj->btf_vmlinux);
                ^~

due to 34d66b750e83d49c7d3d33d59e6a1b49e0d5db15 ("libbpf: Free 
btf_vmlinux when closing bpf_object")

the btf_vmlinux member was introduced with 
a6ed02cac690b635dbb938690e795812ce1e14ca ("libbpf: Load btf_vmlinux only 
once per object.") which is only in >= 5.6.

Suggset we drop that commit.
-- 
Florian


  parent reply	other threads:[~2023-09-20 17:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 11:26 [PATCH 5.4 000/367] 5.4.257-rc1 review Greg Kroah-Hartman
2023-09-20 11:27 ` [PATCH 5.4 050/367] eventfd: prevent underflow for eventfd semaphores Greg Kroah-Hartman
2023-09-20 11:31 ` [PATCH 5.4 310/367] autofs: fix memory leak of waitqueues in autofs_catatonic_mode Greg Kroah-Hartman
2023-09-20 17:21 ` Florian Fainelli [this message]
2023-09-21 12:20   ` [PATCH 5.4 000/367] 5.4.257-rc1 review Guenter Roeck
2023-09-23  8:26     ` Greg Kroah-Hartman
2023-09-20 21:37 ` Shuah Khan
2023-09-21 12:08 ` Naresh Kamboju
2023-09-21 13:10   ` Sui Jingfeng
2023-09-21 13:16     ` Sui Jingfeng
2023-09-23  8:30       ` Greg Kroah-Hartman
2023-09-21 14:33 ` Naresh Kamboju
2023-09-21 15:55 ` Guenter Roeck
2023-09-22  9:46 ` Jon Hunter

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=166b5b43-adab-7d00-e3f6-c9a1dfd29f52@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=conor@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --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=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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