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.
999546e1 | zeising | June 17, 2019, 4:54 p.m. | pci.4: wordsmith and add missing words
Add missing words after PCI in the description of the PCIOCWRITE and PCIOCATTACHED ioctls. Use singular in PCIOCREAD, we only read one register at the time. Reviewed by: bcr, bjk, rgrimes, cem MFC after: 2 weeks X-MFC-with: r349133 Differential Revision: https://reviews.freebsd.org/D20671cgit ViewVC |
|
060e6388 | ian | June 17, 2019, 4:50 p.m. | Put periods at the ends of argument descriptions. Explain the relationship | |
7d763870 | ian | June 17, 2019, 4:43 p.m. | Follow changes in the pwmc(4) driver in relation to device filenames.
The driver now names its cdev nodes pwmcX.Y where X is unit number and Y is the channel within that unit. Change the default device name from pwmc0 to pwmc0.0. The driver now puts cdev files and label aliases in the /dev/pwm directory, so allow the user to provide unqualified names with -f and automatically prepend the /dev/pwm part for them. Update the examples in the manpage to show the new device name format and location within /dev/pwm.cgit ViewVC |
|
b5d67730 | ian | June 17, 2019, 4:26 p.m. | Put the pwmc cdev filenames under the pwm directory along with any label | |
d0d71d81 | cem | June 17, 2019, 3:09 p.m. | random(4): Generalize algorithm-independent APIs
At a basic level, remove assumptions about the underlying algorithm (such as output block size and reseeding requirements) from the algorithm-independent logic in randomdev.c. Chacha20 does not have many of the restrictions that AES-ICM does as a PRF (Pseudo-Random Function), because it has a cipher block size of 512 bits. The motivation is that by generalizing the API, Chacha is not penalized by the limitations of AES. In READ_RANDOM_UIO, first attempt to NOWAIT allocate a large enough buffer for the entire user request, or the maximal input we'll accept between signal checking, whichever is smaller. The idea is that the implementation of any randomdev algorithm is then free to divide up large requests in whatever fashion it sees fit. As part of this, two responsibilities from the "algorithm-generic" randomdev code are pushed down into the Fortuna ra_read implementation (and any other future or out-of-tree ra_read implementations): 1. If an algorithm needs to rekey every N bytes, it is responsible for handling that in ra_read(). (I.e., Fortuna's 1MB rekey interval for AES block generation.) 2. If an algorithm uses a block cipher that doesn't tolerate partial-block requests (again, e.g., AES), it is also responsible for handling that in ra_read(). Several APIs are changed from u_int buffer length to the more canonical size_t. Several APIs are changed from taking a blockcount to a bytecount, to permit PRFs like Chacha20 to directly generate quantities of output that are not multiples of RANDOM_BLOCKSIZE (AES block size). The Fortuna algorithm is changed to NOT rekey every 1MiB when in Chacha20 mode (kern.random.use_chacha20_cipher="1"). This is explicitly supported by the math in FS&K ยง9.4 (Ferguson, Schneier, and Kohno; "Cryptography Engineering"), as well as by their conclusion: "If we had a block cipher with a 256-bit [or greater] block size, then the collisions would not have been an issue at all." For now, continue to break up reads into PAGE_SIZE chunks, as they were before. So, no functional change, mostly. Reviewed by: markm Approved by: secteam(delphij) Differential Revision: https://reviews.freebsd.org/D20312cgit ViewVC |
|
403c0413 | cem | June 17, 2019, 2:59 p.m. | random(4): Add regression tests for uint128 implementation, Chacha CTR
Add some basic regression tests to verify behavior of both uint128 implementations at typical boundary conditions, to run on all architectures. Test uint128 increment behavior of Chacha in keystream mode, as used by 'kern.random.use_chacha20_cipher=1' (r344913) to verify assumptions at edge cases. These assumptions are critical to the safety of using Chacha as a PRF in Fortuna (as implemented). (Chacha's use in arc4random is safe regardless of these tests, as it is limited to far less than 4 billion blocks of output in that API.) Reviewed by: markm Approved by: secteam(gordon) Differential Revision: https://reviews.freebsd.org/D20392cgit ViewVC |
|
eadd12d3 | asomers | June 17, 2019, 2:42 p.m. | fusefs: rename the ReadCacheable.default_readahead test | |
7d8ec1b7 | mm | June 17, 2019, 11:46 a.m. | MFV r349134: | |
c31a08f6 | mm | June 17, 2019, 11:29 a.m. | Update vendor/libarchive/dist to git 809f0dc32fff7434aef45a7c688fa285c7208af7 | |
65d328a3 | zeising | June 17, 2019, 5:41 a.m. | pci(4): Document PCIOCATTACHED
Document the PCIOCATTACHED ioctl(2) in the pci(4) manual. PCIOCATTACHED is used to query if a driver has attached to a PCI. Reviewed by: bcr, imp MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D20652cgit ViewVC |
|
2c6c030c | ian | June 17, 2019, 3:48 a.m. | Add back a const qualifier I somehow fumbled away between test-building | |
0a06f11d | ian | June 17, 2019, 3:40 a.m. | Implement the ofw_bus_get_node method in aw_pwm(4) so that ofw_pwmbus can | |
b43e2c8b | ian | June 17, 2019, 3:32 a.m. | Add ofw_pwmbus to enumerate pwmbus devices on systems configured with fdt | |
29c25bd7 | alc | June 17, 2019, 1:58 a.m. | Eliminate a redundant call to pmap_invalidate_page() from
pmap_ts_referenced(). MFC after: 14 days Differential Revision: https://reviews.freebsd.org/D12725cgit ViewVC |
|
c8f59059 | alc | June 16, 2019, 10:13 p.m. | Three changes to arm64's pmap_unwire():
Implement wiring changes on superpage mappings. Previously, a superpage mapping was unconditionally demoted by pmap_unwire(), even if the wiring change applied to the entire superpage mapping. Rewrite a comment to use the arm64 names for bits in a page table entry. Previously, the bits were referred to by their x86 names. Use atomic_"op"_64() instead of atomic_"op"_long() to update a page table entry in order to match the prevailing style in this file. MFC after: 10 dayscgit ViewVC |