Re: HEADS UP: NFS changes coming into CURRENT early February

2025-02-01 Thread Gleb Smirnoff
On Sat, Feb 01, 2025 at 06:06:27AM -0800, Rick Macklem wrote: R> You might want to put an entry in UPDATING noting that the daemons R> need to be upgraded with the kernel. Of course I did :) Short update on the resource leaks. The patch that reduces refcount on the back channel proved to be inco

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-02-01 Thread Rick Macklem
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote: > > CAUTION: This email originated from outside of the University of Guelph. Do > not click links or open attachments unless you recognize the sender and know > the content is safe. If in doubt, forward suspicious emails to > ith...@uoguelph

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-28 Thread Gleb Smirnoff
On Tue, Jan 28, 2025 at 09:14:00PM -0800, Gleb Smirnoff wrote: T> Second, with the patch the M_RPC leak count for me is 2. And I found that these T> two items are basically is a clnt_vc that belongs to a closed connection: T> T> f80029614a80 tcp4 0 0 10.6.6.9.772 10.6.6.9.204

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-28 Thread Gleb Smirnoff
On Mon, Jan 27, 2025 at 06:10:42PM -0800, Rick Macklem wrote: R> I think I've found a memory leak, but it shouldn't be a show stopper. R> R> What I did on the NFS client side is: R> # vmstat -m | fgrep -i rpc R> # mount -t nfs -o nfsv4,tls nfsv4-server:/ /mnt R> # ls --lR /mnt R> --> Then I networ

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-27 Thread Rick Macklem
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote: > > CAUTION: This email originated from outside of the University of Guelph. Do > not click links or open attachments unless you recognize the sender and know > the content is safe. If in doubt, forward suspicious emails to > ith...@uoguelph

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-26 Thread Rick Macklem
On Sun, Jan 26, 2025 at 1:44 PM Rick Macklem wrote: > > On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote: > > > > CAUTION: This email originated from outside of the University of Guelph. Do > > not click links or open attachments unless you recognize the sender and > > know the content is s

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-26 Thread Rick Macklem
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote: > > CAUTION: This email originated from outside of the University of Guelph. Do > not click links or open attachments unless you recognize the sender and know > the content is safe. If in doubt, forward suspicious emails to > ith...@uoguelph

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-24 Thread Gleb Smirnoff
On Thu, Jan 23, 2025 at 02:42:54PM -0800, Rick Macklem wrote: R> > The code is posted on phabricator, reviews D48547 through D48552. R> > Reviewers are very welcome! R> > R> > I share my branch on Github. It is usually rebased on today's CURRENT: R> > R> > https://github.com/glebius/FreeBSD/commits

Re: HEADS UP: NFS changes coming into CURRENT early February

2025-01-23 Thread Rick Macklem
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote: > > CAUTION: This email originated from outside of the University of Guelph. Do > not click links or open attachments unless you recognize the sender and know > the content is safe. If in doubt, forward suspicious emails to > ith...@uoguelph

HEADS UP: NFS changes coming into CURRENT early February

2025-01-21 Thread Gleb Smirnoff
Hi, TLDR version: users of NFS with Kerberos (e.g. running gssd(8)) as well as users of NFS with TLS (e.g. running rpc.tlsclntd(8) or rpc.tlsservd(8)) as well as users of network lock manager (e.g. having 'options NFSLOCKD' and running rpcbind(8)) are affected. You would need to recompile & rei