User Details
- User Since
- Dec 9 2017, 2:51 PM (351 w, 9 h)
Jun 25 2024
Jun 19 2024
Jun 14 2024
May 30 2024
May 27 2024
May 25 2024
May 21 2024
Jan 21 2024
Dec 7 2023
Playing with this again, a lot better now!
Oct 13 2023
Ah no, the cache_enter_time thing seems to be unrelated. Maybe it was bad luck that I got it very quickly after porting the patches just doing some ls commands; with pkg fetching packages it has happened both with the patches as they are and without them at all; i.e. no matter what. Not sure what can be done, my attempts to "fix" it (with my nonexistent vfs knowledge) seem to only introduce new panics.
Interesting!! The excl->share thing I was getting seems to happen when I mount /home, but not when I mount /home/val only. (On the host /home/val is a mounted ZFS dataset if that matters… well /home is a dataset too but only has the mountpoint dir.)
Oct 12 2023
Just logging in to a home directory shared with the Linux host, there's a lock order issue:
Sep 23 2023
Aug 24 2023
Thanks @trasz, I'll experiment with building on top of fchroot. I'll post new proposals as separate revisions and leave this closed as-is for historical reference :)
ping!
Aug 2 2023
Jul 27 2023
WITHOUT_CLEAN builds should benefit as well then.. (Not sure why people still use it when META_MODE exists but okay :D)
Well, you wouldn't really save any time on a non-incremental build as all the libraries would be rebuilt anyway. The *problem* this solves is specific to META_MODE :)
May 8 2023
May 7 2023
May 5 2023
Apr 28 2023
Apr 20 2023
Hey, couple random notes:
Apr 15 2023
Yeah, I guess it would make sense to only report "exiting" when not yet exited.
BTW, is the only difference between P_WEXIT and zombie state is that P_WEXIT gets set earlier in the process?
Apr 13 2023
Mar 30 2023
Yeah, I solved the same problem in drm initially by writing a dummy driver too, but now it's been replaced by FB_FLAG_NOWRITE.
This is how we're doing it, it's a bit annoying that we have to check the driver and reach into its softc, ideally flags like that would be a more outer-level thing somehow (?)
Mar 27 2023
Found some interesting discussion from almost a decade ago: https://lists.freebsd.org/pipermail/freebsd-arch/2013-August/014707.html confirming that MONOTONIC should include suspended time:
Mar 26 2023
Oh, what's also pretty neat about the "MONOTONIC includes suspend like OpenBSD" choice is that software doing some security timeouts like sudo does would default to the secure behavior (not prolonging timeouts across suspends) even without doing anything for suspend-awareness / while being just POSIX without any OS-specific code!! :)
Mar 25 2023
Mar 2 2023
Feb 22 2023
Oops… cr_cansee actually would only deny this with security.bsd.see_other_uids=0 btw. Is there a "fs write" style check anywhere in the common code?
Feb 20 2023
Though, hm, various AT_RESOLVE_BENEATH documentation does collapse it all into one item:
Yeah, makes sense, let's try like this
Feb 19 2023
Hopefully more clear this way?
Feb 12 2023
Feb 10 2023
Wait wait wait… if we decided not to put gettime/settime here, to keep it as an interface only for creating various kinds of descriptors, why are we still going to duplicate the falloc_noinstall/finstall/fdrop dance across the individual functions for each descriptor kind?
Feb 9 2023
just implement these to as syscalls leaving __specialfd for descriptor creation
sure, D38445 LGTM
Feb 7 2023
ok, let's go with D38392
Feb 6 2023
Remove $FreeBSD$ tags, add header include to the .c file to fix missing-prototype
btw, what toggles the error is --(no-)undefined-version, no became the default. It seems difficult to make *everything* work with --no-undefined-version, but this was the only thing in the kernel.
Rebase after D38222
Yes, it has failed. I wouldn't be that bothered with a little warning :)
Feb 5 2023
Rebased. Ping!
rebased / author name changed / etc. (dang it's been a year)
rebased (bye bye MIPS \o/). ping!
rebased patch, no functional changes. ping!
rebased patch, no changes