Date: Wed, 3 May 2006 14:31:04 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Tor Egge <tegge@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_snapshot.c ffs_vnops.c Message-ID: <20060503183104.GA31055@xor.obsecurity.org> In-Reply-To: <20060503172526.H98950@woozle.rinet.ru> References: <200605022352.k42Nqi1s095377@repoman.freebsd.org> <20060503172526.H98950@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 05:36:57PM +0400, Dmitry Morozovsky wrote: > Dear Tor, >=20 > On Tue, 2 May 2006, Tor Egge wrote: >=20 > TE> Modified files: > TE> sys/ufs/ffs ffs_snapshot.c ffs_vnops.c=20 > TE> Log: > TE> Close a race when VOP_LOCK() on a snapshot file is attempted at the > TE> same time as it is changed back into a normal file. The locker wou= ld > TE> get the shared "snaplk" lock which would no longer be the correct l= ock > TE> for the vnode. >=20 > Any chance this (and subsequent) change(s) would fix snaplk errors report= ed by=20 > me? How can I help testing (patch applied cleanly, but I hesitate to test= it=20 > blindly ;) It does not, but these are some related issues found while testing. Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWPboWry0BWjoQKURAiN5AKDg84SM0zjYI3U3dSt0uuTRYxknsACfXu5Q l3eHsnI3Y/XEgeWv1Kci8vA= =q8zl -----END PGP SIGNATURE----- --huq684BweRXVnRxX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060503183104.GA31055>