On Thu, Apr 5, 2018 at 1:20 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > On Thu, Apr 5, 2018 at 12:52 PM, Kees Cook <keesc...@chromium.org> wrote: >> >> This patch seems finished (*knock on wood*). Do you want to take this >> directly for v4.17, should I send a single-patch pull-request, or >> should this go through -mm (for either 4.17 or 4.18)? > > I was actually expecting it to go with the other VLA removal patches, > but if the plan is to try to just get them in individual maintainer > trees, I guess I can just take this directly.
Yeah, the VLA patches have been going through maintainer trees -- mostly due to needing specialized review, etc. While many are trivial, a fair number aren't (or at least the trade-offs aren't always obvious). > So if it would be a single-commit pull request, I'll just take it as a > patch. I guess it could go through -mm, but since I was involved in > the discussion anyway, I also don't mind just taking it directly. If > it causes problems, I can curse at myself. Yeah, I'm in no rush to collect the "unresponded" VLA patches into a tree, and we've still got more to go, so right now it'd just be a single-patch pull. If you can snag it now, that'd be great! :) Thanks! -Kees -- Kees Cook Pixel Security
