00:01:25 it should be freshly allocated in arc_write_ready, just before calling abd_copy(). however, as ::whatis is suggesting some of those pointers are actually freed from cache, I kind of fail to see how... of course, if some other thread was poking this arc_buf_hdr ... 00:01:43 anyhow, its too late here, need to sleep on this:D 00:16:49 tsoome: There were some commits by amotin to OpenZFS recently that might or might not be relevant. 00:17:33 I recall some of the changes involving ensuring done callbacks were properly called. I also vaguely remember a recent PR about reference counts. 00:18:40 Oh. The reference count patch was in the DMU/DSL and was by someone else: https://github.com/openzfs/zfs/commit/d816bc5ec76b050ab5319112320e1676d538161c 15:02:55 [illumos-gate] 14596 cstyle should allow empty increment with for loop -- Toomas Soome 16:59:15 is it me, or is redmine being sluggish? 16:59:26 It is not just you 17:00:29 there it goes... 17:01:15 granted that was a long description 17:01:20 (#15420) 17:02:17 but i thought it might be helpful to show how we got from 'devinfo callers are stuck in the kernel' to 'deadlock between dls and mac' 17:02:34 since it was a bit of a journey 17:04:07 so many bad memories of that journey 17:08:54 Really nice write up :) 17:09:41 I have just been looking at lock ordering in this area for issue 15167 (fenix) 17:09:50 fenix will no doubt take a while to talk to remine too.. 17:09:54 *redmine 17:10:09 BUG 15167: Panic when halting a zone with self-created links (In Progress) 17:10:09 ↳ https://www.illumos.org/issues/15167 | https://code.illumos.org/c/illumos-gate/+/2662 17:10:36 the 'modunload -i 0' in /sbin/rc3 was probably the most 'whaaaa' part of it honestly :) 17:58:16 unfortunately, i'm not entirely sure of how to fix it... 18:02:54 missed the context on the modunload -i 0 but IIRC that's related to reducing kernel footprint after a reconfiguration reboot when all modules get loaded to see if they're needed. 18:04:43 yep. 18:04:48 ah, it's in #15420 18:04:54 (the context, that is) 18:05:50 and, yes, that's a good writeup. 18:53:32 if there's one thing I took working for joyent, it's a huge appreciation for good bug descriptions 18:54:16 it kinda spoiled me when then getting bug reports that consist wholly of 'xxx is busted' :) 18:54:23 (elsewhere) 18:58:05 fenix illumos 15420 18:58:16 fenix illumos#15420 18:58:16 BUG 15420: dls_devnet_destroy can deadlock with link notifications (New) 18:58:16 ↳ https://www.illumos.org/issues/15420 19:15:49 [illumos-gate] 15402 Incorrect service name and other errors in the zonestat(1) manual -- Peter Tribble 19:52:46 jbk: Joyent is not the only place that values good bug descriptions. OpenZFS/ZFSOnLinux values it too. In fact, I learned to write good commit messages and descriptive reports from Brian shortly after I started contributing. There are times when I feel that I am writing excessive amounts of documentation, but so far, I have never once heard someone tell me to write less. 19:53:43 In fact, at the OpenZFS developer summit last year, I mentioned at the bar that I felt that I was writing excessive documentation for changes. I was told to keep doing it. :D 20:02:09 Detailed long-form bug writeups were part of the engineering culture within the part of Sun where I worked and it's good to see that this has carried over in the diaspora... 20:04:33 yeah, i'm sure that came from the various ex-sun people that were there 20:15:17 jbk: Sorry, redmine has been sluggish. There's a shady web crawler probably related to the TikTok family of companies that is pretending to be an old Android phone. I've just blocked its user agent string. Let me know if it gets sluggish again. 20:19:02 jbk: I remember hearing a talk by Bryan Cantrill that said that it was from Jeff Bonwick. 20:24:45 you definitely appreciate it when you're coming in basically blind to an issue 20:24:59 or are wanting to understand why a change was done 20:26:00 jbk: I appreciated it not that long ago when some dead code made no sense to me. I simply looked up the original rationale for the change and then I realized that the intention had been to make a warning appear less often, but by putting an assignment in the wrong case statement, the patch made it dead code entirely. 20:26:56 It was this: https://github.com/openzfs/zfs/commit/dee8934e8fcd002eb826cf29aa453632d634b826 20:27:31 That was 5 months ago... it still feels like yesterday for some reason. :/