| created | 2019-08-12T15:27:07Z |
|---|---|
| begin | 2019-08-05T00:00:00Z |
| end | 2019-08-06T00:00:00Z |
| path | src/sys |
| commits | 9 |
| date | 2019-08-05T01:55:38Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/net/if_tpmr.c | log | diff | annotate |
| message |
pay some lip service to TPMR compliance according to 802.1Q-2018 the spec says we should filter packets destined to a list of ethernet addresses. im currently interpreting "filter" as meaning dropping, which this diff does. however, one of the addresses to filter is the one lacp uses by default and not a lot of lacp implementations (read switches) support the configuration of a different address. i still need lacp to go over tpmr, and because i can't change the address, this diff also has a way to configure tpmr to still allow the packets through. |
|||
| date | 2019-08-05T03:56:31Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/net/if_tpmr.c | log | diff | annotate |
| message |
run pf against ip packets coming in and out of the two ports. the idea and a good chunk of the implementation is copied from bridge(4). note that IP packets inside "service delimited" traffic, ie, vlan, svlan, or bpe encapsulated traffic, are not considered IP and will therefore not be given to pf to look at. if you want to filter that you'll need to configure vlan/svlan/bpe interfaces to get past their headers, and then configure them with their own tpmrs. hopefully the interface input handlers were established in the right order. |
|||
| date | 2019-08-05T08:33:38Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/dev/pci/files.pci | log | diff | annotate |
| message |
sis(4) calls mii_phy_reset(); add explicit dependency on mii_phy in config from grunk@ |
|||
| date | 2019-08-05T08:35:59Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/dev/pci/drm/drm_linux.c | log | diff | annotate |
| src/sys/isofs/cd9660/cd9660_vnops.c | log | diff | annotate | |
| src/sys/kern/kern_descrip.c | log | diff | annotate | |
| src/sys/kern/kern_sysctl.c | log | diff | annotate | |
| src/sys/kern/vfs_syscalls.c | log | diff | annotate | |
| src/sys/kern/vfs_vnops.c | log | diff | annotate | |
| src/sys/miscfs/fuse/fuse_vnops.c | log | diff | annotate | |
| src/sys/msdosfs/msdosfs_vnops.c | log | diff | annotate | |
| src/sys/nfs/nfs_kq.c | log | diff | annotate | |
| src/sys/sys/file.h | log | diff | annotate | |
| src/sys/tmpfs/tmpfs_vnops.c | log | diff | annotate | |
| src/sys/ufs/ufs/ufs_vnops.c | log | diff | annotate | |
| message |
Allow concurrent reads of the f_offset field of struct file by serializing both read/write operations using the existing file mutex. The vnode lock still grants exclusive write access to the offset; the mutex is only used to make the actual write atomic and prevent any concurrent reader from observing intermediate values. ok mpi@ visa@ |
|||
| date | 2019-08-05T08:46:46Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/dev/diskmap.c | log | diff | annotate |
| message |
Favor vn_close() in the error path of diskmapioctl() since side-effects caused by calling vn_open() with write permissions must be reverted. Otherwise, the vfs subsystem could panic while releasing the last vnode reference if the writecount is still positive. ok visa@ Reported-by: [email protected] Reported-by: [email protected] |
|||
| date | 2019-08-05T10:42:51Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/net/if_aggr.c | log | diff | annotate |
| message |
try to be more compliant with the spec by implementing marker responses. i hope, i didn't test this that hard. |
|||
| date | 2019-08-05T13:31:07Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/kern/kern_unveil.c | log | diff | annotate |
| message | Remove the unused function parameter rootvnode from unveil_add_vnode(). | |||
| date | 2019-08-05T15:13:43Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/kern/vfs_syscalls.c | log | diff | annotate |
| message |
Kernel realpath(3) had the same vnode leakage bug like unveil(2). If parent and lookup vnode are equal, namei(9) locks them once but reference counts twice. from Moritz Buhl |
|||
| date | 2019-08-05T23:28:55Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/kern/vfs_syscalls.c | log | diff | annotate |
| message |
Kernel realpath(3) and unveil(2) did not work correctly if the root directory was written as "//". If there is no non-slash character in the path name, use the spacial case for root. found by gmake regression tests; OK naddy@ benno@ |
|||