From: Ian Kent <raven@themaw.net>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: Automount daemon getting killed by SIGBUS
Date: Thu, 25 Feb 2010 11:15:31 +0800 [thread overview]
Message-ID: <4B85EB53.7010907@themaw.net> (raw)
In-Reply-To: <20100222194830.GA11730@libre.l.ngdn.org>
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 <spawn_mount+829>: mov %r12d,%eax
> 0x0000555555566bd0 <spawn_mount+832>: pop %rbx
> 0x0000555555566bd1 <spawn_mount+833>: pop %r12
> 0x0000555555566bd3 <spawn_mount+835>: pop %r13
> 0x0000555555566bd5 <spawn_mount+837>: pop %r14
> 0x0000555555566bd7 <spawn_mount+839>: pop %r15
> 0x0000555555566bd9 <spawn_mount+841>: leaveq
> 0x0000555555566bda <spawn_mount+842>: 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?
What is the version in use and what additional patches have been applied?
Ian
next prev parent reply other threads:[~2010-02-25 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100222194830.GA11730@libre.l.ngdn.org>
2010-02-23 2:46 ` Automount daemon getting killed by SIGBUS Ian Kent
2010-02-25 3:15 ` Ian Kent [this message]
2010-02-25 11:15 ` Leonardo Chiquitto
2010-02-26 2:30 ` Ian Kent
2010-03-18 0:07 ` Leonardo Chiquitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B85EB53.7010907@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=leonardo.lists@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.