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 _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
