Date: Fri, 30 May 2003 17:11:56 +0800 From: "David Xu" <davidxu@freebsd.org> To: "Terry Lambert" <tlambert2@mindspring.com>, "Bryan Liesner" <bleez@verizon.net> Cc: freebsd-current@freebsd.org Subject: Re: panic: kern/52718 Message-ID: <000701c3268b$86faaa30$f001a8c0@davidw2k> References: <20030529164240.X769@gravy.homeunix.net> <3ED71E39.A0F8EBC3@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----=20 From: "Terry Lambert" <tlambert2@mindspring.com> To: "Bryan Liesner" <bleez@verizon.net> Cc: <freebsd-current@freebsd.org> Sent: Friday, May 30, 2003 5:02 PM Subject: Re: panic: kern/52718 > Bryan Liesner wrote: > >=20 > > Is anyone going to look at this before the next release? > > Of course, if more info is needed, I'll send it along. No dump is > > available - it panics during boot. > >=20 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D52718 >=20 > This was caused by rev. 1.3 of a commit by Jeff Robertson to > kern_utmx.c. The problem is that the proc struct is not locked > for: >=20 > FOREACH_THREAD_IN_PROC(td->td_proc, td0) >=20 > in the lock and unlock. >=20 > Either lock the proc before and unlock it after this, in both > _utmx_lock() and _utmx_unlock(), or revert the code to 1.2. >=20 > It's pretty simple. No one needs t look at it, all they need > to do is act on information already present. >=20 kern_sig.c has same issue in several places. > -- Terry > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000701c3268b$86faaa30$f001a8c0>