committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|2b0cabbd||delphij||Aug. 8, 2019, 6:27 a.m.||Update geom_uzip to use new zlib:
- Use new zlib headers; - Removed z_alloc and z_free to use the common sys/dev/zlib version. - Replace z_compressBound with compressBound from zlib. While there, limit LZMA CFLAGS to apply only for g_uzip_lzma.c. PR: 229763 Submitted by: Yoshihiro Ota <ota j email ne jp> (with changes, bugs are mine) Differential Revision: https://reviews.freebsd.org/D20271cgit ViewVC
|56e66ce8||alc||Aug. 8, 2019, 6:26 a.m.||Ordinarily, during a superpage promotion or demotion within a pmap, the
pmap's lock ensures that other operations on the pmap don't observe the old mapping being broken before the new mapping is established. However, pmap_kextract() doesn't acquire the kernel pmap's lock, so it may observe the broken mapping. And, if it does, it returns an incorrect result. This revision implements a lock-free solution to this problem in pmap_update_entry() and pmap_kextract() because pmap_kextract() can't acquire the kernel pmap's lock. Reported by: andrew, greg_unrelenting.technology Reviewed by: andrew, markj Tested by: greg_unrelenting.technology X-MFC with: r350579 Differential Revision: https://reviews.freebsd.org/D21169cgit ViewVC
|47fec6f3||cem||Aug. 8, 2019, 4:29 a.m.||r350739 try #2|
|be3ab187||cem||Aug. 8, 2019, 3:27 a.m.||Disable useless -Wformat-zero-length|
|937e8f20||jhibbits||Aug. 8, 2019, 3:18 a.m.||powerpc/pmap: Minor optimizations to 64-bit booke pmap|
|ca05fff0||jhibbits||Aug. 8, 2019, 3:16 a.m.||Change autounmountd(8) to use time_t for duration instead of double
Summary: autounmountd(8) uses doubles to handle mount time durations. However, it must convert to integer types, time_t in particular, to do anything meaningful. Additionally, even though it's a floating-point value in seconds, the sub-seconds component is never used, so it's unnecessary. Switching type to time_t fixes an assertion on powerpc64, which checks that a sleep value that's not -1.0 is greater than 0. On powerpc64, it happens that the value of -1.0 gets loaded as a float (perhaps a bug in gcc), but gets compared to a double. This compares as false, so follows through the 'sleep != -1.0' path, and fails the assert. Since the sub-second component isn't used in the double, just drop it and deal with whole-integer seconds. Reviewed by: trasz Differential Revision: https://reviews.freebsd.org/D21109cgit ViewVC
|7d0658ad||cem||Aug. 8, 2019, 1:37 a.m.||Fix !DDB kernel configurations after r350713|
|26a6feda||lwhsu||Aug. 8, 2019, 12:51 a.m.||Follow r350693 to add a link for sbuf_nl_terminate(9)|
|088c17b4||cem||Aug. 8, 2019, 12:42 a.m.||ddb(4): Add 'sysctl' command
Implement `sysctl` in `ddb` by overriding `SYSCTL_OUT`. When handling the req, we install custom ddb in/out handlers. The out handler prints straight to the debugger, while the in handler ignores all input. This is intended to allow us to print just about any sysctl. There is a known issue when used from ddb(4) entered via 'sysctl debug.kdb.enter=1'. The DDB mode does not quite prevent all lock interactions, and it is possible for the recursive Giant lock to be unlocked when the ddb(4) 'sysctl' command is used. This may result in a panic on return from ddb(4) via 'c' (continue). Obviously, this is not a problem when debugging already-paniced systems. Submitted by: Travis Lane (formerly: <travis.lane AT isilon.com>) Reviewed by: vangyzen (earlier version), Don Morris <dgmorris AT earthlink.net> Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D20219cgit ViewVC
|09b238e7||avg||Aug. 7, 2019, 9:20 p.m.||rc.8: fix a typo in r350701|
|ce6c81b9||avg||Aug. 7, 2019, 9:07 p.m.||rc.8: add a reference to service(8)|
|84922a5d||lwhsu||Aug. 7, 2019, 9:02 p.m.||Get configuration variable with default value for not breaking default setting|
|0bf48626||asomers||Aug. 7, 2019, 8:28 p.m.||Remove the fuse.ko -> fusefs.ko symlink
On FreeBSD 13.0, the fuse driver will always be known as fusefs. The backwards compatibility symlink will still be used for stable/12 and stable/11, though. Reported by: jhibbits Reviewed by: rgrimes, imp, cem MFC after: Never Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D21181cgit ViewVC
|aa8d1268||dim||Aug. 7, 2019, 8:13 p.m.||Fix a possible segfault in wcsxfrm(3) and wcsxfrm_l(3).
If the length of the source wide character string, passed in via the "size_t n" parameter, is set to zero, the function should only return the required length for the destination wide character string. In this case, it should *not* attempt to write to the destination, so the "dst" parameter is permitted to be NULL. However, when the internally called _collate_wxfrm() function returns an error, such as when using the "C" locale, as a fallback wcscpy(3) or wcsncpy(3) are used. But if the input length is zero, wcsncpy(3) will be called with a length of -1! If the "dst" parameter is NULL, this will immediately result in a segfault, or if "dst" is a valid pointer, it will most likely result in unexpectedly overwritten memory. Fix this by explicitly checking for an input length greater than zero, before calling wcsncpy(3). Note that a similar situation does not occur in strxfrm(3), the plain character version of this function, as it uses strlcpy(3) for the error case. The strlcpy(3) function does not write to the destination if the input length is zero. MFC after: 1 weekcgit ViewVC
|13a7c4d4||markj||Aug. 7, 2019, 7:45 p.m.||Use designated initializers for vmm_ops.|