Date: Sat, 25 Oct 2003 16:37:49 -0700 From: Alfred Perlstein <bright@mu.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_sig.c Message-ID: <20031025233749.GW99943@elvis.mu.org> In-Reply-To: <200310251614.h9PGE925019013@repoman.freebsd.org> References: <200310251614.h9PGE925019013@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is bad, it's time to add a flag to the vnode to do this properly instead of relying upon the underlying FS to implement the locking. * Robert Watson <rwatson@FreeBSD.org> [031025 09:14] wrote: > rwatson 2003/10/25 09:14:09 PDT > > FreeBSD src repository > > Modified files: > sys/kern kern_sig.c > Log: > When generate a core dump, use advisory locking in an advisory way: > if we do acquire an advisory lock, great! We'll release it later. > However, if we fail to acquire a lock, we perform the coredump > anyway. This problem became particularly visible with NFS after > the introduction of rpc.lockd: if the lock manager isn't running, > then locking calls will fail, aborting the core dump (resulting in > a zero-byte dump file). > > Reported by: Yogeshwar Shenoy <ynshenoy@alumni.cs.ucsb.edu> > > Revision Changes Path > 1.260 +6 -6 src/sys/kern/kern_sig.c -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031025233749.GW99943>