Date: Fri, 25 Jul 2014 00:45:52 +0400 From: Andrey Chernov <ache@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-10@freebsd.org Subject: Re: svn commit: r269055 - stable/10/sys/kern Message-ID: <53D17080.4010407@freebsd.org> In-Reply-To: <20140724194820.GV93733@kib.kiev.ua> References: <201407241043.s6OAhFoF061672@svn.freebsd.org> <53D15F14.9010606@freebsd.org> <20140724194820.GV93733@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24.07.2014 23:48, Konstantin Belousov wrote: > On Thu, Jul 24, 2014 at 11:31:32PM +0400, Andrey Chernov wrote: >> On 24.07.2014 14:43, Konstantin Belousov wrote: >>> Author: kib >>> Date: Thu Jul 24 10:43:15 2014 >>> New Revision: 269055 >>> URL: http://svnweb.freebsd.org/changeset/base/269055 >>> >>> Log: >>> MFC r268384: >>> When the lock was stolen from us, retry the whole lock sequence in kernel, >>> instead of returning EINTR. >> >> Does it make dead loop possible? > > What is dead loop ? I mean infinite retries with returning EDOOFUS each time and goto retry_setlock; again. > Do you see a problem on your machine ? No, just by looking at the commit message. -- http://ache.vniz.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D17080.4010407>