Date: Wed, 20 Mar 2013 09:43:20 -0400 From: John Baldwin <jhb@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Jeremy Chadwick <jdc@koitsu.org>, Michael Landin Hostbaek <mich@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca>, freebsd-stable@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: Core Dump / panic sleeping thread Message-ID: <201303200943.20356.jhb@freebsd.org> In-Reply-To: <20130320132222.GC3794@kib.kiev.ua> References: <5148A454.1080303@FreeBSD.org> <424B99CB-A6D3-4219-A21E-62E5FB778E82@FreeBSD.org> <20130320132222.GC3794@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, March 20, 2013 9:22:22 am Konstantin Belousov wrote: > On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek wrote: > > > > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov <kostikbel@gmail.com> wrote: > > > > > > I do not like it. As I said in the previous response to Andrey, > > > I think that moving the vnode_pager_setsize() after the unlock is > > > better, since it reduces races with other thread seeing half-done > > > attribute update or making attribute change simultaneously. > > > > OK - so should I wait for another patch - or? > > I think the following is what I mean. As an additional note, why nfs > client does not trim the buffers when server reported node size change ? Will changing the size always result in an mtime change forcing the client to throw away the data on the next read or fault anyway (or does it only affect ctime)? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303200943.20356.jhb>