created | 2019-09-06T05:01:09Z |
---|---|
begin | 2019-09-04T00:00:00Z |
end | 2019-09-05T00:00:00Z |
path | src/sys |
commits | 12 |
date | 2019-09-04T11:25:54Z | |||
---|---|---|---|---|
author | kettenis | |||
files | src/sys/dev/ofw/ofw_misc.c | log | diff | annotate |
message | Add comment. |
date | 2019-09-04T14:27:55Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/kern/kern_time.c | log | diff | annotate |
message |
gettimeofday, settimeofday(2): limit timezone support For gettimeofday(2), always copy out an empty timezone struct. For settimeofday(2), still copyin(9) the struct but ignore the contents. In gettimeofday(2)'s case we have not changed the original BSD semantics: the kernel only tracks UTC time without an offset for DST, so a zeroed timezone struct is the correct thing to return to the caller. Future work could move these out into libc as stubs for clock_gettime and clock_settime(2). But, definitely a "later" thing, given that we are in beta. Update the manpage to de-emphasize the timezone parameters for these syscalls. Discussed with tedu@, deraadt@, millert@, kettenis@, yasuoka@, jca@, and guenther@. Tested by job@. Ports input from jca@ and sthen@. Manpage input from jca@. ok jca@ deraadt@ |
date | 2019-09-04T14:29:41Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/arch/alpha/conf/RAMDISK | log | diff | annotate |
src/sys/arch/alpha/conf/RAMDISKB | log | diff | annotate | |
src/sys/arch/alpha/conf/RAMDISKBIG | log | diff | annotate | |
src/sys/arch/alpha/conf/RAMDISKC | log | diff | annotate | |
src/sys/arch/amd64/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/amd64/conf/RAMDISK_CD | log | diff | annotate | |
src/sys/arch/arm64/conf/GENERIC | log | diff | annotate | |
src/sys/arch/arm64/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/armv7/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/hppa/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/i386/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/i386/conf/RAMDISK_CD | log | diff | annotate | |
src/sys/arch/landisk/conf/RAMDISK | log | diff | annotate | |
message | Remove DST/TIMEZONE options(4) from kernel configs; ok jca@ deraadt@ |
date | 2019-09-04T14:29:42Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/arch/loongson/conf/RAMDISK | log | diff | annotate |
src/sys/arch/luna88k/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/macppc/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/octeon/conf/BOOT | log | diff | annotate | |
src/sys/arch/octeon/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/sgi/conf/RAMDISK-IP22 | log | diff | annotate | |
src/sys/arch/sgi/conf/RAMDISK-IP26 | log | diff | annotate | |
src/sys/arch/sgi/conf/RAMDISK-IP27 | log | diff | annotate | |
src/sys/arch/sgi/conf/RAMDISK-IP28 | log | diff | annotate | |
src/sys/arch/sgi/conf/RAMDISK-IP30 | log | diff | annotate | |
src/sys/arch/sgi/conf/RAMDISK-IP32 | log | diff | annotate | |
src/sys/arch/sparc64/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/sparc64/conf/RAMDISKU1 | log | diff | annotate | |
src/sys/arch/sparc64/conf/RAMDISKU5 | log | diff | annotate | |
message | Remove DST/TIMEZONE options(4) from kernel configs; ok jca@ deraadt@ |
date | 2019-09-04T14:40:22Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/msdosfs/msdosfs_conv.c | log | diff | annotate |
message |
msdosfs: remove timezone support This support is undocumented, only works if you're using the kernel timezone, and breaks during a DST shift. It also preferences file systems managed by a Windows installation: many implementations, like ours, use UTC by default (think: phones, digital cameras). No complaints on tech@. "good riddance" tedu@, "Yep." deraadt@ |
date | 2019-09-04T16:11:58Z | |||
---|---|---|---|---|
author | bluhm | |||
files | src/sys/netinet6/ip6_mroute.c | log | diff | annotate |
message |
Fix a route use after free in IPv6 multicast route. Move the mrt6_mcast6_del() out of the rtable_walk(). This avoids recursion to prevent stack overflow. Also it allows freeing the route outside of the walk. Now mrt6_mcast_del() frees the route only when it is deleted from the routing table. If that fails, it must not be freed. After the route is returned by mf6c_find(), it is reference counted. Then we need a rtfree(), but not in the other case. Name mrt6_mcast_add() and mrt6_mcast_del() consistently. Move rt_timer_remove_all() into mrt6_mcast_del(). Reported-by: [email protected] OK mpi@ |
date | 2019-09-04T16:13:49Z | |||
---|---|---|---|---|
author | bluhm | |||
files | src/sys/netinet6/ip6_mroute.c | log | diff | annotate |
message | Add RCS Id. |
date | 2019-09-04T17:15:56Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/scsi/st.c | log | diff | annotate |
message |
The great density mode purge of 2006 (r1.62) was never carried through to a logical conclusion. Start cleaning up the left overs. First, delete the unused quirk ST_Q_BLKSIZE and simplify the one condition referencing it in light of the fact that !ST_Q_BLKSIZE would always be true. |
date | 2019-09-04T18:41:33Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/scsi/st.c | log | diff | annotate |
message |
Various whitespace nits. Reformat quirks array the way the autoindenter likes it to minimize the effort needed to keep diffs short. |
date | 2019-09-04T19:09:41Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/scsi/st.c | log | diff | annotate |
message |
'quirks' field of struct modes is superfluous. There is only 1 mode. Just use the 'quirks' field of struct quirksdata. |
date | 2019-09-04T20:03:12Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/scsi/st.c | log | diff | annotate |
message |
Hoist the quirks up another rung. drive_quirks is superfluous, just store the discovered quirks in st_softc's 'quirks' field. |
date | 2019-09-04T23:40:28Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/scsi/st.c | log | diff | annotate |
message |
Shuffle sdstart() and sdminphys() declarations closer to their friends. Nuke pointless 'quirkdata' pointer in st_softc. We use the data once at attach time and don't need to remember where we got it from. |