kib style feedback
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Thu, May 30
Wed, May 29
kib feedback on style and __result_use_check
kib feedback on KASSERT style, and fix a comment typo
Tue, May 28
Mon, May 27
Sun, May 26
What about arc_available_memory() in sys/contrib/openzfs/module/os/freebsd/zfs/arc_os.c? Isn't that still broken?
In D45360#1034889, @kib wrote:LK_NOWAIT is the common pattern for this situation. Besides buffers, another immediate example is the vm_map lock in vmspace_fork() (look for the new_map locking and comment).
Sat, May 25
Fri, May 24
Wed, May 22
alc feedback: const and style fixups
markj feedback: elaborate on comment and provide vm_batchqueue_empty()
Implement markj's suggestion
Tue, May 21
In D45287#1033196, @jhibbits wrote:The only time this makes a difference is if the sizes of bus_addr_t and bus_size_t are different, and I don't have any test hardware where that's the case and I can test TPM. (Only hardware I have where that's the case is ppc Book-E, but that doesn't have a TPM).
Mon, May 20
- getblk: fail faster with GB_LOCK_NOWAIT
- GB_LOCK_NOWAIT markj feedback
In D45245#1032681, @markj wrote:My only comment is that, reading the code, it's not immediately obvious why we give up right away when failing to acquire the buf lock, but not when we successfully acquire the buf lock and discover that the buffer identity has changed.
@glebius I ran into this while running the kern tests. This new test is failing reliably for me, and it looks like in CI too, e.g. this run on April 9:
https://ci.freebsd.org/job/FreeBSD-main-amd64-test/25066/testReport/sys.kern/unix_seqpacket_test/random_eor_and_waitall/
In D45245#1032333, @kib wrote:I think that this is technically correct but unfair. Intent was that failed unlocked buffer lookup should not change the behavior, in particular, allowing the normal lookup quirks to proceed.
Sun, May 19
Oct 12 2022
Jul 18 2022
Jul 7 2022
Jun 14 2022
LGTM. I don't get why we don't send PC and the watch stop reason in the '?' case but it probably doesn't matter and it looks like a faithful refactor.
Mar 8 2022
I don't have an objection to changing the LOG_WARNING to LOG_ERR, but I'm confused about what this actually changes. I looked at man 3 syslog and vsyslog1() to see if we printed to stderr by default for LOG_ERR but I'm not seeing that. So, what does this actually do?
Feb 1 2022
Oct 21 2021
A NULL check seems like a clear improvement over a crash.
Oct 13 2021
Sep 23 2021
Sep 21 2021
Jul 7 2021
Jul 3 2021
In D28762#697585, @arichardson wrote:Seems like this is needed to build stable/13 with GCC. Are you going to MFC this? If not I can cherry-pick it for you.
Apr 15 2021
Will work on a providing a better semaphore first.
Apr 7 2021
Apr 1 2021
In D29542#662307, @mjg wrote:I disagree with the patch.
The current mechanism is crap and should probably be retired, anyone interested in ramping up kernel memory use has plenty of other ways to do it.
Mar 23 2021
LGTM, and I checked $work's tree for other references.
Mar 22 2021
Mar 14 2021
Mar 11 2021
Mar 5 2021
Change looks fine once the i386 hack is restored.
Feb 25 2021
This can be done without introducing another object pointer (nobj) by resetting lobj and following the pattern elsewhere, but I found the approach with nobj to be more readable.