Date: Mon, 6 Jun 2016 21:08:58 -0700 From: Conrad Meyer <cem@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Mark Johnston <markj@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: thread suspension when dumping core Message-ID: <CAG6CVpW7uWY0umFj8z7gNY5vQWPqxALzD38brB5BPTKSm9BsGw@mail.gmail.com> In-Reply-To: <20160607024610.GI38613@kib.kiev.ua> References: <20160604022347.GA1096@wkstn-mjohnston.west.isilon.com> <20160604093236.GA38613@kib.kiev.ua> <20160606171311.GC10101@wkstn-mjohnston.west.isilon.com> <20160607024610.GI38613@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 6, 2016 at 7:46 PM, Konstantin Belousov <kostikbel@gmail.com> wrote: > On Mon, Jun 06, 2016 at 10:13:11AM -0700, Mark Johnston wrote: >> On Sat, Jun 04, 2016 at 12:32:36PM +0300, Konstantin Belousov wrote: >> > Does your fs both set TDF_SBDRY and call lf_advlock()/lf_advlockasync() ? >> >> It doesn't. This code belongs to a general framework for distributed FS >> locks; in this particular case, the application was using it to acquire >> a custom advisory lock. > What statement was not true: that your code sets TDF_SBDRY, or that > the lf_advlock() function was called ? We set TDF_SBDRY; we don't call lf_advlock(). I don't have the core yet, so I can't get the thread information, sorry. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpW7uWY0umFj8z7gNY5vQWPqxALzD38brB5BPTKSm9BsGw>