{"push_id":1142707762,"size":13,"distinct_size":1,"ref":"refs/heads/hardened/current/log","head":"8cef384dd6cf15b13320fc44732ac0d6073cc1ed","before":"848d693e72a9ce1912e2139e64b05ff92489ffa0","commits":[{"sha":"120a010498079d934ace3e789561c8fa5f8d692b","author":{"name":"andrew","email":"6b7c097d961f68685fc978cf91eeae17be6cbb45@FreeBSD.org"},"message":"Add an interface to handle interrupt controllers that have a contiguous\nrange of interrupts they pass to a second controller driver to handle.\nThe parent driver is expected to detect when one of these interrupts has\nbeen triggered and call intr_child_irq_handler to pass the interrupt to\na child. The children controllers are then expected to manage the range\nby allocating interrupts as needed.\n\nThis will initially be used by the ARM GICv3 driver, but is is expected to\nbe useful for other driver where this type of allocation applies.\n\nObtained from:\tABT Systems Ltd\nSponsored by:\tThe FreeBSD Foundation\nDifferential Revision:\thttps://reviews.freebsd.org/D6436","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/120a010498079d934ace3e789561c8fa5f8d692b"},{"sha":"a00165d816704b0ac2235fdeb0fce0e705654674","author":{"name":"andrew","email":"6b7c097d961f68685fc978cf91eeae17be6cbb45@FreeBSD.org"},"message":"Add the GICv3 ITS intrng driver. As the interface to the interrupt\nframework has significantly changed the driver has moved to a new file.\nWhile it shares some code with the existing driver this has been modified\nto work better with the intrng framework.\n\nThis has been tested on the ThunderX servers in the netperf cluster and has\nbeen used to boot them for other testing, including DTrace and hwpmc.\n\nWith this we can use intrng on all supported arm64 platforms I was able to\ntest on. It is expected we will move to intrng soon, and disable the old\narm64 interrupt framework.\n\nObtained from:\tABT Systems Ltd\nSponsored by:\tThe FreeBSD Foundation\nDifferential Revision:\thttps://reviews.freebsd.org/D6437","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/a00165d816704b0ac2235fdeb0fce0e705654674"},{"sha":"5583bfd183d3dbc2cd7d479de8eddb7e58420734","author":{"name":"skra","email":"325d1d0866bcffc45ec6f33248f0ccfec829fa93@FreeBSD.org"},"message":"Postpone allocation of IRQ resource to the time when interrupt\ncontroller devices are attached. This has already been done for\nbus_setup_intr().\n\nThere was no doubt that if someone wants to setup an interrupt,\ncorresponding interrupt controller device must already be attached.\nHowever, the same must be valid for allocation of an interrupt resource\nunless the allocation is done blindly, without any information that\nsuch interrupt even exists. While it was done this blind way before,\nit won't be possible after next INTRNG change.","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/5583bfd183d3dbc2cd7d479de8eddb7e58420734"},{"sha":"edf0e66e31d85cbc18783ea275a2d14f43646742","author":{"name":"skra","email":"325d1d0866bcffc45ec6f33248f0ccfec829fa93@FreeBSD.org"},"message":"Define irq variable only in the block where used.","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/edf0e66e31d85cbc18783ea275a2d14f43646742"},{"sha":"75d860b725166d5562ea3732397649572e435e41","author":{"name":"royger","email":"bd2e32ed1e094e43d302dc446ba6468ce6a7b524@FreeBSD.org"},"message":"blkback: add support for hotplug scripts\n\nHotplug scripts are needed in order to use fancy disk configurations in xl,\nlike iSCSI disks. The job of hotplug scripts is to locally attach the disk\nand present it to blkback as a block device or a regular file.\n\nThis change introduces a new xenstore node in the blkback hierarchy, called\n\"physical-device-path\". This is a straigh replacement for the \"params\" node,\nwhich was used before.\n\nHotplug scripts will need to read the \"params\" node, perform whatever\nactions are necessary and then write the \"physical-device-path\" node. The\nhotplug script is also in charge of detaching the disk once the domain has\nbeen shutdown.\n\nSponsored by: Citrix Systems R&D","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/75d860b725166d5562ea3732397649572e435e41"},{"sha":"28ea44dac8d1daa2b1d50448cbbb48c2f51045fd","author":{"name":"royger","email":"bd2e32ed1e094e43d302dc446ba6468ce6a7b524@FreeBSD.org"},"message":"xen-blkback: fix error path on failed attach\n\nThe current error path in case of failure during attach/initialization is\nnot correct and leaves blkback in a stuck state. This is due to blkback\nwaiting for blkfront to switch to state XenbusStateClosed, but if blkfront\nnever attached (because the guest is not even started) it cannot possibly\nmake it to that state.\n\nInstead just wait for the frontend to be in a state different than\nXenbusStateConnected in order to proceed with the shutdown. Also, it is\nwrong to call xbb_detach directly because it destroys the lock which can\nstill be used by xbb_frontend_changed.\n\nSponsored by: Citrix Systems R&D","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/28ea44dac8d1daa2b1d50448cbbb48c2f51045fd"},{"sha":"69cdb2137c13e36cbc467dd745ab15126fc22063","author":{"name":"bz","email":"0882102703f32cc323693fb9c179adcb3c0e971b@FreeBSD.org"},"message":"Introduce a per-VNET flag to enable/disable netisr prcessing on that VNET.\nAdd accessor functions to toggle the state per VNET.\nThe base system (vnet0) will always enable itself with the normal\nregistration. We will share the registered protocol handlers in all\nVNETs minimising duplication and management.\nUpon disabling netisr processing for a VNET drain the netisr queue from\npackets for that VNET.\n\nUpdate netisr consumers to (de)register on a per-VNET start/teardown using\nVNET_SYS(UN)INIT functionality.\n\nThe change should be transparent for non-VIMAGE kernels.\n\nReviewed by:\tgnn (, hiren)\nObtained from:\tprojects/vnet\nMFC after:\t2 weeks\nSponsored by:\tThe FreeBSD Foundation\nDifferential Revision:\thttps://reviews.freebsd.org/D6691","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/69cdb2137c13e36cbc467dd745ab15126fc22063"},{"sha":"1926b48f81a36f9b0d9915e77daa7e1191646071","author":{"name":"avg","email":"b24d11afb16644e3ff52469bebd6e863d3282d4e@FreeBSD.org"},"message":"openssl: change SHLIB_VERSION_NUMBER to reflect the reality\n\nSome consumers actually use this definition.\n\nWe probably need some procedure to ensure that SHLIB_VERSION_NUMBER\nis updated whenever we change the library version in\nsecure/lib/libssl/Makefile.","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/1926b48f81a36f9b0d9915e77daa7e1191646071"},{"sha":"3ad48fe4cf3af65f4d0b06a73053646934078914","author":{"name":"avg","email":"b24d11afb16644e3ff52469bebd6e863d3282d4e@FreeBSD.org"},"message":"zfs_root: fix a potential root vnode reference leak\n\nIt could happen in an unlikely case that we fail to lock the root vnode\nwith requested flags (which appear to never include LK_NOWAIT).\n\nMFC after:\t1 week","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/3ad48fe4cf3af65f4d0b06a73053646934078914"},{"sha":"c46e1b80b9c6160967bf2db2289a277529a4d2ad","author":{"name":"vangyzen","email":"432b6b09e7c190dd67aae7b18be069071a5e8858@FreeBSD.org"},"message":"Improve errno documentation in pthread_create(3) and thr_new(2)\n\nAdd some missing errno values to thr_new(2) and pthread_create(3).\nIn particular, EDEADLK was not documented in the latter.\nWhile I'm here, improve some English and cross-references.\n\nReviewed by:\tkib\nSponsored by:\tDell Inc.\nDifferential Revision:\thttps://reviews.freebsd.org/D6663","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/c46e1b80b9c6160967bf2db2289a277529a4d2ad"},{"sha":"3184a6cb731f764b0552a4901ca4f95ee41f6536","author":{"name":"avg","email":"b24d11afb16644e3ff52469bebd6e863d3282d4e@FreeBSD.org"},"message":"zfs: set VROOT / VV_ROOT consistently and in a single place\n\nThis is a followup to r300131.\n\nA filesystem's root vnode can be reached not only through VSF_ROOT, but\nby other means as well.  For example, via a dot-dot lookup.\nAlso, a root vnode can get reclaimed and then re-created.  For these\nreasons it was insufficient to clear VV_ROOT flag from a root vnode of a\nsnapshot mounted under .zfs in zfsctl_snapdir_lookup().\n\nSo, now we set the flag in zfs_znode_sa_init() only if a vnode\nrepresent a root of a filesystem or a standalone snapshot.\nThat is, the flag is not set for snapshots mounted under .zfs.\n\nMFC after:\t2 weeks","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/3184a6cb731f764b0552a4901ca4f95ee41f6536"},{"sha":"4975ce34392512f59051d4c2e90e2e3b51e8f448","author":{"name":"Oliver Pinter +","email":"924fd90530ea0369cfaf1274bf61a797817afd0e@hardenedbsd.org"},"message":"Merge branch 'freebsd/current/master' into hardened/current/master","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/4975ce34392512f59051d4c2e90e2e3b51e8f448"},{"sha":"8cef384dd6cf15b13320fc44732ac0d6073cc1ed","author":{"name":"Oliver Pinter +","email":"924fd90530ea0369cfaf1274bf61a797817afd0e@hardenedbsd.org"},"message":"Merge remote-tracking branch 'origin/hardened/current/master' into hardened/current/log","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/8cef384dd6cf15b13320fc44732ac0d6073cc1ed"}]}
{"actor":{"display_login":"opntr-auto"}}