committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r345418||avg||March 22, 2019, 5:44 p.m.||Revert r345410, VOP_FSYNC change in ZFS vdev_file
I overlooked the fact that that VOP_FSYNC() call is not a FreeBSD VFS call, but a macro that provides an illumos-compatible wrapper for the FreeBSD operation. PR: 236475 Reported by: lwhsu Pointyhat to: avgViewVC
|r345417||mhorne||March 22, 2019, 5:37 p.m.||Update mentor and calendar files
Add an entry for myself (mhorne) to these files. Approved by: markjViewVC
|r345412||cy||March 22, 2019, 11:46 a.m.||Use internal command variables for consistent style.
Reported by: rgrimes@ MFC after: 13 days X-MFC with: r345400ViewVC
|r345411||avg||March 22, 2019, 10:38 a.m.||intpm: change translation of HBA error status to smbus(4) errors
PIIX4_SMBHSTSTAT_ERR can be set for several reasons that, unfortunately, cannot be distinguished, but the most typical case is a missing or hung slave (SMB_ENOACK). PIIX4_SMBHSTSTAT_FAIL means failed or killed / aborted transaction, so it's previous mapping to SMB_ENOACK was not ideal. After this change an smb(4) access to a missing slave results in ENXIO rather than EIO. To me, that seems to be more appropriate. MFC after: 3 weeksViewVC
|r345410||avg||March 22, 2019, 9:11 a.m.||ZFS vdev_file: use correct value for waitfor parameter of VOP_FSYNC
PR: 236475 Reported by: asomers MFC after: 2 weeksViewVC
|r345409||kp||March 22, 2019, 7:39 a.m.||pf tests: Test CVE-2019-5598
Verify that pf correctly drops inconsistent ICMP packets (i.e. where the IP src/dst do not match the IP src/dst in the ICMP packet.ViewVC
|r345408||cperciva||March 22, 2019, 6:36 a.m.||Add nvme support to the arm64 GENERIC kernel.|
|r345407||cperciva||March 22, 2019, 6:33 a.m.||Build if_ena.ko on arm64.
This module provides support for the Amazon Elastic Network Adapter; it was previously only built on x86 architectures, but Amazon EC2 now also has ARM64 instances with this hardware. Submitted by: Greg VViewVC
|r345406||cperciva||March 22, 2019, 6:28 a.m.||Initialize uart_bus_space_mem.
This value was being used uninitialized, resulting in predictable issues on systems with memory-mapped UART registers. A case could be made that memmap_bus should be declared in a header rather than being declared in each .c file which needs to refer to it, but that's a broader style question. This commit unbreaks hw.uart.console="mm:..." on ARM64. Submitted by: Greg VViewVC
|r345405||cperciva||March 22, 2019, 6:21 a.m.||Obey SPCR AccessWidth parameter.
The "access width" value was hard-coded as 2, indicating 32-bit accesses; instead, use the value specified in the SPCR table. This unbreaks the console on EC2 "A1" family instances. Submitted by: Greg VViewVC
|r345403||cy||March 22, 2019, 1:43 a.m.||From r345400, remove the ippool rc script when ipfilter is not wanted
by the user. PR: 218433 MFC after: 2 weeks X-MFC with: r345400ViewVC
|r345402||jhibbits||March 22, 2019, 1:43 a.m.||powerpc64: Handle the modern (2.05+) implementaiton of tlbie
By happenstance gcc4 puts 'vpn' into r0 in all uses of TLBIE(), but modern gcc does not. Also, the single-argument form of tlbie zeros all unused arguments, making the modern tlbie instruction use r0 as the RS field (LPID). The vpn argument has the bottom 12 bits cleared (the input having been left-shifted by 12 bits), which just so happens, on the POWER9 and previous incarnations, to be the number of LPID bits supported. With those bits being zero, the instruction: tlbie r0, r0 will invalidate the VPN in r0, in LPAR 0 (ignoring the upper bits of r0 for the RS field). One build with gcc8 yields: tlbie r9, r0 with r0 having arbitrary contents, not equal to r9. This leads to strange crashes, behaviors, and panics, due to the requested TLB entry not actually being invalidated. As the moea64_native must work on both old and new, we explicitly zero out r0 so that it can work with only the single argument, built with base gcc and modern gcc. isa3_hashtb takes a different approach, encoding the two-argument form, soas not to explicitly clobber r0, and instead let the compiler decide. Reported by: Brandon Bergren Tested by: Brandon Bergren MFC after: 1 weekViewVC
|r345401||cy||March 22, 2019, 1:42 a.m.||From r345400, connect ippool to the build/install.
PR: 218433 MFC after: 2 weeks X-MFC with: r345400ViewVC
|r345400||cy||March 22, 2019, 1:30 a.m.||Add rc.d support for ippool(8).
I've been using ippool at my site for approximately two years. It's about time this was committed. PR: 218433 MFC after: 2 weeksViewVC
|r345388||jkim||March 21, 2019, 9:45 p.m.||Catch up with Clang 8.0.|