| created | 2019-06-01T11:05:05Z |
|---|---|
| begin | 2019-05-30T00:00:00Z |
| end | 2019-05-31T00:00:00Z |
| path | src/sys |
| commits | 8 |
| date | 2019-05-30T03:56:26Z | |||
|---|---|---|---|---|
| author | jmatthew | |||
| files | src/sys/dev/pci/if_mcx.c | log | diff | annotate |
| message | wrap some long lines, except in bits I'll probably have to rewrite soon | |||
| date | 2019-05-30T05:55:10Z | |||
|---|---|---|---|---|
| author | jmatthew | |||
| files | src/sys/dev/pci/if_mcx.c | log | diff | annotate |
| message |
Mellanox support tells me that according to an internal datasheet, legacy interrupts are not supported, leaving us with just MSI-X for mcx(4). |
|||
| date | 2019-05-30T12:58:20Z | |||
|---|---|---|---|---|
| author | beck | |||
| files | src/sys/kern/vfs_syscalls.c | log | diff | annotate |
| message |
Correct call to vfs_getcwd_common from within __realpath I borrowed an example usage from __getcwd poorly to begin with and then there was some other strangeness in there. diagnosed with deraadt. ok deraadt@ |
|||
| date | 2019-05-30T13:10:23Z | |||
|---|---|---|---|---|
| author | deraadt | |||
| files | src/sys/kern/vfs_getcwd.c | log | diff | annotate |
| message | use copyoutstr, instead of fragile range math; ok beck | |||
| date | 2019-05-30T13:11:53Z | |||
|---|---|---|---|---|
| author | deraadt | |||
| files | src/sys/kern/vfs_getcwd.c | log | diff | annotate |
| src/sys/kern/vfs_syscalls.c | log | diff | annotate | |
| message |
namei() generate KTR_NAMEI record input filenames, but getcwd(2) and realpath(2) have output filenames. Generate additional KTR_NAMEI records upon success. ok millert beck |
|||
| date | 2019-05-30T13:34:54Z | |||
|---|---|---|---|---|
| author | beck | |||
| files | src/sys/kern/vfs_getcwd.c | log | diff | annotate |
| message |
Fix the initialization of bp before calling vfs_getcwd_common It is bad style to make a pointer point outside the object so correct this to simply point to the last byte up front. ok deraadt@ |
|||
| date | 2019-05-30T21:44:21Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/dev/pci/pcireg.h | log | diff | annotate |
| message |
Fix definitions of PCI_MSIX_MAU32 and add a define for the MSI-X function mask bit. ok mlarkin@, jmatthew@ |
|||
| date | 2019-05-30T22:03:14Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/arch/amd64/pci/pci_machdep.c | log | diff | annotate |
| message |
Use two 32-bit writes instead of a single 64-bit write to write the message address into an MSI-X table entry. The RTL8168/RTL8111 hardware does not respond to 64-bit access (reads return all-ones, writes are ignored) and the PCI specification documents separate 32-bit "DWORD" fields for message address and message upper address. ok mlarkin@, jmatthew@ |
|||