{"push_id":1253562201,"size":30,"distinct_size":30,"ref":"refs/heads/master","head":"ee90d2aeb37da008cd42576cc887f110f11ba115","before":"854321733645cfdec8dc4f80518172050d5d5cbe","commits":[{"sha":"fae35efb7f672f76d5a7fc43f0ee382f5d83c7de","author":{"name":"rrs","email":"2c8bebb97edb135d7e520425780adfbbc1757d40@FreeBSD.org"},"message":"This cleans up the timer code in TCP and also makes it so we do not\ntake the INFO lock *unless* we are really going to delete the TCB.\n\nDifferential Revision:\tD7136","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/fae35efb7f672f76d5a7fc43f0ee382f5d83c7de"},{"sha":"30758bfe033754eeccf880590167094277c03c6b","author":{"name":"rrs","email":"2c8bebb97edb135d7e520425780adfbbc1757d40@FreeBSD.org"},"message":"Comments describing how to properly use the new lock_add functions\nand its respective companion.\n\nSponsored by:\tNetflix Inc.","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/30758bfe033754eeccf880590167094277c03c6b"},{"sha":"2f07869625fd0587fc0ef78b9353be4235e1ab5a","author":{"name":"sbz","email":"6ec121fb1c6c832012c7f2026d121713b88e09c3@FreeBSD.org"},"message":"tty: Use proper definition of exit status code and stdin macro\n\nReviewed by:\tbapt, bdrewery\nDifferential Revision:\thttps://reviews.freebsd.org/D6828","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/2f07869625fd0587fc0ef78b9353be4235e1ab5a"},{"sha":"7019b55f504e07b3f4d20e2d17224f4c30e7948e","author":{"name":"manu","email":"72114924aa08a15a82c8c613abfdd8e52e025bb3@FreeBSD.org"},"message":"Use %ju modifier for u_int64_t and %jd modifier for off_t.\noff_t is long long on arm32 and long on amd64\n\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/7019b55f504e07b3f4d20e2d17224f4c30e7948e"},{"sha":"f13741f250f48623ccf836447379ec014c6d1c2d","author":{"name":"manu","email":"72114924aa08a15a82c8c613abfdd8e52e025bb3@FreeBSD.org"},"message":"Only use WaitForKeys event if it exists, this is not the case in u-boot efi implementation.\n\nReviewed by:\tjhb, emaste\nMFC after:\t1 week\nDifferential Revision:\thttps://reviews.freebsd.org/D6781","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/f13741f250f48623ccf836447379ec014c6d1c2d"},{"sha":"4d7e0cd8cdd16c3e6822ad1f71f93c8707eefec9","author":{"name":"rrs","email":"2c8bebb97edb135d7e520425780adfbbc1757d40@FreeBSD.org"},"message":"Here we update the  modular tcp to be able to switch to an\nalternate TCP stack in other then the closed state (pre-listen/connect).\nThe idea is that *if* that is supported by the alternate stack, it\nis asked if its ok to switch. If it approves the \"handoff\" then we\nallow the switch to happen. Also the fini() function now gets a flag\nto tell if you are switching away *or* the tcb is destroyed. The\ninit() call into the alternate stack is moved to the end so the\ntcb is more fully formed before the init transpires.\n\nSponsored by:\tNetflix Inc.\nDifferential Revision:\tD6790","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/4d7e0cd8cdd16c3e6822ad1f71f93c8707eefec9"},{"sha":"c9af4f2541fd437e0805365fbeec46d69e033310","author":{"name":"rrs","email":"2c8bebb97edb135d7e520425780adfbbc1757d40@FreeBSD.org"},"message":"A few more wording tweaks as suggested (with some modifications\nas well) by Ravi Pokala. Thanks for the comments :-)\nSponsored by: Netflix Inc.","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/c9af4f2541fd437e0805365fbeec46d69e033310"},{"sha":"26a21fb116af44eec505aa2fc2192b9f087f0785","author":{"name":"araujo","email":"055005da815b4a0b34f5dba644a1dd2bae09a23a@FreeBSD.org"},"message":"Use nitems() from sys/param.h.\n\nMFC after:\t2 weeks.","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/26a21fb116af44eec505aa2fc2192b9f087f0785"},{"sha":"cc1da273bdb9f0bb76ead167aef29e8355c0e0d2","author":{"name":"araujo","email":"055005da815b4a0b34f5dba644a1dd2bae09a23a@FreeBSD.org"},"message":"Use nitems() from sys/param.h.\n\nMFC after:\t2 weeks.","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/cc1da273bdb9f0bb76ead167aef29e8355c0e0d2"},{"sha":"03c6968a37b4902e5b6ecb785eb9d455d147ac83","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"In ffs_balloc_ufs{1,2} routines, assert that unwind records do not\noverflow local arrays.  This is not immediately obvious from the\nstatic code inspection, due to retry logic.\n\nReviewed by:\tmckusick\nTested by:\tpho\nSponsored by:\tThe FreeBSD Foundation\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/03c6968a37b4902e5b6ecb785eb9d455d147ac83"},{"sha":"4e01efcc0c917cfbefc61574b016fb62540e53e0","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"When block allocation fails in UFS_BALLOC(), and the volume does not\nhave SU enabled, there is no point in calling softdep_request_cleanup().\n\nThe call cannot produce free blocks, but we unecessarily lock ufsmount\nand do inode block write.  Usual point of not doing optimizations for\nthe corner case of the full volume is not applicable there, the work\nis easily avoidable, and the addition CPU and disk io load do not lead\nto succeeding retry.\n\nReviewed by:\tmckusick\nTested by:\tpho\nSponsored by:\tThe FreeBSD Foundation\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/4e01efcc0c917cfbefc61574b016fb62540e53e0"},{"sha":"e037bf91c2e70b633f526d71cfdc52d9ec001a6a","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"When looking up dandling buffers for unwing after failing block\nallocation in UFS_BALLOC(), there is no need to map them.\n\nReviewed by:\tmckusick\nSponsored by:\tThe FreeBSD Foundation\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/e037bf91c2e70b633f526d71cfdc52d9ec001a6a"},{"sha":"0aeae89e961290a23a4bb11c8cb5663a86933a88","author":{"name":"mckusick","email":"266c969ed9e3b126d3e11fa86e60f953da4ab5d0@FreeBSD.org"},"message":"Add two new macros, SLIST_CONCAT and LIST_CONCAT. Note in both the\nqueue.h header file and in the queue.3 manual page that they are O(n)\nso should be used only in low-usage paths with short lists (otherwise\nan STAILQ or TAILQ should be used).\n\nReviewed by: kib","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/0aeae89e961290a23a4bb11c8cb5663a86933a88"},{"sha":"fd0eaea7aace6c4cef38a33888ae2bb069ebb96f","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"On unwind after failed block allocation in ffs_balloc_ufs{1,2}, assert\nthat recorded allocated blocks numbers match the physical block\nnumbers of dandling buffers which are released.\n\nWhen finally freeing the blocks during unwind, assert that dandling\nbuffers where not re-allocated.  They shouldn't, because the vnode lock\nis owned exclusive.\n\nReviewed by:\tmckusick\nTested by:\tpho\nSponsored by:\tThe FreeBSD Foundation\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/fd0eaea7aace6c4cef38a33888ae2bb069ebb96f"},{"sha":"73de606a86ad376fda2f9906a4ad1e4e57d138d1","author":{"name":"kib","email":"ce9d581103e40ce1b4a3636d5281c849530292f7@FreeBSD.org"},"message":"In UFS_BALLOC(), invalidate pages of indirect buffers on failed block\nallocation unwinding.\n\nDandling buffers are released on UFS_BALLOC() failure to ensure that\nlater attempt to allocate blocks in close range do not find the blocks\nwith invalid content, since possible partial block allocations are\nunwound.  As such, it is not enough to just release the buffers, the\npages must also invalidated and removed from the vnode vm_object\nqueue.  Otherwise the pages might be found later and used to\nreconstruct indirect buffers when doing allocations at offset close to\nthe failure point, and their stale content compromise the filesystem\nintegrity.\n\nNote that just marking the buffer as B_INVAL is not enough, B_NOCACHE\nis required.  To be sure, clear the B_CACHE flag as well.  This\ncomplements the r174973, which started releasing buffers.\n\nReported and tested by:\tpho\nReviewed by:\tmckusick\nSponsored by:\tThe FreeBSD Foundation\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/73de606a86ad376fda2f9906a4ad1e4e57d138d1"},{"sha":"347d2809fde7f267fb609df0a6a58d388c241542","author":{"name":"markj","email":"47b3ed30e5a83fd756a28e99bf1950376aed42e8@FreeBSD.org"},"message":"Remove prototypes missed in r303951.","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/347d2809fde7f267fb609df0a6a58d388c241542"},{"sha":"1e7f2891b9cfb722b415bb7d6c62e5dbe7390a6e","author":{"name":"ngie","email":"305547d4cc311567c72a2740c290593f0de39607@FreeBSD.org"},"message":"Only expect :encode_tv_random_million to fail on 64-bit platforms\n\nIt passes on i386\n\nMFC after:\t1 week\nSponsored by:\tEMC / Isilon Storage Division","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/1e7f2891b9cfb722b415bb7d6c62e5dbe7390a6e"},{"sha":"d1132818f9b90ac2219a7967c49ca3ab69919393","author":{"name":"mckusick","email":"266c969ed9e3b126d3e11fa86e60f953da4ab5d0@FreeBSD.org"},"message":"Bug 211013 reports that a write error to a UFS filesystem running\nwith softupdates panics the kernel. The problem that has been pointed\nout is that when there is a transient write error on certain metadata\nblocks, specifically directory blocks (PAGEDEP), inode blocks\n(INODEDEP), indirect pointer blocks (INDIRDEPS), and cylinder group\n(BMSAFEMAP, but only when journaling is enabled), we get a panic\nin one of the routines called by softdep_disk_io_initiation that\nthe I/O is \"already started\" when we retry the write.\n\nThese dependency types potentially need to do roll-backs when called\nby softdep_disk_io_initiation before doing a write and then a\nroll-forward when called by softdep_disk_write_complete after the\nI/O completes.  The panic happens when there is a transient error.\nAt the top of softdep_disk_write_complete we check to see if the\nwrite had an error and if an error occurred we just return.  This\nreturn is correct most of the time because the main role of the routines\ncalled by softdep_disk_write_complete is to process the now-completed\ndependencies so that the next I/O steps can happen.\n\nBut for the four types listed above, they do not get to do their\nrollback operations. This causes the panic when softdep_disk_io_initiation\ngets called on the second attempt to do the write and the roll-back\nroutines find that the roll-backs have already been done. As an\naside I note that there is also the problem that the buffer will\nhave been unlocked and thus made visible to the filesystem and to\nuser applications with the roll-backs in place.\n\nThe way to resolve the problem is to add a flag to the routines called\nby softdep_disk_write_complete for the four dependency types noted\nthat indicates whether the write was successful (WRITESUCCEEDED).\nIf the write does not succeed, they do just the roll-backs and then\nreturn. If the write was successful they also do their usual\nprocessing of the now-completed dependencies.\n\nThe fix was tested by selectively injecting write errors for buffers\nholding dependencies of each of the four types noted above and then\nverifying that the kernel no longer paniced and that following the\nsuccessful retry of the write that the filesystem could be unmounted\nand successfully checked cleanly.\n\nPR: 211013\nReviewed by: kib","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/d1132818f9b90ac2219a7967c49ca3ab69919393"},{"sha":"298dc9cdcd2b391d1463fe328cd96dc490965514","author":{"name":"landonf","email":"56cee983e1ccd99bfa5a5fbe036a4765b0950d54@FreeBSD.org"},"message":"bhndb(4): Drop MIPS-incompatible __builtin_ctz dependency.\n\nThis replaces the bitfield representation of the bhndb register window\nfreelist with the bitstring API, eliminating a dependency on\n(MIPS-unsupported) __builtin_ctz().\n\nApproved by:\tadrian (mentor)\nDifferential Revision:\thttps://reviews.freebsd.org/D7495","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/298dc9cdcd2b391d1463fe328cd96dc490965514"},{"sha":"44059bbc9529cdd843733b722a4e125cee1de7d6","author":{"name":"landonf","email":"56cee983e1ccd99bfa5a5fbe036a4765b0950d54@FreeBSD.org"},"message":"bhnd(4): Implement NVRAM support required for PMU bring-up.\n\n- Added a generic bhnd_nvram_parser API, with support for the TLV format\n  used on WGT634U devices, the standard BCM NVRAM format used on most\n  modern devices, and the \"board text file\" format used on some hardware\n  to supply external NVRAM data at runtime (e.g. via an EFI variable).\n\n- Extended the bhnd_bus_if and bhnd_nvram_if interfaces to support both\n  string-based and primitive data type variable access, required for\n  common behavior across both SPROM and NVRAM data sources.\n- Extended the existing SPROM implementation to support the new\n  string-based NVRAM APIs.\n\n- Added an abstract bhnd_nvram driver, implementing the bhnd_nvram_if\n  atop the bhnd_nvram_parser API.\n- Added a CFE-based bhnd_nvram driver to provide read-only access to\n  NVRAM data on MIPS SoCs, pending implementation of a flash-aware\n  bhnd_nvram driver.\n\nApproved by:\tadrian (mentor)\nDifferential Revision:\thttps://reviews.freebsd.org/D7489","distinct":true,"url":"https://api.github.com/repos/Moteesh/freebsd/commits/44059bbc9529cdd843733b722a4e125cee1de7d6"}]}
{"actor":{"display_login":"Moteesh"}}