For some time now, gpg has been having issues on my -CURRENT system with being unable to mlock() the ~8k buffer it uses to hold the decrypted secret key. A ktrace shows that it's being returned an EAGAIN from mlock(), which my peeking around has shown could be: 1) I hit the RLIMIT_MLOCK limit on memory locking, or 2) I hit the system-wide "wired pages" limit. There are no memlock resource limits, so I figure it must be #2. I have managed to figure out that the limit in question is held in "vm_page_max_wired" in vm_pageout.c, but I can't find any way to display this number at runtime. I have (I think) plenty of RAM on this machine, certainly enough for gpg to lock 8k of it for a few seconds, so I dunno why I'd be hitting any system-wide limit. Any advice on where to look further? --Mike
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:07 UTC