- User Since
- Jul 18 2014, 8:51 PM (273 w, 3 d)
Mon, Oct 7
Sun, Oct 6
Sun, Sep 29
Wed, Sep 25
Tue, Sep 17
I am starting to concurr that this call may be obsoleted.
Let me add the kqueue maintainer and the fuse maintainer (Alan added kqueue support to fuse) as they may shed some more light on this
Committed as r350970.
Sep 13 2019
I was busy in the hospital (visiting not as patient) and didn't get the chance to approve it ... Huge thanks for doing this!
Sep 9 2019
Aug 29 2019
Aug 27 2019
Aug 23 2019
Aug 16 2019
Aug 13 2019
This passes "mandoc -Tlint".
This passes "mandoc -Tlint".
Aug 11 2019
Aug 8 2019
Aug 6 2019
Aug 4 2019
Aug 3 2019
I think the problem in libssp_nonshared.a is brought in bogusly by the
Aug 2 2019
Jul 31 2019
Jul 26 2019
Jul 22 2019
Jul 15 2019
Jul 6 2019
Its an ext4 feature, linux calls it crtime (creation time), just to be different ;).
In general I prefer we support a lower number of the protocol but that we support it well.
Jun 30 2019
Jun 24 2019
I think andreast@ and gerald@ may want to be kept in the loop for the GCC update then :).
Very exciting ... will upstream GCC require changes as well?
Jun 9 2019
Adding fsu@ in case he wants to mention something else :).
Yes, we do fully support ext4 read and write in FreeBSD 12+. We also support Extended Attributes, ACLs, and most features with the exception of journalling and encryption. As mentioned in BSDNow, 12.1 will have a DTrace provider.
Jun 8 2019
Thanks for working on this. For the record,
May 29 2019
May 25 2019
The changes seem correct.
I don't think a simple phabricator acceptance from a committer is suficient approval for a non src committer though, so I hereby explicitly approve it.
May 12 2019
May 8 2019
May 1 2019
Apr 27 2019
This has rusted since the last revision: fts had some changes (mostly just updated prototypes) and glob has been rewritten.
It needs some fresh eyes into it (cc'ing brooks in case he wants to take over).
Most of these don't make sense as they cant overflow, and those that do were committed.
This was committed as r337456.
Is this still a valid review? I recall something related was committed.
Apr 24 2019
Apr 19 2019
Apr 18 2019
Apr 17 2019
Apr 13 2019
Apr 10 2019
I still hope to hear from the DTrace experts, but I like this very much. Thanks!
Apr 8 2019
Very cool (but I am biased since I suggested the fusefs-dtrace changes as a starting point)!
Apr 5 2019
Mar 1 2019
Feb 27 2019
Upon further thought: the situation is very different for ext2fs than to a filesystem in which the all the system depends as in UFS.
OK, you are rught, we were not allocating (with M_ZERO) this before.
We have this as a panic in UFS, as well.
We should probably keep this panic for consistency with UFS, which also panics on this case.
Feb 25 2019
Note why we specifically set ip->i_flags = 0 since r294652:
Feb 24 2019
Feb 22 2019
FWIW, the GPLv3 version does an ugly calloc() dance with pointers which looks a lot more confusing.
I am unsure if it is a style rule but we generally place such pragmas before and after all declarations so that they don't get in the way of easier reading.
Feb 20 2019
Feb 19 2019
(trasz is the expert here)
Feb 15 2019
If it's not needed then just lets not spend time on it.
Note that I have no idea of MIPS asm, just noticed the commit on OpenBSD MIPS64 .. feel free to commit if it works for you.
Feb 12 2019
(Don't expect any failure but will test anyways)