Changes in UPDATING

3df06c28 - Add UPDATING entry and bump version

Fri, 29 Jan 2021 00:16:22 +0000

Add UPDATING entry and bump versionApproved by: so List of files: /freebsd-12.1/UPDATING

e30782bb - Fix OpenSSL NULL pointer de-reference.

Tue, 08 Dec 2020 19:10:40 +0000

Fix OpenSSL NULL pointer de-reference.Approved by: soSecurity: FreeBSD-SA-20:33.opensslSecurity: CVE-2020-1971 List of files: /freebsd-12.1/UPDATING

c944cb74 - Add UPDATING entries and bump version.

Tue, 01 Dec 2020 19:40:58 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

554a831b - Add UPDATING entries and bump version.

Tue, 15 Sep 2020 21:48:24 +0000

Add UPDATING entries and bump version.Approved by: soApproved by: re (implicit for releng/12.2) List of files: /freebsd-12.1/UPDATING

145fad72 - Add UPDATING entries and bump version.

Wed, 02 Sep 2020 16:29:40 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

136975a9 - Add UPDATING entries and bump version.

Wed, 05 Aug 2020 17:14:37 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

46b2ed29 - Add UPDATING entries and bump version.

Wed, 08 Jul 2020 20:26:19 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

5c94e710 - Add UPDATING entries and bump version.

Tue, 09 Jun 2020 16:15:07 +0000

Add UPDATING entries and bump version.Approved by: soApproved by: re (implicit) List of files: /freebsd-12.1/UPDATING

f132e99e - Add UPDATING entries and bump version.

Tue, 12 May 2020 17:00:23 +0000

Add UPDATING entries and bump version.Approved by: soApproved by: re (implicit) List of files: /freebsd-12.1/UPDATING

3689a022 - Add UPDATING entries and bump version.

Tue, 21 Apr 2020 15:54:08 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

514c1ff9 - Add UPDATING entries and bump version.

Thu, 19 Mar 2020 17:01:57 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

e75cfcd9 - Add UPDATING entries and bump version.

Tue, 28 Jan 2020 18:58:37 +0000

Add UPDATING entries and bump version.Approved by: so List of files: /freebsd-12.1/UPDATING

8cd56fbf - Add UPDATING entries and bump version numbers.

Tue, 12 Nov 2019 18:13:51 +0000

Add UPDATING entries and bump version numbers.Approved by: so List of files: /freebsd-12.1/UPDATING

cc807f9e - - Switch releng/12.1 from RC2 to RELEASE.

Fri, 01 Nov 2019 00:00:17 +0000

- Switch releng/12.1 from RC2 to RELEASE.- Add the anticipated 12.1-RELEASE date to UPDATING.- Set a static __FreeBSD_version.Approved by: re (implicit)Sponsored by: Rubicon Communications, LLC (Netgate) List of files: /freebsd-12.1/UPDATING

00228bec - MFC the new fusefs driver

Sun, 15 Sep 2019 04:14:31 +0000

MFC the new fusefs driverMFC r350665, r350990, r350992, r351039, r351042, r351061, r351066, r351113, r351560, r351961, r351963, r352021, r352025, r352230r350665:fusefs: merge from projects/fuse2This commit imports the new fusefs driver. It raises the protocol levelfrom 7.8 to 7.23, fixes many bugs, adds a test suite for the driver, andadds many new features. New features include:* Optional kernel-side permissions checks (-o default_permissions)* Implement VOP_MKNOD, VOP_BMAP, and VOP_ADVLOCK* Allow interrupting FUSE operations* Support named pipes and unix-domain sockets in fusefs file systems* Forward UTIME_NOW during utimensat(2) to the daemon* kqueue support for /dev/fuse* Allow updating mounts with "mount -u"* Allow exporting fusefs file systems over NFS* Server-initiated invalidation of the name cache or data cache* Respect RLIMIT_FSIZE* Try to support servers as old as protocol 7.4Performance enhancements include:* Implement FUSE's FOPEN_KEEP_CACHE and FUSE_ASYNC_READ flags* Cache file attributes* Cache lookup entries, both positive and negative* Server-selectable cache modes: writethrough, writeback, or uncached* Write clustering* Readahead* Use counter(9) for statistical reportingPR: 199934 216391 233783 234581 235773 235774 235775PR: 236226 236231 236236 236291 236329 236381 236405PR: 236327 236466 236472 236473 236474 236530 236557PR: 236560 236844 237052 237181 237588 238565Reviewed by: bcr (man pages)Reviewed by: cem, ngie, rpokala, glebius, kib, bde, emaste (post-commit review on project branch)Relnotes: yesSponsored by: The FreeBSD FoundationPull Request: https://reviews.freebsd.org/D21110r350990:fusefs: add SVN Keywords to the test filesReported by: SVN pre-commit hooksMFC-With: r350665Sponsored by: The FreeBSD Foundationr350992:fusefs: skip some tests when unsafe aio is disabledMFC-With: r350665Sponsored by: The FreeBSD Foundationr351039:fusefs: fix intermittency in the default_permissions.Unlink.ok testThe test needs to expect a FUSE_FORGET operation. Most of the time the testwould pass anyway, because by chance FUSE_FORGET would arrive after theunmount.MFC-With: 350665Sponsored by: The FreeBSD Foundationr351042:fusefs: Fix the size of fuse_getattr_inIn FUSE protocol 7.9, the size of the FUSE_GETATTR request has increased.However, the fusefs driver is currently not sending the additional fields.In our implementation, the additional fields are always zero, so I therehaven't been any test failures until now. But fusefs-lkl requires therequest's length to be correct.Fix this bug, and also enhance the test suite to catch similar bugs.PR: 239830MFC-With: 350665Sponsored by: The FreeBSD Foundationr351061:fusefs: fix the 32-bit build after 351042Reported by: jhbMFC-With: 351042Sponsored by: The FreeBSD Foundationr351066:fusefs: fix conditional from r351061The entirety of r351061 was a copy/paste error. I'm sorry I've beencomitting so hastily.Reported by: rpokalaReviewed by: rpokalaMFC-With: 351061Sponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D21265r351113:fusefs: don't send the namespace during listextattrThe FUSE_LISTXATTR operation always returns the full list of a file'sextended attributes, in all namespaces. There's no way to filter the listserver-side. However, currently FreeBSD's fusefs driver sends a namespacestring with the FUSE_LISTXATTR request. That behavior was probably copiedfrom fuse_vnop_getextattr, which has an attribute name argument. It'sbeen there ever since extended attribute support was added in r324620. Thiscommit removes it.Reviewed by: cemSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D21280r351560:fusefs: Fix some bugs regarding the size of the LISTXATTR list* A small error in r338152 let to the returned size always being exactly eight bytes too large.* The FUSE_LISTXATTR operation works like Linux's listxattr(2): if the caller does not provide enough space, then the server should return ERANGE rather than return a truncated list. That's true even though in FUSE's case the kernel doesn't provide space to the client at all; it simply requests a maximum size for the list. We previously weren't handling the case where the server returns ERANGE even though the kernel requested as much size as the server had told us it needs; that can happen due to a race.* We also need to ensure that a pathological server that always returns ERANGE no matter what size we request in FUSE_LISTXATTR won't cause an infinite loop in the kernel. As of this commit, it will instead cause an infinite loop that exits and enters the kernel on each iteration, allowing signals to be processed.Reviewed by: cemSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D21287r351961:Coverity fixes in fusefs(5)CID 1404532 fixes a signed vs unsigned comparison error in fuse_vnop_bmap.It could potentially have resulted in VOP_BMAP reporting too manyconsecutive blocks.CID 1404364 is much worse. It was an array access by an untrusted,user-provided variable. It could potentially have resulted in a maliciousfile system crashing the kernel or worse.Reported by: CoverityReviewed by: emasteSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D21466r351963:fusefs: coverity cleanup in the testsAddress the following defects reported by Coverity:* Structurally dead code (CID 1404366): set m_quit before FAIL, not after* Unchecked return value of sysctlbyname (CID 1404321)* Unchecked return value of stat(2) (CID 1404471)* Unchecked return value of open(2) (CID 1404402, 1404529)* Unchecked return value of dup(2) (CID 1404478)* Buffer overflows. These are all false positives caused by the fact that Coverity thinks I'm using a buffer to store strings, when in fact I'm really just using it to store a byte array that happens to be initialized with a string. I'm changing the type from char to uint8_t in the hopes that it will placate Coverity. (CID 1404338, 1404350, 1404367, 1404376, 1404379, 1404381, 1404388, 1404403, 1404425, 1404433, 1404434, 1404474, 1404480, 1404484, 1404503, 1404505)* False positive file descriptor leak. I'm going to try to fix this with Coverity modeling, but I'll also change an EXPECT to ASSERT so we don't perform meaningless assertions after the failure. (CID 1404320, 1404324, 1404440, 1404445).* Unannotated file descriptor leak. This will be followed up by a Coverity modeling change. (CID 1404326, 1404334, 1404336, 1404357, 1404361, 1404372, 1404391, 1404395, 1404409, 1404430, 1404448, 1404451, 1404455, 1404457, 1404458, 1404460)* Uninitialized variables in C++ constructors (CID 1404327, 1404346). In the case of m_maxphys, this actually led to part of the FUSE_INIT's response being set to stack garbage during the WriteCluster::clustering test.* Uninitialized sun_len field in struct sockaddr_un (CID 1404330, 1404371, 1404429).Reported by: CoverityReviewed by: emasteSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D21457r352021:fusefs: suppress some Coverity resource leak CIDs in the testsThe fusefs tests deliberately leak file descriptors. To do otherwise wouldadd extra complications to the tests' mock FUSE server. This annotationshould hopefully convince Coverity to shut up about the leaks.Reviewed by: uqsSponsored by: The FreeBSD Foundationr352025:mount_fusefs: fix a segfault on memory allocation failureReported by: CoverityCoverity CID: 1354188Sponsored by: The FreeBSD Foundationr352230:fusefs: Fix iosize for FUSE_WRITE in 7.8 compat modeWhen communicating with a FUSE server that implements version 7.8 (or older)of the FUSE protocol, the FUSE_WRITE request structure is 16 bytes shorterthan normal. The protocol version check wasn't applied universally, leadingto an extra 16 bytes being sent to such servers. The extra bytes wereallocated and bzero()d, so there was no information disclosure.Reviewed by: emasteMFC-With: r350665Sponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D21557 List of files: /freebsd-12.1/UPDATING

2f3cabf9 - MFC r345350, r346441, r346765

Fri, 06 Sep 2019 17:21:21 +0000

MFC r345350, r346441, r346765r345350:Rename fuse(4) to fusefs(4)This makes it more consistent with other filesystems, which all end in "fs",and more consistent with its mount helper, which is already named"mount_fusefs".Reviewed by: cem, rgrimesSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D19649r346441:Use symlinks for kernel modules rather than hardlinksWhen aliasing a kernel module to a different name (ie if_igb for if_em),it's better to use symlinks than hard links. kldxref will omit entries forthe links, ensuring that the loaded module has the correct name.Reviewed by: impSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D19979r346765:Don't symlink fusefs.ko to fuse.ko on PPCSome PPC systems (PowerNV) use msdosfs for /boot, which can't handle eithersymlinks or hardlinks. So on PPC, copy the module instead. This change fixesinstallkernel on such systems after r345350.Reported by: Brandon Bergren Reviewed by: jhibbits, rgrimesMFC-With: 345350, 346441Sponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D19993 List of files: /freebsd-12.1/UPDATING

cd695c14 - MFC r349807, r349974, r349976, r350324, r350361, r350445

Sun, 11 Aug 2019 23:01:31 +0000

MFC r349807, r349974, r349976, r350324, r350361, r350445r349807:Eliminate spurious periodic.daily error message for rotating accounting log.In 2011, r218961 removed local code for rotating logs in favor of using therotate_log command in etc/rc.d/accounting. If the accounting service isactivated then subsequently de-activated in rc.conf but still remains activein periodic.conf, then you get an error message every day in the periodicjobs about being unable to rotate the logs.With this change to use "onerotate_log", the log rotation will happen thefirst time periodic daily runs after accounting was disabled but periodicaccounting was left enabled. After that happens once, the /var/account/acctwill no longer exist, which results in a different path through the periodiccode and no more error messages will appear (unless daily_show_badconfig isset, in which case the admin will be told that periodic security processingis enabled but the accounting file is not present).This is only a partial fix for the problems reported in PR 202203.PR: 202203r349974:Limit access to system accounting files.In 2013 the security chapter of the Handbook was updated in r42501 tosuggest limiting access to the system accounting file [*1] by creating theinitial file with a mode of 0600. This was in part based on a discussion inthe forums [*2]. Unfortunately, this advice is overridden by the fact that anew file is created as part of periodic daily processing, and the file modeis set by the rc.d/accounting script.These changes update the accounting script to create the directory with mode0750 if it doesn't already exist, and to create the daily file with mode0640. This limits write access to root only, read access to root and membersof wheel, and eliminates world access completely. For admins who want toprevent even members of wheel from accessing the files, the mode of the/var/account directory can be manually changed to 0700, because the scriptnever creates or changes that directory if it already exists.The accounting_rotate_log() function now also handles the error cases of noexisting log file to rotate, and attempting to rotate the file multipletimes (.0 file already exists).Another small change here eliminates the complexity of the mktemp/chmod/mvsequence for creating a new acct file by using install(1) with the flagsneeded to directly create the file with the desired ownership andmodes. That allows coalescing two separate if checkyesno accounting_enableblocks into one.These changes were inspired by my investigation of PR 202203.[1] https://www.freebsd.org/doc/handbook/security-accounting.html[2] http://forums.freebsd.org/showthread.php?t=41059PR: 202203Differential Revision: https://reviews.freebsd.org/D20876r349976:Add an entry mentioning the permission/mode change to daily accounting files.r350324:Fix indentation (spaces->tab).r350361:Re-wrap the text at 80 columns after fixing the indent in the prior commit.r350445:Create the /var/account dir with mode 0750; this is a followup to r349974.The rc.d/account script contains code to create the /var/account dir, soit hadn't occurred to me that it is normally created via mtree; thanks tojilles@ for pointing it out. List of files: /freebsd-12.1/UPDATING

85573313 - MFC r348504 (by kevans):

Tue, 23 Jul 2019 18:40:32 +0000

MFC r348504 (by kevans):llvm-symbolizer: Move out of CLANG_EXTRAS, into CLANGASAN reports become a lot more useful with llvm-symbolizer in $PATH, and thebuild is not much more time-consuming. The added benefit is that theresulting reports will actually include symbol information; without, threadtrace information includes a bunch of addresses that immediately resolve toan inline function in^/contrib/compiler-rt/lib/sanitizer_common/sanitizer_common.h and take alittle more effort to examine.Reviewed by: emasteDifferential Revision: https://reviews.freebsd.org/D20484MFC r349004:Upgrade our copies of clang, llvm, lld, lldb, compiler-rt, libc++,libunwind and openmp to the upstream release_80 branch r363030(effectively, 8.0.1 rc2). The 8.0.1 release should follow this within aweek or so.MFC r349351 (by jhibbits, partially):powerpc: Transition to Secure-PLT, like most other OSs (Toolchain part)Summary:Toolchain follow-up to r349350. LLVM patches will be submitted upstream for9.0 as well.The bsd.cpu.mk change is required because GNU ld assumes BSS-PLT if itcannot determine for certain that it needs Secure-PLT, and some binaries donot compile in such a way to make it know to use Secure-PLT.Reviewed By: nwhitehorn, bdragon, pfgDifferential Revision: https://reviews.freebsd.org/D20598MFC r349793:Upgrade our copies of clang, llvm, lld, lldb, compiler-rt, libc++,libunwind and openmp to the upstream release_80 branch r364487(effectively, 8.0.1 rc3). The 8.0.1 release will most likelyhave no further changes.MFC r350177:Merge llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp8.0.1 final release r366581. The only functional change is a fix for amismerge of upstream r360816, which properly restores the r2 registerwhen unwinding on PowerPC64 (See https://reviews.freebsd.org/D20337).Relnotes: yesPR: 236062 List of files: /freebsd-12.1/UPDATING

ea235a20 - Revert r344898 (by kib), now that clang 8 has been merged:

Sat, 13 Apr 2019 11:09:42 +0000

Revert r344898 (by kib), now that clang 8 has been merged:Disable WITH_RETPOLINE on stable/12.It is known that clang 7 generates broken ifunc calls when retpoline isenabled. Since libc uses ifuncs, mark WITH_RETPOLINE as always brokenand disabled. To be removed after clang 8 MFC.This is a direct commit to the branch.Reported by: manyTested by: Nikola Mihaylov Reviewed by: emasteSponsored by: The FreeBSD Foundation List of files: /freebsd-12.1/UPDATING

4fe15510 - After r346168, put the actual commit dates into UPDATING and

Sat, 13 Apr 2019 08:50:41 +0000

After r346168, put the actual commit dates into UPDATING andObsoleteFiles.inc. I completely forgot about those, sorry.This is a direct commit to stable/12. List of files: /freebsd-12.1/UPDATING