From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933900AbdKBPkO (ORCPT ); Thu, 2 Nov 2017 11:40:14 -0400 Received: from mail-io0-f178.google.com ([209.85.223.178]:43175 "EHLO mail-io0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933567AbdKBPkM (ORCPT ); Thu, 2 Nov 2017 11:40:12 -0400 X-Google-Smtp-Source: ABhQp+RkmnpA79u/dDbtQ/q5bMXrTSxKl8u7LEu2nkXd12h2/m2dYjI3FHl2BbhRgXnKRWEA3cIYtm+wwRoeUOksWAE= MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Thu, 2 Nov 2017 08:40:11 -0700 X-Google-Sender-Auth: wrvNPEHmtDlMX4YYV4G-jBJyXgw Message-ID: Subject: Re: Regression: commit da029c11e6b1 broke toybox xargs. To: Rob Landley Cc: Kees Cook , Linux Kernel Mailing List , toybox@lists.landley.net Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 1, 2017 at 9:28 PM, Linus Torvalds wrote: > > Behavior changed. Things that test particular limits will get different > results. That's not breakage. > > Did an actual user application or script break? Ahh. I should have read that email more carefully. If xargs broke, that _will_ break actual scripts, yes. Do you actually set the stack limit to insane values? Anybody using toybox really shouldn't be doing 32MB stacks. So I still do wonder if this actually breaks anything real, or just a test-suite or something? Linus