From: Leonardo Chiquitto Subject: Re: Automount daemon getting killed by SIGBUS Date: Thu, 25 Feb 2010 08:15:09 -0300 Message-ID: <20100225111509.GA22789@libre.l.ngdn.org> References: <20100222194830.GA11730@libre.l.ngdn.org> <4B85EB53.7010907@themaw.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=98eTGbtLwNDQI3+BiniudzOub47sQsKg3XGnnaeb304=; b=B6pYqX+vum8yJYEWMZnA7Rw6pLWtxCukPsQHX6ZAcfXFB0WUulICgm5EjMAqvkcf2A dD2B9qrwVPMvdm1gOiakBBtYus7l8dDt7TyaHzTtRNO8le1q8E21KecZuXkC5boIqOwh fq+8LqyPcLEgSVJeDjBJI5rjwt2eVrI39n/3c= Content-Disposition: inline In-Reply-To: <4B85EB53.7010907@themaw.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: Ian Kent Cc: autofs@linux.kernel.org On Thu, Feb 25, 2010 at 11:15:31AM +0800, Ian Kent wrote: > On 02/23/2010 03:48 AM, Leonardo Chiquitto wrote: > > Hello, > > > > We have a user reporting periodic crashes in automount. The daemon gets > > killed by SIGBUS when returning from spawn_mount(): > > > > Core was generated by `/usr/sbin/automount -p /var/run/automount.pid'. > > Program terminated with signal 7, Bus error. > > #0 0x0000555555566bd0 in spawn_mount (logopt=Cannot access memory at > > address 0x80004062242c > > ) at spawn.c:412 > > 412 } > > > > 0x0000555555566bcd : mov %r12d,%eax > > 0x0000555555566bd0 : pop %rbx > > 0x0000555555566bd1 : pop %r12 > > 0x0000555555566bd3 : pop %r13 > > 0x0000555555566bd5 : pop %r14 > > 0x0000555555566bd7 : pop %r15 > > 0x0000555555566bd9 : leaveq > > 0x0000555555566bda : retq > > > > Is it possible that we're exceeding stack usage at this point, mostly > > due to the call to alloca()? Do you think we should replace alloca() with > > regular malloc() in spawn.c (patch below)? > > Does this patch actually resolve your customers' problem? Unfortunately I still don't know. Customer is currently running with a workaround (increased stack limit from 8k to 32k) to avoid the problem. I did some basic tests with the patch here but decided to wait for your comments before submitting a test package. > What is the version in use and what additional patches have been applied? They are running 5.0.3 plus all the patches in patch_order-5.0.3 and autofs-5.0.4-fix_negative_cache_non-existent_key.patch, meaning that we don't have the other alloca() replacements that went in after 5.0.4. Thanks! Leonardo