Date: Fri, 05 Oct 2001 16:17:14 -0700 From: Yevgeniy Aleynikov <eugenea@infospace.com> To: Kirk McKusick <mckusick@mckusick.com> Cc: Ian Dowse <iedowse@maths.tcd.ie>, Matt Dillon <dillon@earth.backplane.com>, peter@FreeBSD.ORG, ache@FreeBSD.ORG, Ken Pizzini <kenp@infospace.com>, hackers@FreeBSD.ORG Subject: Re: bleh. Re: ufs_rename panic Message-ID: <3BBE3F7A.98FBC714@infospace.com> References: <200110030610.f936AbR11859@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems like there's no activity on this subject. This is local DoS, guys. if it gets on public (which is probably gonna be soon) everything everywhere will be crashing, and there's no stable fix ready. How can i help to accelerate this problem solution? .... And why FreeBSD security officer's email address always bounces my mail? Thanks! Kirk McKusick wrote: > > The problems all arise from the fact that we unlock the source > while we look up the destination, and when we return to relookup > the source, it may have changed/moved/disappeared. The reason to > unlock the source before looking up the destination was to avoid > deadlocking against ourselves on a lock that we held associated > with the source. Since we now allow recursive locks on vnodes, it > is no longer necessary to release the source before looking up > the destination. So, it seems to me that the correct fix is to > *not* release the source after looking it up, but rather hold it > locked while we look up the destination. We can completely get > rid of relookup and lots of other hairy code and generally make > rename much simpler. Am I missing something here? > > ~Kirk -- Yevgeniy Aleynikov Infospace, Inc. SysAdmin, USE Work: (206)357-4594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BBE3F7A.98FBC714>