Date: Sun, 9 Jul 2006 09:28:04 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Chuck Lever <chucklever@gmail.com> Cc: cvs-src@freebsd.org, src-committers@freebsd.org Subject: Re: cvs commit: src/sys/nfsclient nfs_socket.c Message-ID: <20060709062804.GB37822@deviant.kiev.zoral.com.ua> In-Reply-To: <76bd70e30607081205v57db0e48w70fa9025391b9fcb@mail.gmail.com> References: <200607081539.k68FdB5D007666@repoman.freebsd.org> <76bd70e30607081205v57db0e48w70fa9025391b9fcb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--uWAbeGC4mMoqIxdF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 08, 2006 at 03:05:35PM -0400, Chuck Lever wrote: > On 7/8/06, Konstantin Belousov <kib@freebsd.org> wrote: > >kib 2006-07-08 15:39:11 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/nfsclient nfs_socket.c > > Log: > > Signals may be delivered to process as well as to the thread. Check the > > thread-delivered signals in addition to the process one. > > > > Reviewed by: mohan > > MFC after: 1 month > > Approved by: kan (mentor) > > > > Revision Changes Path > > 1.142 +3 -1 src/sys/nfsclient/nfs_socket.c >=20 > Is this a problem in the NFSv4 client as well? Hmm, as it seems, rpcclnt_sigintr correctly accounts for both thread and process signals. On the other hand, another my commit, into nfs_vnops.c, is relevant to the nfs4. I do not have infrastructure for nfs v4 testing, and would like to obtain the opinion of somebody who knows nfs4 client before considering commiting that. --uWAbeGC4mMoqIxdF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsKHzC3+MBN1Mb4gRAsRXAJ9DIBBtUFiSIRlQi0c/uQNEu/1z0ACg131l pcjl3ksh5Q4X4jSWx3MAp2M= =T5o7 -----END PGP SIGNATURE----- --uWAbeGC4mMoqIxdF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060709062804.GB37822>