<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>02f234f3 - MFC r351399: Fix the build with WITHOUT_GOOGLETEST</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/tests/sys/fs/Makefile#02f234f3</link>
        <description>MFC r351399: Fix the build with WITHOUT_GOOGLETESTAttempting to build the fusefs tests WITHOUT_GOOGLETEST will result in anerror if the host system or sysroot doesn&apos;t already have googletest headersin /usr/include/private (e.g. host built/installed WITHOUT_GOOGLETEST, cleancross-buildworld WITHOUT_GOOGLETEST).

            List of files:
            /freebsd-12.1/tests/sys/fs/Makefile</description>
        <pubDate>Sun, 15 Sep 2019 14:37:50 +0000</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>00228bec - MFC the new fusefs driver</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/tests/sys/fs/Makefile#00228bec</link>
        <description>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 &quot;mount -u&quot;* 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&apos;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&apos;t been any test failures until now.  But fusefs-lkl requires therequest&apos;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&apos;m sorry I&apos;ve beencomitting so hastily.Reported by:	rpokalaReviewed by:	rpokalaMFC-With:	351061Sponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D21265r351113:fusefs: don&apos;t send the namespace during listextattrThe FUSE_LISTXATTR operation always returns the full list of a file&apos;sextended attributes, in all namespaces. There&apos;s no way to filter the listserver-side. However, currently FreeBSD&apos;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&apos;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&apos;s listxattr(2): if the  caller does not provide enough space, then the server should return ERANGE  rather than return a truncated list.  That&apos;s true even though in FUSE&apos;s  case the kernel doesn&apos;t provide space to the client at all; it simply  requests a maximum size for the list.  We previously weren&apos;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&apos;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&apos;m using a buffer to store strings, when in fact I&apos;m  really just using it to store a byte array that happens to be initialized  with a string. I&apos;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&apos;m going to try to fix this with  Coverity modeling, but I&apos;ll also change an EXPECT to ASSERT so we don&apos;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&apos;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&apos; 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&apos;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/tests/sys/fs/Makefile</description>
        <pubDate>Sun, 15 Sep 2019 04:14:31 +0000</pubDate>
        <dc:creator>Alan Somers &lt;asomers@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>669c2535 - Integrate contrib/netbsd-tests/fs/tmpfs into the FreeBSD test suite</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/tests/sys/fs/Makefile#669c2535</link>
        <description>Integrate contrib/netbsd-tests/fs/tmpfs into the FreeBSD test suiteas tests/sys/fsThese testcases exercise tmpfs supportMFC after:	2 weeksSponsored by:	Dell EMC Isilon

            List of files:
            /freebsd-12.1/tests/sys/fs/Makefile</description>
        <pubDate>Fri, 21 Oct 2016 05:24:08 +0000</pubDate>
        <dc:creator>Enji Cooper &lt;ngie@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
