On Thu, Jun 06, 2024 at 11:10:43AM -0700, Kees Cook wrote: > On Thu, Jun 06, 2024 at 08:48:37PM +0300, Andy Shevchenko wrote: > > On Thu, Jun 6, 2024 at 8:46 PM Kees Cook <kees@xxxxxxxxxx> wrote: > > > > > > On Thu, Jun 06, 2024 at 08:35:13PM +0300, Andy Shevchenko wrote: > > > > On Thu, Jun 6, 2024 at 6:56 PM Kees Cook <kees@xxxxxxxxxx> wrote: > > > > > On Thu, 06 Jun 2024 15:46:09 +0100, Jean-Philippe Brucker wrote: > > > > > > > > [...] > > > > > > > > > Applied to for-next/hardening, thanks! > > > > > > > > Btw, is it possible to get this for v6.10, so we may start enabling it > > > > for others? > > > > > > Which others do you mean? > > > > There are a lot of users of kmemdup(x*y) which I want to convert > > sooner than later to kmemdup_array(x,y). > > Ah-ha, I see what you mean. Well, I'm not sure we can do v6.10 for this > because rc2 is behind us, and that's what most subsystems merge to. I > can land the patch for rc3 so there will be no warnings in Linus's > tree/-next, but conversions in subsystem trees will gain warnings, I > think... I see, but v6.10-rc3 is still better than v6.11-rc1. Some of the subsystems are okay to merge rcX to their for-next if needed. -- With Best Regards, Andy Shevchenko
