|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0 |
|
| #
ae8c08e7 |
| 12-Apr-2019 |
Simon J. Gerraty <[email protected]> |
Add support for loader veriexec
Also sbin/veriexec for mac_veriexec
MFC r343281,344564-344568,344780,344784,345289,346070
|
|
Revision tags: release/12.0.0 |
|
| #
5952343e |
| 24-Jul-2018 |
Kyle Evans <[email protected]> |
Rename be(1) to bectl(8); continues to live in /sbin
Discussed with: rpokala, allanjude
|
| #
28f16a0f |
| 24-Jul-2018 |
Kyle Evans <[email protected]> |
Import libbe(3)/be(1) from socsvn/soc2017/kneitinger/libbe-head
|
| #
aa571745 |
| 24-Jun-2018 |
Eitan Adler <[email protected]> |
Makefiles: remove outdated comments
|
|
Revision tags: release/11.2.0 |
|
| #
f0f8a1af |
| 14-Jun-2018 |
Warner Losh <[email protected]> |
NVME support is only for x86 and powerpc64.
Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camco
NVME support is only for x86 and powerpc64.
Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme.
This should fix the newly introduced nvme files to camcontrol which were building everywhere.
Pointy Hat To: imp Sponsored by: Netflix
show more ...
|
| #
590682b6 |
| 12-Feb-2018 |
Warner Losh <[email protected]> |
Move devmatch to sbin from usr/sbin.
Since we want to use devmatch in context before a split /,/usr system has mounted /usr, move devmatch to /sbin.
Sponsored by: Netflix
|
| #
93b09f58 |
| 05-Nov-2017 |
Konstantin Belousov <[email protected]> |
Remove badsect(8).
Failure modes of the modern (that is, produced in the last 25 years) hard drives and SSDs made the utility outdated. Since the kernel interface to support it was removed in r3248
Remove badsect(8).
Failure modes of the modern (that is, produced in the last 25 years) hard drives and SSDs made the utility outdated. Since the kernel interface to support it was removed in r324853, cut the userspace remnants as well.
Discussed with: bde (who does not like the removal) Sponsored by: The FreeBSD Foundation MFC after: 2 weeks
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0 |
|
| #
01df7d10 |
| 06-Jul-2017 |
Enji Cooper <[email protected]> |
Remove SUBDIR ordering/uniquifying in *bin/Makefile
After the addition of SUBDIR.yes, uniquifying/ordering the SUBDIRs doesn't make a whole lot of sense, and it's in effect a half measure.
Ordering
Remove SUBDIR ordering/uniquifying in *bin/Makefile
After the addition of SUBDIR.yes, uniquifying/ordering the SUBDIRs doesn't make a whole lot of sense, and it's in effect a half measure.
Ordering SUBDIR (after adding SUBDIR.yes to it) in bsd.subdir.mk is a separate change that warrants more discussion/testing, because while the SUBDIR_PARALLEL work largely fixed dependency ordering for SUBDIRs, there might be downstream FreeBSD consumers that rely on the SUBDIR ordering.
MFC after: 2 months Reviewed by: bdrewery Differential Revision: D11398
show more ...
|
| #
a7dc3128 |
| 24-Apr-2017 |
Brooks Davis <[email protected]> |
Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the cas
Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
show more ...
|
| #
480f31c2 |
| 10-Dec-2016 |
Konrad Witaszczyk <[email protected]> |
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDU
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump configuration in the diocskerneldump_arg structure to the kernel. The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using an RSA public key in capability mode. Currently only AES-256-CBC is supported but EKCD was designed to implement support for other algorithms in the future. The public key is chosen using the -k flag. The dumpon rc(8) script can do this automatically during startup using the dumppubkey rc.conf(5) variable. Once the keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random IV and sets up the key schedule for the specified algorithm. Each time the kernel tries to write a crash dump to the dump device, the IV is replaced by a SHA-256 hash of the previous value. This is intended to make a possible differential cryptanalysis harder since it is possible to write multiple crash dumps without reboot by repeating the following commands: # sysctl debug.kdb.enter=1 db> call doadump(0) db> continue # savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted symmetric key. The kernel dump key size is included in a kernel dump header. The size is an unsigned 32-bit integer and it is aligned to a block size. The header structure has 512 bytes to match the block size so it was required to make a panic string 4 bytes shorter to add a new field to the header structure. If the kernel dump key size in the header is nonzero it is assumed that the kernel dump key is placed after the first header on the dump device and the core dump is encrypted.
Separate functions were implemented to write the kernel dump header and the kernel dump key as they need to be unencrypted. The dump_write function encrypts data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps are not supported due to the way they are constructed which makes it impossible to use the CBC mode for encryption. It should be also noted that textdumps don't contain sensitive data by design as a user decides what information should be dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel dump key. This is performed by a child process in capability mode. If the decryption was not successful the parent process removes a partially decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8), dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU. The feature still has to be tested on arm and arm64 as it wasn't possible to run FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd Reviewed by: cem, oshogbo, pjd Partial review: delphij, emaste, jhb, kib Approved by: pjd (mentor) Differential Revision: https://reviews.freebsd.org/D4712
show more ...
|
| #
97371ba2 |
| 29-Oct-2016 |
Andriy Gapon <[email protected]> |
zfsbootcfg: a simple tool to set next boot (one time) options for zfsboot
(gpt)zfsboot will read one-time boot directives from a special ZFS pool area. The area was previously described as "Boot Bl
zfsbootcfg: a simple tool to set next boot (one time) options for zfsboot
(gpt)zfsboot will read one-time boot directives from a special ZFS pool area. The area was previously described as "Boot Block Header", but currently it is know as Pad2, marked as reserved and is zeroed out on pool creation. The new code interprets data in this area, if any, using the same format as boot.config. The area is immediately wiped out. Failure to parse the directives results in a reboot right after the cleanup. Otherwise the boot sequence proceeds as usual.
zfsbootcfg writes zfsboot arguments specified on its command line to the Pad2 area of a disk identified by vfs.zfs.boot.primary_pool and vfs.zfs.boot.primary_vdev kenv variables that are set by loader during boot. Please see the manual page for more.
Thanks to all who reviewed, contributed and made suggestions! There are many potential improvements to the feature, please see the review for details.
Reviewed by: wblock (docs) Discussed with: jhb, tsoome MFC after: 3 weeks Relnotes: yes Differential Revision: https://reviews.freebsd.org/D7612
show more ...
|
|
Revision tags: release/11.0.1, release/11.0.0 |
|
| #
014db25b |
| 12-Aug-2016 |
Enji Cooper <[email protected]> |
Update ^/vendor/NetBSD/tests/dist to a more recent snapshot
Pulled on "Thu Aug 11 18:01:19 PDT 2016"
|
|
Revision tags: release/10.3.0 |
|
| #
c501d73c |
| 25-Feb-2016 |
Mariusz Zaborski <[email protected]> |
Convert casperd(8) daemon to the libcasper. After calling the cap_init(3) function Casper will fork from it's original process, using pdfork(2). Forking from a process has a lot of advantages: 1. We
Convert casperd(8) daemon to the libcasper. After calling the cap_init(3) function Casper will fork from it's original process, using pdfork(2). Forking from a process has a lot of advantages: 1. We have the same cwd as the original process. 2. The same uid, gid and groups. 3. The same MAC labels. 4. The same descriptor table. 5. The same routing table. 6. The same umask. 7. The same cpuset(1). From now services are also in form of libraries. We also removed libcapsicum at all and converts existing program using Casper to new architecture.
Discussed with: pjd, jonathan, ed, [email protected], emaste Partially reviewed by: [email protected], bdrewery Approved by: pjd (mentor) Differential Revision: https://reviews.freebsd.org/D4277
show more ...
|
| #
6f42d16f |
| 18-Nov-2015 |
Bryan Drewery <[email protected]> |
Convert to SUBDIR.yes format.
Reviewed by: imp Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D4182
|
|
Revision tags: release/10.2.0 |
|
| #
87d352d5 |
| 02-Feb-2015 |
Enji Cooper <[email protected]> |
Remove duplicate MK_ISCSI block and sort the conditional blocks so this error won't crop up again in the future
Reported by: gjb MFC after: 1 week
|
| #
c01f300b |
| 26-Jan-2015 |
Enji Cooper <[email protected]> |
Build sbin/iscontrol again if MK_ISCSI != no
MFC after: 13 days X-MFC with: r277675 Pointyhat to: me
|
| #
4e395054 |
| 26-Jan-2015 |
Enji Cooper <[email protected]> |
Add MK_HAST knob for building and installing hastd(8), et al
MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
|
| #
18cc3172 |
| 25-Jan-2015 |
Enji Cooper <[email protected]> |
Add MK_CCD knob for building and installing ccd(4), ccdconfig, etc
MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
|
| #
b29d6977 |
| 25-Jan-2015 |
Enji Cooper <[email protected]> |
Add MK_ISCSI knob for building the iscsi initiator, iscsi daemon, kernel modules, etc
MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
|
| #
21060720 |
| 02-Dec-2014 |
Enji Cooper <[email protected]> |
Make ccd(4), et al conditional based on MK_CCD
|
| #
317fdbc6 |
| 30-Nov-2014 |
Enji Cooper <[email protected]> |
Build spppcontrol if MK_PPP != no
|
| #
466046ec |
| 26-Nov-2014 |
Enji Cooper <[email protected]> |
Conditionalize a number of components in the tree
- bootparamd - bootpd - finger/fingerd - ftp/ftpd - hastctl/hastd - iscsid, et al - rbootd - talk/talkd - tcpd, et al - tftp/tftpd
Add src.conf ent
Conditionalize a number of components in the tree
- bootparamd - bootpd - finger/fingerd - ftp/ftpd - hastctl/hastd - iscsid, et al - rbootd - talk/talkd - tcpd, et al - tftp/tftpd
Add src.conf entries for the various components and do a best effort at adding components to tools/build/mk/OptionalObsoleteFiles.inc
show more ...
|
|
Revision tags: release/10.1.0 |
|
| #
478290db |
| 01-Oct-2014 |
Enji Cooper <[email protected]> |
Check in first src/tests snapshot from NetBSD anoncvs
Sources were obtained like so:
% export CVSROOT="[email protected]:/cvsroot" % cvs -z9 co -D "09/30/2014 20:45" -P src/tests % mv src/
Check in first src/tests snapshot from NetBSD anoncvs
Sources were obtained like so:
% export CVSROOT="[email protected]:/cvsroot" % cvs -z9 co -D "09/30/2014 20:45" -P src/tests % mv src/tests/* tests/dist/.
'*CVS*' has been added to svn:ignore to ease updating periodically from upstream
Some line ending issues had to be resolved with test outputs and scripts via dos2unix and by deleting the eol-style property set in usr.bin/sort
Discussed with: rpaulo Sponsored by: EMC / Isilon Storage Division
show more ...
|
|
Revision tags: release/9.3.0 |
|
| #
c6063d0d |
| 06-May-2014 |
Warner Losh <[email protected]> |
Use src.opts.mk in preference to bsd.own.mk except where we need stuff from the latter.
|
| #
54ff5d73 |
| 26-Mar-2014 |
Dimitry Andric <[email protected]> |
Add a SUBDIR_PARALLEL option to bsd.subdir.mk, to allow make to process all the SUBDIR entries in parallel, instead of serially. Apply this option to a selected number of Makefiles, which can greatl
Add a SUBDIR_PARALLEL option to bsd.subdir.mk, to allow make to process all the SUBDIR entries in parallel, instead of serially. Apply this option to a selected number of Makefiles, which can greatly speed up the build on multi-core machines, when using make -j.
This can be extended to more Makefiles later on, whenever they are verified to work correctly with parallel building.
I tested this on a 24-core machine, with make -j48 buildworld (N = 6):
before stddev after stddev ======= ====== ======= ====== real time 1741.1 16.5 959.8 2.7 user time 12468.7 16.4 14393.0 16.8 sys time 1825.0 54.8 2110.6 22.8
(user+sys)/real 8.2 17.1
E.g. the build was approximately 45% faster in real time. On machines with less cores, or with lower -j settings, the speedup will not be as impressive. But at least you can now almost max out a machine with buildworld!
Submitted by: jilles MFC after: 2 weeks
show more ...
|