09:59:52 tsoome: About https://www.illumos.org/issues/18334 . How to catch this smatch errors? When I compileв illumos, I didn't see those errors. 09:59:53 → BUG 18334: stmf_sbd: string too large for strcpy() (In Progress) | https://code.illumos.org/c/illumos-gate/+/4949 10:00:21 thats newer smatch. 10:00:50 tsoome: So it needs to change Makefile before? 10:01:10 I can't push it yet there are still bunch of errors it does discover:) 10:02:15 no, not makefile, the smatch itself is updated... 10:02:25 but it is not yet on gate. 10:07:37 https://github.com/tsoome/illumos-gate/tree/smatch_update_labels is current WIP branch 10:09:05 18334 will receive a small addition soon, need to verify it and then will update gerrit. 12:43:42 tsoome: Could you give more information how to enable smatch for smtf/stmf_sbd? I would also run it and check. 12:53:08 it is enabled by default, but if you want to check with my current update, grab the https://github.com/tsoome/illumos-gate/tree/smatch_update_labels and run make install in usr/src/tools/smatch, then you can switch to branch with your changes and run make manually 15:06:26 tsoome: Sorry, I didn't get. You wrote "thats newer smatch". Does it mean that stmf is not checked by smatch? 15:07:01 it is, but the smatch on gate is older than I have. 15:07:45 so it does detect less problems... 15:15:27 tsoome: what version are you upgrading to? 15:15:45 wondering if it includes https://github.com/error27/smatch/commit/91b751f120e2054d034a4aa4e36ff176dc2fa978 15:15:45 → GitHub commit 91b751f: flow: set prev_stream (committed) 15:16:05 because that might knock some time of the build, IIRC maybe 30s? 15:18:51 I think, I have last commit as commit e9cc34fddeaf6e740cb761bf59d4615be6852652 Date: Wed Apr 22 12:30:33 2026 +0300 - from https://github.com/error27/smatch.git. I havent had time to check latest for awhile. 15:25:07 I have it + updates to smatch to track kmem_alloc and friends and almost all cleanups so far in https://github.com/tsoome/illumos-gate/tree/smatch_update_labels - however, as usual, some of the cleanups can be improved... but also, this newer smatch has bug about detecting double free I havent been able to diagnose properly - so it is not something we want to push immediately even as it does pretty good job in other areas. 16:23:01 [illumos-gate] 18314 vmc_space_unmap() iterates the held-pages list with the wrong object -- Andy Fiddaman 17:16:41 Hi i'm looking to set up a demonstration of illumos or a variant for an internal team. My ask is what's the general familiarty bias for the most popular "distribution" of illumos. 17:28:30 if you want to 'get the gist' on most actively developed illumos distributions, take a look at 'Stephen's Machine Room' illumos playlist on yt 17:30:28 he covers OI, omnios, tribblix and some smartOS 17:32:30 Copy that. Thanks. 17:34:07 Some of those videos have some fantastic dates on them. Kind of threw me off for a second with that playlist. 17:38:38 yeah, they are old-ish, but the information is, for the most part, still relevant today, afaict 17:40:11 unfortunately, nor that much of a illumos content out there, which is a shame, imho 17:43:14 I get that it's a niche, and I'm not just trying to jump to my own famliarity bias. I'll probably go back and listen to the Oxide and Friends podcast episode as well 18:02:12 jbk: Sorry to be such a pest. I'm getting a lot of pressure to get the new fileserver online and in service. Any projections on ICE driver availability? 18:10:59 [illumos-gate] 18301 zfs panic "decompression failed" with gzip compression and low memory -- Matthew Ahrens 18:59:00 nomad: i'm working on it... that's the best I can say... 18:59:25 this thing is so fucking overengineered, it could be working today, or it could be another two months of working through code 18:59:41 i'm sorry but you really should have chosen a different NIC 19:00:03 i'm working my ass off trying to get it working, but even that doesn't seem to be enough 19:01:05 (I actually hope it's the last NIC intel produces, because there's no way I'm writing a driver for the next one) 19:02:19 I wish we'd had a different NIC as well but the only alternative we were offered is one danmcd said to avoid so we went with this one. 19:05:22 IIRC the alternative was something that would never be supported. I think it was from broadcom but I could easily be misremembering. 21:06:46 ENOMAD it was Broadcom.