{"push_id":1310578546,"size":1000,"distinct_size":9253,"ref":"refs/heads/master","head":"3d3e8fb2475fff335e9ad001699dc69f10f2df91","before":"ca306200182fff93e860526ec021a5c8ea545c03","commits":[{"sha":"5cba75d7c70f66075115953d248d0636c4d4085b","author":{"name":"markj","email":"47b3ed30e5a83fd756a28e99bf1950376aed42e8@FreeBSD.org"},"message":"MFC r295583, r295584, r295729, r295730:\nNDP code cleanup changes.\n\nMFC r295732:\nFix an IPv6 DAD reference count leak.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/5cba75d7c70f66075115953d248d0636c4d4085b"},{"sha":"fdef3ab0211b87d886c8a87fe46be53c0642ee0c","author":{"name":"jtl","email":"5a4310232d3032dace51fcd14379dd3cb74d04b7@FreeBSD.org"},"message":"MFC r298408:\n  Prevent underflows in tp->snd_wnd if the remote side ACKs more than\n  tp->snd_wnd. This can happen, for example, when the remote side responds\n  to a window probe by ACKing the one byte it contains.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/fdef3ab0211b87d886c8a87fe46be53c0642ee0c"},{"sha":"399bde7ffd971f7602a44774c88871a7414c157b","author":{"name":"pfg","email":"b4bef5e76f3a4d1e472e2020ecbc9a2f265096d4@FreeBSD.org"},"message":"MFC r298868, r298874:\nrestore: fix memory and resource handle leaks.\n\nCID:\t\t272297, 1007784","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/399bde7ffd971f7602a44774c88871a7414c157b"},{"sha":"90678861caecec09aa55f23a43decea36e8834b6","author":{"name":"sephe","email":"0d6bcc8c34e4768bd207247de4ee55fd5915c840@FreeBSD.org"},"message":"MFC r298038\n\nhyperv/stor: Temporary disable the wrongly done command timeout.\n\nIt will be reenabled once the request processing is corrected.\n\nSponsored by:\tMicrosoft OSTC","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/90678861caecec09aa55f23a43decea36e8834b6"},{"sha":"a12d292261f46057b0544ea29d3ad3090b61ce89","author":{"name":"sephe","email":"0d6bcc8c34e4768bd207247de4ee55fd5915c840@FreeBSD.org"},"message":"MFC r298385\n\ndhclient: Log a warning instead of bailing upon \"illegal\" options\n\nIn Azure, the DHCP servers add private option (id 0xf5), which contains\nbinary form of an IPv4 address. Once this option is converted to string\nform, it could contain '$', e.g.\n\nIPv4 address: 100.72.36.54\nbinary form: 0x64 0x48 0x24 0x36\nstring form: \"dH$6\"\n\ndhclient bails upon \"illegal\" options like the above example, thus the\nVM bring-up will fail.\n\nAlso as a side note, this \"illegal\" option detection was added in\nOpenBSD ~11years ago:\nhttp://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin/dhclient/dhclient.c?rev=1.50&content-type=text/x-cvsweb-markup\n\nAnd it was removed along with the removal of script support in OpenBSD\n~3years ago:\nhttp://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin/dhclient/dhclient.c?rev=1.159&content-type=text/x-cvsweb-markup\n\nReported by:\tHongxiong Xian <v-hoxian microsoft com>\nReviewed by:\tjhb, Dexuan Cui <decui microsoft com>\nTested by:\tHongxiong Xian <v-hoxian microsoft com>\nAnalyzed by:\tDong Liu <doliu microsoft com>\nSponsored by:\tMicrosoft OSTC\nDifferential Revision:\thttps://reviews.freebsd.org/D5853","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/a12d292261f46057b0544ea29d3ad3090b61ce89"},{"sha":"344a285d780c5e77f293134bdeaae37053f8971c","author":{"name":"bcr","email":"a3f3208a081f5aee2be6335f34a25456c98a99c1@FreeBSD.org"},"message":"MFC r298893:\nProvide an example to the kqueue man page, showing\na basic usage example.  Although it is an\nuntypical example for the use of kqueue, it is\nbetter than nothing and should get people started.\n\nPR:\t\t196844\nSubmitted by:\tfernando.apesteguia@gmail.com\nReviewed by:\tkib\nApproved by:\tkib\nDifferential Revision:  https://reviews.freebsd.org/D6082","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/344a285d780c5e77f293134bdeaae37053f8971c"},{"sha":"b67c104f1b8cb3d6a5a5b5dfe47492ae00e5c848","author":{"name":"sbruno","email":"d5ff4883b309663de90db713f6552b6c0b42502b@FreeBSD.org"},"message":"MFC r298279\n\nPlug memory leak in ctl(4) when ctl_copyin_args() is called with a non-\nnull terminated ASCII string.\n\nPR:\t\t207626\nSubmitted by:\tcturt@hardenedbsd.org","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/b67c104f1b8cb3d6a5a5b5dfe47492ae00e5c848"},{"sha":"4bfb599a88eed45fdf48862528275443df7623b7","author":{"name":"sbruno","email":"d5ff4883b309663de90db713f6552b6c0b42502b@FreeBSD.org"},"message":"MFC r298224\n\nCorrect possible underflow conditions when checking for available space\nin the tx h/w ring buffer.\n\nSponsored by:\tLimelight Networks","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/4bfb599a88eed45fdf48862528275443df7623b7"},{"sha":"00649b2ea81b97c73999ace6219ec79a366790a2","author":{"name":"sbruno","email":"d5ff4883b309663de90db713f6552b6c0b42502b@FreeBSD.org"},"message":"MFC r298280\n\naacraid(4): Sanely copyin userland pointers and ensure that we don't get\nanything janky from a user. (cturt)\n\naac(4) landergriffith+freebsdbugzilla@gmail.com pointed out that aac(4)\nhad the same issue and handling of pointers, so let's change that too.\n\nPR:\t\t206573\nSubmitted by:\tcturt@hardenedbsd.org","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/00649b2ea81b97c73999ace6219ec79a366790a2"},{"sha":"45f14820b0ec21c50e7647c5dfde71d497adade8","author":{"name":"rmacklem","email":"41d58ec6f63c608c74759e8abb6a62fcbabf5df2@FreeBSD.org"},"message":"MFC: r297837\nBruce Evans reported that there was a performance regression between\nthe old and new NFS clients. He did a good job of isolating the problem\nwhich was caused by the new NFS client not setting the post write mtime\ncorrectly. The new NFS client code was cloned from the old client, but\nwas incorrect, because the mtime in the nfs vnode's cache wasn't yet\nupdated. This patch fixes this problem. The patch also adds missing mutex\nlocking.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/45f14820b0ec21c50e7647c5dfde71d497adade8"},{"sha":"87a1c9e2bc3b23998e3f5436aa6e2820bcde44b0","author":{"name":"rmacklem","email":"41d58ec6f63c608c74759e8abb6a62fcbabf5df2@FreeBSD.org"},"message":"MFC: r297869\nIf the VOP_SETATTR() call that saves the exclusive create verifier failed,\nthe NFS server would leave the newly created vnode locked. This could\nresult in a file system that would not unmount and processes wedged,\nwaiting for the file to be unlocked.\nSince this VOP_SETATTR() never fails for most file systems, this bug\ndoesn't normally manifest itself. I found it during testing of an\nexported GlusterFS file system, which can fail.\nThis patch adds the vput() and changes the error to the correct NFS one.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/87a1c9e2bc3b23998e3f5436aa6e2820bcde44b0"},{"sha":"8164852d60b6e40c7105ae9781d95de68e4f5be1","author":{"name":"dchagin","email":"dd471d854a70d8f4c09fe2d1c417a1710115ea8b@FreeBSD.org"},"message":"MFC r298519:\nFix streams and svr4 module dependency. Both modules are complaining about\nundefined symbol svr4_delete_socket which was moved from streams to the svr4 module\nin r160558 that created a two-way dependency between them.\n\nMFC r298520:\nAllow to build svr4 module with SYSV support separatelly from the kernel build.\n\nPR:\t\t208464\nReported by:\tKristoffer Eriksson","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/8164852d60b6e40c7105ae9781d95de68e4f5be1"},{"sha":"5caad23a8a432db49f549d3e8e215f47f1ba89e6","author":{"name":"dchagin","email":"dd471d854a70d8f4c09fe2d1c417a1710115ea8b@FreeBSD.org"},"message":"MFC r285394 (by mjg@):\nvref the vnode passed to vn_fullpath.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/5caad23a8a432db49f549d3e8e215f47f1ba89e6"},{"sha":"2bbf6b4b75457aadc05058cc03b671f3372b6eb2","author":{"name":"dchagin","email":"dd471d854a70d8f4c09fe2d1c417a1710115ea8b@FreeBSD.org"},"message":"MFC r295856 (by des@):\nImplement /proc/$$/limits.\n\nMFC r297781 (by dchagin@):\nMore complete implementation of /proc/self/limits.\nFix the way the code accesses process limits struct - pointed out by mjg@.\n\nMFC r298318, 298319 (by cem@):\nDon't print uninitialized values and initialize error return before use.\n\nPR:\t\t207386","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/2bbf6b4b75457aadc05058cc03b671f3372b6eb2"},{"sha":"2051c9b023f12da3a8b40342d4484f3cf8069b83","author":{"name":"rmacklem","email":"41d58ec6f63c608c74759e8abb6a62fcbabf5df2@FreeBSD.org"},"message":"MFC: r298495\nFix a LOR in the NFSv4.1 server.\n\nThe ordering of acquisition of the state and session mutexes was\nreversed in two cases executed when an NFSv4.1 client created/freed\na session. Since clients will typically do this only when mounting\nand dismounting, the likelyhood of causing a deadlock was low but possible.\nThis can only occur for NFSv4.1 mounts, since the others do not\nuse sessions.\nThis was detected while testing the pNFS server/client where the\nclient crashed during dismounting.\nThe patch also reorders the unlocks, although that isn't necessary\nfor correct operation.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/2051c9b023f12da3a8b40342d4484f3cf8069b83"},{"sha":"2896a257180eedb682efef6d421b860208065553","author":{"name":"rmacklem","email":"41d58ec6f63c608c74759e8abb6a62fcbabf5df2@FreeBSD.org"},"message":"MFC: r298523\nAllow the NFSv4 server to reply NFSERR_WRONGSEC for the SetClientID operation.\n\nIt was reported via email that a Linux client couldn't do a Kerberized\nNFS mount when only \"sec=krb5\" was specified for the exports. The Linux\nclient attempted a mount via krb5i and the server replied NFSERR_SERVERFAULT.\nAlthough NFSERR_WRONGSEC isn't listed as an error for SetClientID, I\nthink it is the correct reply, so this patch enables that.\nI do not know if this fixes the mount attempt, but adding \"krb5i\" to the\nlist of allowed security flavours does allow the mount to work.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/2896a257180eedb682efef6d421b860208065553"},{"sha":"81e53c0ce30e143c149e439284bb82999e092b99","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"MFC r298890:\nMake it explicit that D_MEM cdevsw d_flag is to signify that the\ndriver is (or behaves identically to) /dev/mem.  Remove the D_MEM flag\nfrom random drivers.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/81e53c0ce30e143c149e439284bb82999e092b99"},{"sha":"b541111f4875e3769e0f0cc615c7e2216292ac94","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"MFC r298891:\nAvoid duplicated calls to pmap_page_get_memattr().\nAvoid logging inconsistency for the /dev/mem device.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/b541111f4875e3769e0f0cc615c7e2216292ac94"},{"sha":"1e1c6951b00289b8de42bb7d821861b25d4fc604","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"MFC r298898:\nExplain NOTE_LINK reporting for the directories.","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/1e1c6951b00289b8de42bb7d821861b25d4fc604"},{"sha":"474ac0fbf4af918a4825854649bafccc48949fc1","author":{"name":"delphij","email":"42e0a3b0cf665f904614845e159d13b2ed3608f0@FreeBSD.org"},"message":"Revert r298920 until we have addressed all known regressions on head/ after\nsettle.  file is now downgraded to 5.25.\n\nPR:\t\tbin/209211\nRequested by:\tTomoaki AOKI\nRelnotes:\tyes","distinct":true,"url":"https://api.github.com/repos/markjdb/freebsd-dev/commits/474ac0fbf4af918a4825854649bafccc48949fc1"}]}
{"actor":{"display_login":"markjdb"}}