Show last: 20 , 50 , 100 , 250
Next page

Date Files Revision Author Revision Log
2020/02/29 09:21:53 /user/pho/stress2/misc/kinfo3.sh
358458 pho Added a timeout and an error exit to this test.
2020/02/29 09:19:50 /user/pho/stress2/misc/all.sh
358457 pho Update the list of tests with known problems.
2020/02/29 09:18:41 /user/pho/stress2/misc/systrace.sh
/user/pho/stress2/misc/systrace2.sh
358456 pho Added regressions tests for dtrace/systrace.
2020/02/29 03:43:18 /head/share/man/man5/src.conf.5
358455 emaste regen src.conf.5 after r358454, GCC 4.2.1 retirement
2020/02/29 03:25:51 /head/Makefile.inc1
/head/ObsoleteFiles.inc
/head/UPDATING
/head/etc/mtree/BSD.include.dist
/head/gnu/lib/Makefile
/head/gnu/lib/libgcov
/head/gnu/lib/libgomp
/head/gnu/lib/libstdc++
/head/gnu/lib/libsupc++
/head/gnu/usr.bin/Makefile
[and more paths]
358454 emaste remove GCC 4.2.1 build infrastructure

As described in Warner's email message[1] to the FreeBSD-arch mailing
list we have reached GCC 4.2.1's retirement date. At this time all
supported architectures either use in-tree Clang, or rely on external
toolchain (i.e., a contemporary GCC version from ports).

GCC 4.2.1 was released July 18, 2007 and was imported into FreeBSD later
that year, in r171825. GCC has served us well, but version 4.2.1 is
obsolete and not used by default on any architecture in FreeBSD. It
does not support modern C and does not support arm64 or RISC-V.

Thanks to everyone responsible for maintaining, updating, and testing
GCC in the FreeBSD base system over the years.

So long, and thanks for all the fish.

[1] https://lists.freebsd.org/pipermail/freebsd-arch/2020-January/019823.html

PR: 228919
Reviewed by: brooks, imp
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D23124
2020/02/28 22:00:50 /stable/11
/stable/11/sys/dev/usb/input/ukbd.c
358453 hselasky MFC r358310:
Use hid_get_data_unsigned() instead of hid_get_data() when reading the
key-codes from the USB keyboard. Negative key-codes are currently skipped.

While at it use the bit size value provided by the HID location structure
instead of assuming a value of 8.

This fixes a regression issue after r357861.

Reported by: Minoru TANABE <kotanabe3@gmail.com>
PR: 224592
PR: 233884
Sponsored by: Mellanox Technologies
2020/02/28 22:00:01 /stable/12
/stable/12/sys/dev/usb/input/ukbd.c
358452 hselasky MFC r358310:
Use hid_get_data_unsigned() instead of hid_get_data() when reading the
key-codes from the USB keyboard. Negative key-codes are currently skipped.

While at it use the bit size value provided by the HID location structure
instead of assuming a value of 8.

This fixes a regression issue after r357861.

Reported by: Minoru TANABE <kotanabe3@gmail.com>
PR: 224592
PR: 233884
Sponsored by: Mellanox Technologies
2020/02/28 21:42:48 /head/sys/kern/kern_sendfile.c
/head/sys/kern/vfs_bio.c
/head/sys/vm/vm_page.c
/head/sys/vm/vm_page.h
358451 jeff Provide a lock free alternative to resolve bogus pages. This is not likely
to be much of a perf win, just a nice code simplification.

Reviewed by: markj, kib
Differential Revision: https://reviews.freebsd.org/D23866
2020/02/28 21:31:40 /head/sys/dev/mmc/host/dwmmc.c
358450 manu mmc: dwmmc: Fix off by one error

The IVAR_MAX_DATA is supposed to have the number of descriptor X the mmc
block size and desc_count contain all this information + 1.

Reported by: phk
MFC after: 1 week
2020/02/28 21:13:15 /head/sys/sys/sysctl.h
358449 brooks Define SCTL_MASK32 when COMPAT_FREEBSD32 is defined.

Remove the list of architectures and depend on COMPAT_FREEBSD32 which is
defined (if relevent) in opt_global.h and thus defined everywhere in
the kernel.

This is a minor change in behavior in that 32-bit compat for sysctls now
depends on COMPAT_FREEBSD32 rather than on the potential for 32-bit
compat support. The prior arrangement may have been part of an attempt
to allow 32-bit compat to be loadable, but such attempts are doomed to
failure (due to the fact that ioctls have no meaning without the
associated file descriptor) without vastly more refactoring and some
sort of COMPAT_FREEBSD32_SUPPORT option.

Reviewed by: jhb
Sponsored by: DARPA
Differential Revision: https://reviews.freebsd.org/D23748
2020/02/28 20:43:35 /head/usr.sbin/services_mkdb/services
358448 pfg /etc/services: attempt to bring the database to this century 1/2.

This is the result of splitting r358153 in two, in order to avoid a build
system bug and being able to merge the change to previous releases..

Document better this file, updating the URL to the IANA registry and closely
match the official services.

For system ports (0 to 1023) we now try to follow the registry closely, noting
some historical differences where applicable.

As a side effect: drop references to unofficial Kerberos IV which was EOL'ed
on Oct 2006[1]. While it is conceivable some people may still use it in some
very old FreeBSD machines that can't be replaced easily, the use of it is
considered a security risk. Also drop the unofficial netatalk, which we
supported long ago in the kernel but was dropped long ago.

Leave for now smtps, even though it conflicts with IANA's submissions.
The change should have very little visibility, if any, but should be a
step closer to the current IANA database.

[1] https://web.mit.edu/kerberos/krb4-end-of-life.html

MFC after: 2 weeks
2020/02/28 20:34:30 /head/sys/dev/drm2/ttm/ttm_tt.c
/head/sys/dev/md/md.c
/head/sys/kern/kern_exec.c
/head/sys/kern/kern_sendfile.c
/head/sys/kern/vfs_bio.c
/head/sys/vm/vm_glue.c
358447 jeff Convert a few triviail consumers to the new unlocked grab API.

Reviewed by: kib, markj
Differential Revision: https://reviews.freebsd.org/D23847
2020/02/28 20:33:28 /head/sys/kern/uipc_shm.c
358446 jeff Use unlocked grab for uipc_shm/tmpfs.

Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D23865
2020/02/28 20:32:35 /head/sys/vm/vm_page.c
358445 jeff Support the NOCREAT flag for grab_valid_unlocked.

Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D23865
2020/02/28 20:30:53 /head/sys/vm/vm_object.c
358444 jeff Simplify vref() code in object_reference. The local temporary is no longer
necessary. Fix formatting errors.

Reported by: mjg
Discussed with: kib
2020/02/28 20:29:53 /head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c
/head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c
358443 jeff Eliminate object locking in zfs where possible with the new lockless grab
APIs.

Reviewed by: kib, markj, mmacy
Differential Revision: https://reviews.freebsd.org/D23848
2020/02/28 18:35:36 /stable/11
/stable/11/stand/common/interp_lua.c
/stable/12
/stable/12/stand/common/interp_lua.c
358442 kevans MFC r357828: interp_lua: fix bogus indentation, NFC
2020/02/28 18:34:17 /stable/11
/stable/11/usr.sbin/certctl/certctl.sh
/stable/12
/stable/12/usr.sbin/certctl/certctl.sh
358441 kevans MFC r358091: certctl(8): switch to install(1) to fix DESTDIR support

"Oops" - ln(1) is fine and dandy, but when you're using DESTDIR...it's not-
the path will almost certainly be invalid once the root you've just
installed to is relocated, perhaps to /.

Switch to install(1) using `-l rs` to calculate the relative symlink between
the two, which should work just fine in all cases.
2020/02/28 18:32:40 /head/sys/amd64/amd64/pmap.c
358440 rlibby amd64 pmap.c: minor codegen optimization in flag access

Following previous revision, apply the same minor optimization to
hand-rolled atomic_fcmpset_128 in pmap.c.

Reviewed by: kib, markj
Sponsored by: Dell EMC Isilon
Differential Revision: https://reviews.freebsd.org/D23870
2020/02/28 18:32:36 /head/sys/amd64/include/atomic.h
358439 rlibby amd64 atomic.h: minor codegen optimization in flag access

Previously the pattern to extract status flags from inline assembly
blocks was to use setcc in the block to write the flag to a register.
This was suboptimal in a few ways:
- It would lead to code like: sete %cl; test %cl; jne, i.e. a flag
would just be loaded into a register and then reloaded to a flag.
- The setcc would force the block to use an additional register.
- If the client code didn't care for the flag value then the setcc
would be entirely pointless but could not be eliminated by the
optimizer.

A more modern inline asm construct (since gcc 6 and clang 9) allows for
"flag output operands", where a C variable can be written directly from
a flag. The optimizer can then use this to produce direct code where
the flag does not take a trip through a register.

In practice this makes each affected operation sequence shorter by five
bytes of instructions. It's unlikely this has a measurable performance
impact.

Reviewed by: kib, markj, mjg
Sponsored by: Dell EMC Isilon
Differential Revision: https://reviews.freebsd.org/D23869