From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Weinberger Subject: Re: [PATCH][Resend v2] Fix infinite loop in search_binary_handler() Date: Mon, 4 Jul 2011 13:57:43 +0200 Message-ID: <201107041357.43481.richard@nod.at> References: <1309779003-8668-1-git-send-email-richard@nod.at> <201107042051.HEB57830.OJFtMLFSOHFVQO@I-love.SAKURA.ne.jp> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: viro@zeniv.linux.org.uk, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Tetsuo Handa Return-path: Received: from a.ns.miles-group.at ([95.130.255.143]:49040 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750949Ab1GDL5p (ORCPT ); Mon, 4 Jul 2011 07:57:45 -0400 In-Reply-To: <201107042051.HEB57830.OJFtMLFSOHFVQO@I-love.SAKURA.ne.jp> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Am Montag 04 Juli 2011, 13:51:55 schrieb Tetsuo Handa: > Richard Weinberger wrote: > > Running a x86_64 kernel without ia32 emulation and a x86 user land > > triggers this issue. > > Executing /sbin/modprobe for x86_32 on an x86_64 kernel without x86_32 > support? Yep. > Anyway, request_module() calls __request_module() but > __request_module() stops at MAX_KMOD_CONCURRENT levels of nesting. > So, I think "infinite loop" cannot happen. Booting a x86_64 UML kernel with x86_32 user land triggers this issue. I always wondered why the UML kernel hangs an consumes 100% CPU. Thanks, //richard