Re: Core Dump / panic sleeping thread
--ZZEGMFFBHS0xR+g5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Mar 20, 2013 at 09:43:20AM -0400, John Baldwin wrote:
> 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:
> > >=20
> > > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov <kostikbel@gmail.co=
m>=20
> wrote:
> > > >=20
> > > > 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.
> > >=20
> > > OK - so should I wait for another patch - or?=20
> >=20
> > 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 ?
>=20
> Will changing the size always result in an mtime change forcing the clien=
t to
> throw away the data on the next read or fault anyway (or does it only aff=
ect
> ctime)?
UFS only modifies ctime on truncation, it seems.
--ZZEGMFFBHS0xR+g5
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iQIcBAEBAgAGBQJRSga/AAoJEJDCuSvBvK1BfAYP/1EgLiteMNeP9kXLF2tMgTju
suAOy0hYjAYl4leyyYS4l93n7Z2prDo8Ml+OrnJkTC52VdDwgag4z1+QuXK2a6SK
crbxb6It+7kILt+WG12ydX8p28DI0zx2RR+lf6B3OP3Dk5eYww62sBGZ9fIqr3zz
ELZozO2ehVoSSIGlxmcznoWudtQTKZ/PYDV6vvDS0sQ9/5DcqXupAoAlwFYxDGRB
CSlg9B45Bm/MEc/MK2+KE1ut4nBRjteXjB5snKlKv0e630ycNKQovby1rJXQGLGh
CKKSHG6TuOtI8MFSl7+8Wvzw2vVVtps2bzMJgspsDpO0rtLJEolcLqXR+aVPfCxv
2wvxG0v67bqvLOSGRKBC9TE+Lddh9oBHPRIqFwYX5lmQh8i6JBPT74H4BlNMRRAb
gKCdh6RHiYohFGKe+v/ZK+GSq7ptbjqQu/jmG6Po2hFY/QO8p4q3RNolkGwXKOVf
qmb58Uzt/4J8wAd3vPej0F6RNflw0/d2CJ1nGYx+ZSnNJ0TnmJTCsI3jiJ7GOug6
uyFB6CmJp6XPubBT1+9qLrVWw8v6irBnZKcDzl/800LQEChWwbhcHnM+6dDjStiB
ueBkNOsvc4RL7jNeRTa3uIT13QiBELyIpA3Fn26PldHWtCPcbpvDqTukVq5ExCji
wAZpvjsinWbW4eroNlVg
=cpXk
-----END PGP SIGNATURE-----
--ZZEGMFFBHS0xR+g5--
討論串 (同標題文章)
完整討論串 (本文為第 22 之 22 篇)：