You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under HardenedBSD(which is a downstream fork of FreeBSD), the memory system is hardened and the 32bit compat code is taken out. This means that the gopsutil fingerprinting under nomad fails:
but gopsutil is vendored with an older version that uses uint32 here.
It looks like there was some work recently in #5201 to upgrade gopsutil. I'd like you to perhaps re-apply that patch and upgrade your vendored gopsutil.
Which fixes the problem. I understand HardenedBSD is not officially supported, and so maybe you don't care much, except uint32 is apparently even wrong under FreeBSD. It currently works under FreeBSD because of compat code to let a uint32 work. That compat code will probably go away at some point :)
Anyways, for the adventurous among us, one can change the call like in the diff above in the meantime. if you want your HardenedBSD and Nomad to co-exist.
thanks to lattera & newnix in #HardenedBSD for their help.
Thanks for your time and consideration.
The text was updated successfully, but these errors were encountered:
@peacetara Thanks for the report. Given the surface area of usage of gopsutil we would do a vendor upgrade in a major release, will consider this ticket then.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Issue
Under HardenedBSD(which is a downstream fork of FreeBSD), the memory system is hardened and the 32bit compat code is taken out. This means that the gopsutil fingerprinting under nomad fails:
which happens on this call (kdump output):
This call fails because go expects a uint32, but it's actually a uint64 in size.
Solutions
upsteam gopsutil properly uses a uint64 here
but gopsutil is vendored with an older version that uses uint32 here.
It looks like there was some work recently in #5201 to upgrade gopsutil. I'd like you to perhaps re-apply that patch and upgrade your vendored gopsutil.
Alternatively, one can apply this patch:
Which fixes the problem. I understand HardenedBSD is not officially supported, and so maybe you don't care much, except uint32 is apparently even wrong under FreeBSD. It currently works under FreeBSD because of compat code to let a uint32 work. That compat code will probably go away at some point :)
Anyways, for the adventurous among us, one can change the call like in the diff above in the meantime. if you want your HardenedBSD and Nomad to co-exist.
thanks to lattera & newnix in #HardenedBSD for their help.
Thanks for your time and consideration.
The text was updated successfully, but these errors were encountered: