{"push_id":2553234216,"size":9,"distinct_size":9,"ref":"refs/heads/freebsd/current/master","head":"462a26d62e1ddc2495b963b3ad85733372a6505a","before":"fbbe5571b3295f80b2540efb7ce8c7174ecf66c0","commits":[{"sha":"2549fc5001f57deb2ef83dcd3c439dc4bd746c01","author":{"name":"araujo","email":"d43962b0ecc6fa2a514f5b58406ccb3c870bdd0e@FreeBSD.org"},"message":"Rework CTL frontend & backend options to use nv(3), allow creating multiple\nioctl frontend ports.\n\nThis revision introduces two changes to CTL:\n- Changes the way options are passed to CTL_LUN_REQ and CTL_PORT_REQ ioctls.\n  Removes ctl_be_arg structure and associated logic and replaces it with\n  nv(3)-based logic for passing in and out arguments.\n- Allows creating multiple ioctl frontend ports using either ctladm(8) or\n  ctld(8).\n  New frontend ports are represented by /dev/cam/ctl<pp>.<vp> nodes, eg /dev/cam/ctl5.3.\n  Those device nodes respond only to CTL_IO ioctl.\n\nNew command-line options for ctladm:\n# creates new ioctl frontend port with using free pp and vp=0\nctladm port -c\n# creates new ioctl frontend port with pp=10 and vp=0\nctladm port -c -O pp=10\n# creates new ioctl frontend port with pp=11 and vp=12\nctladm port -c -O pp=11 -O vp=12\n# removes port with number 4 (it's a \"targ_port\" number, not pp number)\nctladm port -r -p 4\n\nNew syntax for ctl.conf:\ntarget ... {\n    port ioctl/<pp>\n    ...\n}\n\ntarget ... {\n    port ioctl/<pp>/<vp>\n    ...\n\nNote: Most of this work was made by jceel@, thank you.\n\nSubmitted by:\tjceel\nReworked by:\tmyself\nReviewed by:\tmav (earlier versions and recently during the rework)\nObtained from:  FreeNAS and TrueOS\nRelnotes:\tYes\nSponsored by:\tiXsystems Inc.\nDifferential Revision:\thttps://reviews.freebsd.org/D9299","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/2549fc5001f57deb2ef83dcd3c439dc4bd746c01"},{"sha":"560fc649817de81176ea674720a636e79915b7df","author":{"name":"jhibbits","email":"3bae1b7d571c203acfb4d62748e2c04607e018fd@FreeBSD.org"},"message":"Fix PPC symbol resolution\n\nSummary:\nThere were 2 issues that were preventing correct symbol resolution\non PowerPC/pseries:\n\n1- memory corruption at chrp_attach() - this caused the inital\n   part of the symbol table to become zeroed, which would cause\n   the kernel linker to fail to parse it.\n   (this was probably zeroing out other memory parts as well)\n\n2- DDB symbol resolution wasn't working because symtab contained\n   not relocated addresses but it was given relocated offsets.\n   Although relocating the symbol table fixed this, it broke the\n   linker, that already handled this case.\n   Thus, the fix for this consists in adding a new DDB macro:\n   DB_STOFFS(offs) that converts a (potentially) relocated offset\n   into one that can be compared with symbol table values.\n\nPR:\t\t227093\nSubmitted by:\tLeandro Lupori <leandro.lupori_gmail.com>\nDifferential Revision: https://reviews.freebsd.org/D15372","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/560fc649817de81176ea674720a636e79915b7df"},{"sha":"33b588ad7df49ddc70d65b301a48457fa5771f40","author":{"name":"np","email":"003fffd5649fc27c0fc0d15a402a4fe5b0444ce7@FreeBSD.org"},"message":"cxgbe(4): Disable write-combined doorbells by default.\n\nThis had been the default behavior but was changed accidentally as part\nof the recent iw_cxgbe+OFED overhaul.  Fix another bug in that change\nwhile here: the global knob affects all the adapters in the system and\nshould be left alone by per-adapter code.\n\nMFC after:\t3 days\nSponsored by:\tChelsio Communications","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/33b588ad7df49ddc70d65b301a48457fa5771f40"},{"sha":"f29950c93537eaae9c96461cf1dcc65ea5a25e9b","author":{"name":"delphij","email":"93465216fd46a440eb04b27d6e009aced8b0c153@FreeBSD.org"},"message":"Remove \"All rights reserved\" from my files.\n\nSee r333391 for the rationale.\n\nMFC after:\t1 week","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/f29950c93537eaae9c96461cf1dcc65ea5a25e9b"},{"sha":"196546a6e65941065d19c1e728c5c6a5509ba184","author":{"name":"mw","email":"99c15d92ebc0e182e5c4df7c7e9e30ce96a863df@FreeBSD.org"},"message":"Upgrade ENA version to v0.8.1\n\nSubmitted by: Michal Krawczyk <mk@semihalf.com>\nObtained from: Semihalf\nSponsored by: Amazon, Inc.","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/196546a6e65941065d19c1e728c5c6a5509ba184"},{"sha":"18c1d537254f375055df4eaae6f11f685bbd364c","author":{"name":"mw","email":"99c15d92ebc0e182e5c4df7c7e9e30ce96a863df@FreeBSD.org"},"message":"Apply fixes in ena-com\n\n* Change ena-com BIT macro to work on unsigned value.\n  To make the shifting operations safer, they should be working on\n  unsigned values.\n\n* Fix a mutex not owned ASSERT panic in ENA control path.\n  A thread calling cv_broadcast()/cv_signal() must hold the mutex used for\n  cv_wait(). Fix the ENA control path code that has this problem.\n\nSubmitted by:   Krishna Yenduri <kyenduri@brkt.com>\nReviewed by:    Michal Krawczyk <mk@semihalf.com>\nTested by:      Michal Krawczyk <mk@semihalf.com>","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/18c1d537254f375055df4eaae6f11f685bbd364c"},{"sha":"e2ad139b86622c7be3d0b2f393479eb347393d78","author":{"name":"mw","email":"99c15d92ebc0e182e5c4df7c7e9e30ce96a863df@FreeBSD.org"},"message":"Skip setting the MTU for ENA if it is not changing\n\nOn AWS, a network interface can get reinitialized every 30 minutes due\nto the MTU being (re)set when a new DHCP lease is obtained. This can\ncause packet drop, along with annoying syslog messages.\n\nSkip setting the MTU in the ena driver if the new MTU is the same as the\nold MTU. Note this fix is already in the netfront driver.\n\nTesting: Verified ena up/down messages do not appear every 30 min in\n/var/log/messages with the fix in place.\n\nSubmitted by:   Krishna Yenduri <kyenduri@brkt.com>\nReviewed by: Michal Krawczyk <mk@semihalf.com>","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/e2ad139b86622c7be3d0b2f393479eb347393d78"},{"sha":"6caecdadde9d667125e71bcbe31b493f6a79843f","author":{"name":"manu","email":"158873d90a7ef40f3637a222b7329c09d0222554@FreeBSD.org"},"message":"arm64: Add ALT_BREAK_TO_DEBUGGER to GENERIC\n\nIt is useful to enter kdb with an escape sequence.\nWhile here move the USB_DEBUG with the others debug options and define\nnooptions USB_DEBUG for GENERIC-NODEBUG","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/6caecdadde9d667125e71bcbe31b493f6a79843f"},{"sha":"462a26d62e1ddc2495b963b3ad85733372a6505a","author":{"name":"mw","email":"99c15d92ebc0e182e5c4df7c7e9e30ce96a863df@FreeBSD.org"},"message":"Do not pass header length to the ENA controller\n\nHeader length is optional hint for the ENA device. Because It is not\nguaranteed that every packet header will be in the first mbuf\nsegment, it is better to skip passing any information. If the header\nlength will be indicating invalid value (different than 0), then the\npacket will be dropped.\n\nThis kind situation can appear, when the UDP packet will be fragmented\nby the stack in the ip_fragment() function.\n\nSubmitted by: Michal Krawczyk <mk@semihalf.com>\nReported by:  Krishna Yenduri <kyenduri@brkt.com>\nObtained from: Semihalf\nSponsored by: Amazon, Inc.","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/462a26d62e1ddc2495b963b3ad85733372a6505a"}]}
{"actor":{"display_login":"opntr-auto"}}