From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/3] fs/binfmts: Better handling of binfmt loops
Date: Tue, 30 Jul 2013 14:04:46 -0700
Message-ID: <20130730140446.1a4982e21ac8e183c65e9ed1@linux-foundation.org>
References: <1374766845-13565-1-git-send-email-zml@linux.vnet.ibm.com>
	<1374766845-13565-2-git-send-email-zml@linux.vnet.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	viro@zeniv.linux.org.uk, Zach Levis <zach@zachsthings.com>
To: Zach Levis <zml@linux.vnet.ibm.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <1374766845-13565-2-git-send-email-zml@linux.vnet.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Thu, 25 Jul 2013 08:40:44 -0700 Zach Levis <zml@linux.vnet.ibm.com> wrote:

> With these changes, when a binfmt loop is encountered,
> the ELOOP will propogate back to the 0 depth. At this point the
> argv and argc values will be reset to what they were originally and an
> attempt is made to continue with the following binfmt handlers.

hm, why?  What problem does this fix?  What value does the change offer
to our users?