From: Guenter Roeck <linux@roeck-us.net>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
patches@kernelci.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>,
lkft-triage@lists.linaro.org, pavel@denx.de,
linux- stable <stable@vger.kernel.org>
Subject: Re: [PATCH 4.19 000/244] 4.19.149-rc2 review
Date: Wed, 30 Sep 2020 09:34:48 -0700 [thread overview]
Message-ID: <20200930163448.GA219887@roeck-us.net> (raw)
In-Reply-To: <CA+G9fYup1i8WnQpcg28hkq9jgQTTkuiiEfOVSnm_3wS-1sijiA@mail.gmail.com>
On Wed, Sep 30, 2020 at 09:26:48PM +0530, Naresh Kamboju wrote:
> On Tue, 29 Sep 2020 at 19:59, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 4.19.149 release.
> > There are 244 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, 01 Oct 2020 14:27:43 +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/v4.x/stable-review/patch-4.19.149-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-4.19.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Results from Linaro’s test farm.
> No regressions on arm64, arm, x86_64, and i386.
>
No perf build failure ? I just tried again, with a simple
make defconfig
make tools/perf
on my test system, and it fails to build reliably with
util/evsel.c: In function ‘perf_evsel__exit’:
util/util.h:25:28: error: passing argument 1 of ‘free’ discards ‘const’ qualifier from pointer target type
as reported. The culprit is commit d22b67e7dae9 ("perf parse-events: Fix 3
use after frees found with clang ASAN"). That is not a problem upstream because
of commit 7f7c536f23e6af ("tools lib: Adopt zalloc()/zfree() from tools/perf"),
but that is just hiding a problem with commit d22b67e7dae9 (which assigns a
pointer allocated with strdup() to a const * and then frees that const *).
Anyway, how comes that only I seem to see that problem ?
Guenter
prev parent reply other threads:[~2020-09-30 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 14:29 [PATCH 4.19 000/244] 4.19.149-rc2 review Greg Kroah-Hartman
2020-09-29 21:08 ` Guenter Roeck
2020-09-30 14:33 ` Shuah Khan
2020-09-30 15:56 ` Naresh Kamboju
2020-09-30 16:34 ` Guenter Roeck [this message]
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=20200930163448.GA219887@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@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