linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "David Gow" <davidgow@google.com>,
	"Jinjie Ruan" <ruanjinjie@huawei.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	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,
	conor@kernel.org, kunit-dev@googlegroups.com,
	"Daniel Díaz" <daniel.diaz@linaro.org>
Subject: Re: [PATCH 6.5 000/550] 6.5.12-rc1 review
Date: Thu, 16 Nov 2023 09:02:34 -0500	[thread overview]
Message-ID: <ZVYg-hRRg6Npn2Gt@sashalap> (raw)
In-Reply-To: <CA+G9fYuncLhP1=BWQv561Jh5cZH9EDmnqnH3Znugi+eua5S0MA@mail.gmail.com>

On Thu, Nov 16, 2023 at 06:45:52PM +0530, Naresh Kamboju wrote:
>+ kunit team
>
>On Thu, 16 Nov 2023 at 05:30, Daniel Díaz <daniel.diaz@linaro.org> wrote:
>>
>> Hello!
>>
>> On Wed, 15 Nov 2023 at 15:38, Daniel Díaz <daniel.diaz@linaro.org> wrote:
>> > On Wed, 15 Nov 2023 at 13:20, Greg Kroah-Hartman
>> > <gregkh@linuxfoundation.org> wrote:
>> > > This is the start of the stable review cycle for the 6.5.12 release.
>> > > There are 550 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, 17 Nov 2023 19:14:03 +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.5.12-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.5.y
>> > > and the diffstat can be found below.
>> > >
>> > > thanks,
>> > >
>> > > greg k-h
>> >
>> > We're seeing build regressions on Arm, Arm64, i386, x86, with KUnit
>> > defconfigs (and multi_v5_defconfig on Arm32):
>> > -----8<-----
>> >   In file included from /builds/linux/lib/kunit/executor.c:225:
>> >   /builds/linux/lib/kunit/executor_test.c: In function 'free_suite_set':
>> >   /builds/linux/lib/kunit/executor_test.c:130:30: error: invalid use
>> > of undefined type 'struct kunit_suite_set'
>> >     130 |         kunit_free_suite_set(*(struct kunit_suite_set *)suite_set);
>> >         |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >   /builds/linux/lib/kunit/executor_test.c: In function 'free_suite_set_at_end':
>> >   /builds/linux/lib/kunit/executor_test.c:141:49: error: invalid use
>> > of undefined type 'struct kunit_suite_set'
>> >     141 |         if (!((struct kunit_suite_set *)to_free)->start)
>> >         |                                                 ^~
>> >   /builds/linux/lib/kunit/executor_test.c:144:31: error: invalid
>> > application of 'sizeof' to incomplete type 'struct kunit_suite_set'
>> >     144 |         free = kzalloc(sizeof(struct kunit_suite_set), GFP_KERNEL);
>> >         |                               ^~~~~~
>> >   /builds/linux/lib/kunit/executor_test.c:145:17: error: invalid use
>> > of undefined type 'struct kunit_suite_set'
>> >     145 |         *free = *(struct kunit_suite_set *)to_free;
>> >         |                 ^
>> >   /builds/linux/lib/kunit/executor_test.c:145:15: error: invalid use
>> > of undefined type 'struct kunit_suite_set'
>> >     145 |         *free = *(struct kunit_suite_set *)to_free;
>> >         |               ^
>> >   make[5]: *** [/builds/linux/scripts/Makefile.build:243:
>> > lib/kunit/executor.o] Error 1
>> > ----->8-----
>> >
>> > This is with defconfig, CONFIG_KASAN=y, CONFIG_KUNIT=y, and
>> > CONFIG_KUNIT_ALL_TESTS=y. To reproduce,
>> >
>> > tuxmake \
>> >   --runtime podman \
>> >   --target-arch arm64 \
>> >   --toolchain gcc-13 \
>> >   --kconfig defconfig \
>> >   --kconfig-add CONFIG_KASAN=y \
>> >   --kconfig-add CONFIG_KUNIT=y \
>> >   --kconfig-add CONFIG_KUNIT_ALL_TESTS=y
>> >
>> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>> >
>> > Bisection is on-going.
>
>Thanks Daniel for bisecting this.
>
>> Bisection points to 3aed6e0618a9 ("kunit: test: Fix the possible
>> memory leak in executor_test"), upstream commit
>> 8040345fdae4cb256c5d981f91ae0f22bea8adcc. Reverting this commit brings
>> happiness back to the build.
>>
>> This problem is not observed on other branches.
>
>stable-rc linux-6.6.y - kunit build pass
>stable-rc linux-6.5.y - kunit build failed

Dropping the offending patch from 6.5, thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2023-11-16 14:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 19:09 [PATCH 6.5 000/550] 6.5.12-rc1 review Greg Kroah-Hartman
2023-11-15 19:16 ` [PATCH 6.5 426/550] perf pmu: Remove logic for PMU name being NULL Greg Kroah-Hartman
2023-11-15 21:38 ` [PATCH 6.5 000/550] 6.5.12-rc1 review Daniel Díaz
2023-11-16  0:00   ` Daniel Díaz
2023-11-16 13:15     ` Naresh Kamboju
2023-11-16 14:02       ` Sasha Levin [this message]
2023-11-15 22:32 ` SeongJae Park
2023-11-16 20:05 ` Florian Fainelli
2023-11-16 22:43 ` Ron Economos
2023-11-17  4:14 ` Guenter Roeck

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=ZVYg-hRRg6Npn2Gt@sashalap \
    --to=sashal@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=conor@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=davidgow@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=ruanjinjie@huawei.com \
    --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;
as well as URLs for NNTP newsgroup(s).