Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Sep 2019 15:28:52 +0000
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>
Subject:   Re: Re; svn commit: r352393 - head/sys/fs/nfsclient
Message-ID:  <YTXPR0101MB2189EE93CBE934C637446263DD8C0@YTXPR0101MB2189.CANPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <YTXPR0101MB21890232925E49EDEAF10772DD8C0@YTXPR0101MB2189.CANPRD01.PROD.OUTLOOK.COM>
References:  <YTXPR0101MB21890232925E49EDEAF10772DD8C0@YTXPR0101MB2189.CANPRD01.PROD.OUTLOOK.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
Resent to correct address...=0A=
=0A=
________________________________________=0A=
From: Rick Macklem=0A=
Sent: Monday, September 16, 2019 11:27 AM=0A=
To: kib@freebsd.org; peterj@freebsd.org=0A=
Cc: src-svn-all@freebsd.org=0A=
Subject: Re; svn commit: r352393 - head/sys/fs/nfsclient=0A=
=0A=
Hi Kostik,=0A=
=0A=
I'm afraid there was a reason that only certain cases (where the file was=
=0A=
being shrunk) did the vnode_pager_setsize() call after the NFS node=0A=
lock is released.=0A=
=0A=
See the commit log message for r252528.=0A=
=0A=
If vnode_pager_setsize() now acquires a sleep lock for the case where the=
=0A=
size is increasing, it sounds like the NFS node lock will have to become a=
=0A=
sleep lock instead of a mutex.=0A=
(If needed, I can get working on this in a day or two.)=0A=
=0A=
rick=0A=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR0101MB2189EE93CBE934C637446263DD8C0>