Date: Wed, 17 Mar 2004 00:16:29 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Alexander Kabaev <kan@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_alloc.c Message-ID: <20040316231629.GG11578@pcwin002.win.tue.nl> In-Reply-To: <200403162206.i2GM6WWF061249@repoman.freebsd.org> References: <200403162206.i2GM6WWF061249@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--brEuL7wsLY8+TuWz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 16, 2004 at 02:06:32PM -0800, Alexander Kabaev wrote: > kan 2004/03/16 14:06:32 PST >=20 > FreeBSD src repository >=20 > Modified files: > sys/ufs/ffs ffs_alloc.c=20 > Log: > Avoid doing bawrite to initialize inode block while holding cylinder > group block locked. If filesystem has any active snapshots, bawrite > can come back trying to allocate new snapshot data block from the same > cylinder group and cause panic due to recursive lock attempt. Hey great! A friend of mine ran into what looked like this panic today. Any chance of having this backported to RELENG_5_2 (although I know it's not a security bug, it's pretty serious)? --Stijn --=20 Beware of he who would deny you access to information. For in his heart he thinks himself your master. -- Sid Meier, "Sid Meier's Alpha Centauri" --brEuL7wsLY8+TuWz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAV4rNY3r/tLQmfWcRAqnNAJoDWK4wqyCAoDb7IwDsDfcEObC4VQCZAUTf UJkEopy1oXKijerIhQzZ7Wo= =/aJY -----END PGP SIGNATURE----- --brEuL7wsLY8+TuWz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040316231629.GG11578>