[OpenAFS-devel] Linux deadlocks (possibly fixed in IBM-AFS)

[Neulinger, Nathan]

It would be nice if we could put together test cases for some of
these... I've got a few various test things that I run for problems that
have occurred in the past, but might be nice if we had something as part
of the repository that could be added to easily...=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: chas williams [mailto:chas@cmf.nrl.navy.mil]=20
> Sent: Wednesday, July 03, 2002 10:35 AM
> To: Broughton, Travis V
> Cc: OpenAFS-Devel Mailing List (E-mail)
> Subject: Re: [OpenAFS-devel] Linux deadlocks (possibly fixed=20
> in IBM-AFS)=20
>=20
>=20
> >	srikanth-IY31752-afs3.6-race-condition-in-afs-buffer-cache 1.2
>=20
> i cannot comment on this.  with the description though it should be=20
> easy to check/fix/add.
>=20
> >	srikanth-12885-afs3.6-race.condition.in.linux.event.handling 1.5
>=20
> i believe i helped srikanth with this issue -- he messaged this list
> about the problem.  i developed what i consider a 'correct' fix which
> is in the latest devel and stable releases.  its probably=20
> similar, although
> however, i also eliminated the glock droppping in=20
> osi_linux_alloc() since
> you could still 'loose' a wakeup when adding the event the first time
> through the loop.
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20