Re: Linux 5.16-rc1

From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Nick Terrell <nickrterrell@gmail.com>,
	Nick Terrell <terrelln@fb.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.16-rc1
Date: Mon, 15 Nov 2021 09:53:25 -0800	[thread overview]
Message-ID: <CAHk-=wgm-Co+ys0TQKZ8aRp-NGTb+ER-VFmEOEVamH724cWwFQ@mail.gmail.com> (raw)
In-Reply-To: <652edea7-28a0-70d9-c63f-d910b5942454@roeck-us.net>

On Mon, Nov 15, 2021 at 9:07 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> Top of tree is a bit better:

Thanks for re-testing.

That doesn't actually look all that bad for -rc1.  Several of them
already have fixes, and most of the rest look "easily fixable".

Famous last words.

The most worrisome ones are probably the stack frame complaint ones
(libzstd and a couple of powerpc ones) that Geert also reported, but
they might at least to some degree be as simple as just due to the
same excessive inlining that was already fingered for the code bloat.

But it could be more fundamental - the kernel just doesn't like stack
allocations the same way user space does, so the sync-up to a newer
libzstd might be a bit more problematic than just "don't force
inlining".

Nick - you've been cc'd twice because you sign off your commits with
your work email, but then seem to actually prefer the personal one, so
I didn't know which to use and just added both. See

  https://lore.kernel.org/lkml/652edea7-28a0-70d9-c63f-d910b5942454@roeck-us.net/
  https://lore.kernel.org/lkml/20211115155105.3797527-1-geert@linux-m68k.org

if you didn't already.

               Linus