Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752438AbdHAUTw (ORCPT ); Tue, 1 Aug 2017 16:19:52 -0400 Received: from mail-oi0-f67.google.com ([209.85.218.67]:38301 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752044AbdHAUTu (ORCPT ); Tue, 1 Aug 2017 16:19:50 -0400 MIME-Version: 1.0 In-Reply-To: References: <1501545093-56634-1-git-send-email-keescook@chromium.org> From: Linus Torvalds Date: Tue, 1 Aug 2017 13:19:49 -0700 X-Google-Sender-Auth: Q-Bg-F8FNKdZQH3GKk5WhZOYTdg Message-ID: Subject: Re: [PATCH v4 00/15] exec: Use sane stack rlimit under secureexec To: Kees Cook Cc: James Morris , Andrew Morton , David Howells , "Eric W. Biederman" , John Johansen , "Serge E. Hallyn" , Paul Moore , Stephen Smalley , Casey Schaufler , Tetsuo Handa , James Morris , Andy Lutomirski , "linux-fsdevel@vger.kernel.org" , linux-security-module , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 517 Lines: 12 On Tue, Aug 1, 2017 at 8:04 AM, Kees Cook wrote: > > Do you want me to carry this for -next and send it as a distinct pull > request for v4.14? Yes, I think that would be preferred. I consider this a "execve()" cleanup/change with implications for the security models rather than the other way around, so I'd rather keep it separate, and you already have a few other git trees so I think it makes sense to just treat it as another of your git pulls next merge window. Linus