[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1HPqdBbv83VqCvp@zx2c4.com>
Date: Thu, 20 Oct 2022 16:46:01 -0600
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Alexey Dobriyan <adobriyan@...il.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
mm-commits@...r.kernel.org, masahiroy@...nel.org,
gregkh@...uxfoundation.org, Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH -mm] -funsigned-char, x86: make struct
p4_event_bind::cntr signed array
On Fri, Oct 21, 2022 at 12:34:37AM +0300, Andy Shevchenko wrote:
> On Thu, Oct 20, 2022 at 01:17:33PM -0700, Linus Torvalds wrote:
> > On Thu, Oct 20, 2022 at 12:39 PM Linus Torvalds
> > <torvalds@...ux-foundation.org> wrote:
>
> ...
>
> > And in some cases the differences are enormous:
> >
> > - drivers/net/wireless/ralink/rt2x00/rt2800lib.c generates a 220kB diff
> >
> > which seems to be due to entirely different inlining decisions or
> > something, and the differences are so enormous that I didn't even
> > start looking at the cause.
>
> This one is what we start the epopee from. I think Jason handled it in his last
> patch against this certain driver.
Right, and Kale is taking it for 6.1, because it fixes existing breakage
on ARM. But it's not broken on x86 with -funsigned-char.
Jason
Powered by blists - more mailing lists