{"push_id":872056547,"size":6,"distinct_size":6,"ref":"refs/heads/br-riscv","head":"857836d8bfc1e0bd6709321ac544fb04cd953670","before":"2f4577c330669a59f7a3aab6b711118d8f929f9e","commits":[{"sha":"5ec1c28867cc831823aa9d848fa6fb9012148ff8","author":{"email":"d43962b0ecc6fa2a514f5b58406ccb3c870bdd0e@FreeBSD.org","name":"araujo"},"message":"If a NIS server has long entries on its database that is bigger than\n1024 specified on YPMAXRECORD the ypmatch can get in an infinite retry\nloop when is requesting the information from the NIS server.\n\nThe ypmatch(1) will return an error until the command receives an\nkill(1).\n\nTo avoid this problem, we check the MAX_RETRIES that is by default set\nto 20 and avoid get in infinet loop at the client side.\n\nNOTE: FreeBSD nis(8) server doesn't present this issue.\n\nSubmitted by:\tRavi Pokala <rpokala@panasas.com>,\n\t\tLakshmi N. Sundararajan <lakshmi.n@msystechnologies.com>,\n\t\tLewis, Fred <flewis@panasas.com>,\n\t\tPushkar Kothavade <pushkar.kothavade@msystechnologies.com>\nApproved by:\tbapt (mentor)\nMFC after:\t1 month\nDifferential Revision:\tD4095","distinct":true,"url":"https://api.github.com/repos/freebsd-riscv/freebsd/commits/5ec1c28867cc831823aa9d848fa6fb9012148ff8"},{"sha":"f2aa140123cb6701c58f52302538181a623480c4","author":{"email":"020c73c6726e858291045c5ac872c6f3d8399032@FreeBSD.org","name":"jtl"},"message":"Consistently enforce the restriction against calling malloc/free when in a\ncritical section.\n\numa_zalloc_arg()/uma_zalloc_free() may acquire a sleepable lock on the\nzone. The malloc() family of functions may call uma_zalloc_arg() or\numa_zalloc_free().\n\nThe malloc(9) man page currently claims that free() will never sleep.\nIt also implies that the malloc() family of functions will not sleep\nwhen called with M_NOWAIT. However, it is more correct to say that\nthese functions will not sleep indefinitely. Indeed, they may acquire\na sleepable lock. However, a developer may overlook this restriction\nbecause the WITNESS check that catches attempts to call the malloc()\nfamily of functions within a critical section is inconsistenly\napplied.\n\nThis change clarifies the language of the malloc(9) man page to clarify\nthe restriction against calling the malloc() family of functions\nwhile in a critical section or holding a spin lock. It also adds\nKASSERTs at appropriate points to make the enforcement of this\nrestriction more consistent.\n\nPR:\t\t204633\nDifferential Revision:\thttps://reviews.freebsd.org/D4197\nReviewed by:\tmarkj\nApproved by:\tgnn (mentor)\nSponsored by:\tJuniper Networks","distinct":true,"url":"https://api.github.com/repos/freebsd-riscv/freebsd/commits/f2aa140123cb6701c58f52302538181a623480c4"},{"sha":"b88d7b66e20d669f53c7bfe31c1ec59fa6eee311","author":{"email":"3eb65786145ecb71e9dcbb3a09f06a0b3a6c4d2d@bsdpad.com","name":"Ruslan Bukin"},"message":"Cleanup","distinct":true,"url":"https://api.github.com/repos/freebsd-riscv/freebsd/commits/b88d7b66e20d669f53c7bfe31c1ec59fa6eee311"},{"sha":"353275d1efeae9b2d193c3b7aa822cf0120b99d5","author":{"email":"3eb65786145ecb71e9dcbb3a09f06a0b3a6c4d2d@bsdpad.com","name":"Ruslan Bukin"},"message":"Merge branch 'master' of https://github.com/freebsd/freebsd into br-riscv","distinct":true,"url":"https://api.github.com/repos/freebsd-riscv/freebsd/commits/353275d1efeae9b2d193c3b7aa822cf0120b99d5"},{"sha":"cd2e90d29f81af0e22b708130c63cefc0a1069a2","author":{"email":"3eb65786145ecb71e9dcbb3a09f06a0b3a6c4d2d@bsdpad.com","name":"Ruslan Bukin"},"message":"Remove local hack","distinct":true,"url":"https://api.github.com/repos/freebsd-riscv/freebsd/commits/cd2e90d29f81af0e22b708130c63cefc0a1069a2"},{"sha":"857836d8bfc1e0bd6709321ac544fb04cd953670","author":{"email":"3eb65786145ecb71e9dcbb3a09f06a0b3a6c4d2d@bsdpad.com","name":"Ruslan Bukin"},"message":"Cleanup","distinct":true,"url":"https://api.github.com/repos/freebsd-riscv/freebsd/commits/857836d8bfc1e0bd6709321ac544fb04cd953670"}]}