------------------------------------------------------------------------ r363918 | markj | 2020-08-05 10:07:13 -0700 (Wed, 05 Aug 2020) | 10 lines MFC r363917: Fix a TOCTOU vulnerability in freebsd32_copyin_control(). PR: 248257 Reported by: m00nbsd working with Trend Micro Zero Day Initiative Reviewed by: kib Security: SA-20:23.sendmsg Security: CVE-2020-7460 Security: ZDI-CAN-11543 ------------------------------------------------------------------------ r363940 | kevans | 2020-08-05 21:52:30 -0700 (Wed, 05 Aug 2020) | 6 lines MFC r363421: pkg-bootstrap: complain on improper `pkg bootstrap` usage Right now, the bootstrap will gloss over things like pkg bootstrap -x or pkg bootstrap -f pkg. Make it more clear that this is incorrect, and hint at the correct formatting. ------------------------------------------------------------------------ r363941 | kevans | 2020-08-05 21:54:59 -0700 (Wed, 05 Aug 2020) | 7 lines MFC r363409: libbe: annotate lbh as __unused in be_is_auto_snapshot_name lbh is included for consistency with other functions and in case future work needs to use it, but it is currently unused. Mark it, and a post-OpenZFS-import world will be able to raise WARNS of libbe to the default (pending some minor changes to openzfs libzfs). ------------------------------------------------------------------------ r363944 | avg | 2020-08-06 01:06:07 -0700 (Thu, 06 Aug 2020) | 19 lines MFC r362042: iicbb: rebuild the bit-banging algorithms using different primitives I2C_SET was quite inflexible, it used too long delays as well as some unnecessary delays. The new building blocks are iicbb_clockin and iicbb_clockout. The former sets SDA and starts the high period of SCL, the latter executes the low period of SCL. What happens during the high phase depends on the operation. For writes we just hold both lines, for reads we poll SDA. S, Sr and P change SDA in the middle of the high period. Also, the calculation of udelay has been updated, so that the resulting period more closely corresponds the requested bus frequency. There is a new knob, io_delay, that allows to further adjust udelay based on the estimated latency of pin toggling operations. Finally, I slightly changed debug tracing and added error indicators to it. The debug prints are compiled in but disabled by default. This can be of use if there is any fallout from this change. ------------------------------------------------------------------------ r363947 | kib | 2020-08-06 03:12:39 -0700 (Thu, 06 Aug 2020) | 5 lines MFC r248454: Provide more correct description for sysctl kern.smp.cores. PR: 248454 ------------------------------------------------------------------------ r363952 | markj | 2020-08-06 07:07:49 -0700 (Thu, 06 Aug 2020) | 5 lines MFC r363447: MFOpenZFS: Fix zpool history unbounded memory usage PR: 247557 ------------------------------------------------------------------------ r363953 | markj | 2020-08-06 07:08:23 -0700 (Thu, 06 Aug 2020) | 3 lines MFC r363682: Fix a logic error in uipc_ready_scan(). ------------------------------------------------------------------------ r363956 | mav | 2020-08-06 08:20:31 -0700 (Thu, 06 Aug 2020) | 2 lines MFC r340071: Adjust SiS 966/968 HDA controller naming. ------------------------------------------------------------------------ r363957 | mav | 2020-08-06 08:23:51 -0700 (Thu, 06 Aug 2020) | 3 lines MFC r354143 (by scottl): Add device IDs for the next generation of Intel HDA audio. ------------------------------------------------------------------------ r363958 | mav | 2020-08-06 08:25:11 -0700 (Thu, 06 Aug 2020) | 2 lines MFC r355429 (by scottl): Add support for new sound HDA hardware ------------------------------------------------------------------------ r363973 | kevans | 2020-08-06 11:13:45 -0700 (Thu, 06 Aug 2020) | 37 lines MFC r361720, r362787: Simplify mailer.conf installation r361720: pkgbase: resolve mailer.conf conflict WITHOUT_SENDMAIL When WITHOUT_SENDMAIL is set, we end up with two different mailer.conf that conflict, and hilarity ensues. There's currently three different places that we might install mailer.conf: - ^/etc/Makefile (package=runtime, contingent on MK_MAIL != no) - ^/libexec/dma/dmagent/Makefile (package=dma, contingent on MK_SENDMAIL != no) - ^/usr.sbin/mailwrapper/Makefile (package=utilities, contingent on not-installed) The mailwrapper installation will effectively never happen because the ^/etc one will first. This patch simplifies the whole situation; remove the ^/etc/Makefile version and install it primarily in mailwrapper if MK_MAILWRAPPER != "no". The scenarios covered in mailwrapper are: - sendmail(8) is installed, dma(8) may or may not be installed - neither sendmail(8) nor dma(8) is installed In the first scenario, sendmail(8) is dominant so we can go ahead and install the version in ^/etc/mail. In the unlisted scenario, sendmail(8) is not installed but dma(8) is, we'll let ^/libexec/dma/dmagent do the installation. In the second listed scenario, we still want to install an example mailer.conf so just install the base sendmail(8) version. r362787: mailwrapper: switch mailer.conf to CONFS This matches what was already being done in dma(8), and should again make this merge with etcupdate/mergemaster. ------------------------------------------------------------------------ r363974 | kevans | 2020-08-06 11:17:19 -0700 (Thu, 06 Aug 2020) | 16 lines MFC r363692: diff: fix side_by_side It's currently unclear to me how this could have worked previously; \n here is not a literal newline but actual '\' 'n', and was getting passed to the underlying regex engine as such. regex(3) does not translate this to a newline, and this became an error because we don't really allow escaping of arbitrary ordinary characters anymore. Run the pattern strings through printf to make sure we're dealing with real newlines before passing them through to atf_check, which ultimately feeds them directly to regcomp(3). This fix is different than that will be needed for sed, in that this is the proper way to inject newlines into search strings as long as regex(3) won't combine \ + n as folks might expect. ------------------------------------------------------------------------ r363990 | alfredo | 2020-08-06 13:44:18 -0700 (Thu, 06 Aug 2020) | 10 lines MFC r363020: test: add libkvm read test This test checks if value received from kvm_read is sane, based on value returned by sysctl interface. Reviewed by: jhb Approved by: jhibbits (mentor) Sponsored by: Eldorado Research Institute (eldorado.org.br) Differential Revision: https://reviews.freebsd.org/D23783 ------------------------------------------------------------------------ r363998 | mav | 2020-08-06 17:26:16 -0700 (Thu, 06 Aug 2020) | 13 lines MFC r363490: Make lapic_ipi_vectored(APIC_IPI_DEST_SELF) NMI safe. Sending IPI to self or all CPUs does not require write into upper part of the ICR, prone to races. Previously the code disabled interrupts, but it was not enough for NMIs. Instead of that when possible write only lower part of the register, or use special SELF IPI register in x2APIC mode. This also removes ICR reads used to preserve reserved bits on write. It was there from the beginning, but I failed to find explanation why, neither I see Linux doing it. Specification even tells that ICR content may be lost in deep C-states, so if hardware does not bother to preserve it, why should we? ------------------------------------------------------------------------ r363999 | mav | 2020-08-06 17:33:28 -0700 (Thu, 06 Aug 2020) | 7 lines MFC r363495: Introduce ipi_self_from_nmi(). It allows safe IPI sending to current CPU from NMI context. Unlike other ipi_*() functions this waits for delivery to leave LAPIC in a state safe for interrupted code. ------------------------------------------------------------------------ r364000 | mav | 2020-08-06 17:40:28 -0700 (Thu, 06 Aug 2020) | 10 lines MFC r363527: Allow swi_sched() to be called from NMI context. For purposes of handling hardware error reported via NMIs I need a way to escape NMI context, being too restrictive to do something significant. To do it this change introduces new swi_sched() flag SWI_FROMNMI, making it careful about used KPIs. On platforms allowing IPI sending from NMI context (x86 for now) it immediately wakes clk_intr_event via new IPI_SWI, otherwise it works just like SWI_DELAY. ------------------------------------------------------------------------ r364001 | mav | 2020-08-06 17:50:41 -0700 (Thu, 06 Aug 2020) | 2 lines Fix build after r363999. ------------------------------------------------------------------------ r364002 | mav | 2020-08-06 17:56:20 -0700 (Thu, 06 Aug 2020) | 21 lines MFC r360328 (by vangyzen): Fix handling of NMIs from unknown sources (BMC, hypervisor) Release kernels have no KDB backends enabled, so they discard an NMI if it is not due to a hardware failure. This includes NMIs from IPMI BMCs and hypervisors. Furthermore, the interaction of panic_on_nmi, kdb_on_nmi, and debugger_on_panic is confusing. Respond to all NMIs according to panic_on_nmi and debugger_on_panic. Remove kdb_on_nmi. Expand the meaning of panic_on_nmi by making it a bitfield. There are currently two bits: one for NMIs due to hardware failure, and one for all others. Leave room for more. If panic_on_nmi and debugger_on_panic are both true, don't actually panic, but directly enter the debugger, to allow someone to leave the debugger and [hopefully] resume normal execution. Relnotes: yes: machdep.kdb_on_nmi is gone; machdep.panic_on_nmi changed ------------------------------------------------------------------------ r364003 | mav | 2020-08-06 18:05:10 -0700 (Thu, 06 Aug 2020) | 21 lines MFC r363624: Add initial driver for ACPI Platform Error Interfaces. APEI allows platform to report different kinds of errors to OS in several ways. We've found that Supermicro X10/X11 motherboards report PCIe errors appearing on hot-unplug via this interface using NMI. Without respective driver it ended up in kernel panic without any additional information. This driver introduces support for the APEI Generic Hardware Error Source reporting via NMI, SCI or polling. It decodes the reported errors and either pass them to pci(4) for processing or just logs otherwise. Errors marked as fatal still end up in kernel panic, but some more informative. When somebody get to native PCIe AER support implementation both of the reporting mechanisms should get common error recovery code. Since in our case errors happen when the device is already gone, there is nothing to recover, so the code just clears the error statuses, practically ignoring the otherwise destructive NMIs in nicer way. Relnotes: yes Sponsored by: iXsystems, Inc. ------------------------------------------------------------------------ r364007 | 0mp | 2020-08-07 02:50:44 -0700 (Fri, 07 Aug 2020) | 7 lines MFC 363737: Point to rc(8) for more details about the autoboot variable Reviewed by: bcr, imp Differential Revision: https://reviews.freebsd.org/D25904 ------------------------------------------------------------------------ r364014 | markj | 2020-08-07 06:40:49 -0700 (Fri, 07 Aug 2020) | 5 lines MFC r363735: ng_iface(4): Set the current VNET before calling netisr_dispatch(). PR: 242406 ------------------------------------------------------------------------ r364015 | markj | 2020-08-07 06:42:47 -0700 (Fri, 07 Aug 2020) | 3 lines MFC r363736: ng_iface(4): Remove unsupported protocols. ------------------------------------------------------------------------ r364016 | gbe | 2020-08-07 08:03:20 -0700 (Fri, 07 Aug 2020) | 12 lines MFC r363291: devstat(9): Update the man page to reflect the current implementation - Rename devstat_add_entry to devstat_new_entry - Update the description of devstat_trans_flags - Add manpage aliases for devstat_start_transaction_bio and devstat_end_transaction_bio PR: 157316 Submitted by: novel Reviewed by: cem, bcr Approved by: bcr Differential Revision: https://reviews.freebsd.org/D25677 ------------------------------------------------------------------------ r364017 | gbe | 2020-08-07 08:11:27 -0700 (Fri, 07 Aug 2020) | 6 lines MFC r362230: libcasper(3): Document HISTORY within the manpages Reviewed by: bcr Approved by: bcr Differential Revision: https://reviews.freebsd.org/D24695 ------------------------------------------------------------------------ r364020 | mav | 2020-08-07 08:58:23 -0700 (Fri, 07 Aug 2020) | 2 lines Fix bug in r363624 12 adaptation. ------------------------------------------------------------------------ r364033 | mav | 2020-08-07 10:32:53 -0700 (Fri, 07 Aug 2020) | 19 lines MFC r362661: Add mostly dummy hw.pci.enable_aspm tunable. The only thing this tunable enables now is reporting to ACPI _OSC that Active State Power Management and Clock Power Management Capability are "supported" by the OS. I've found that at least some Supermicro server boards do not allow OS to support native PCIe hot-plug unless it reports those capabilities. After spending significant time in PCIe specs I have found very little motivation for that, and none of it applies to those motherboards, not enabling ASPM themselves. So unless OS explicitly wants to save power, I see nothing for it to do there actually. I guess it may get sense to support ASPM when we get Thunderbolt support. Otherwise I have no system with PCIe hot-plug where power saving matters. It would be nice to enable this by default, but I worry that it affect power saving of some laptops, even though I haven't noticed that myself. ------------------------------------------------------------------------ r364047 | mjg | 2020-08-07 16:31:45 -0700 (Fri, 07 Aug 2020) | 6 lines MFC r363855,r363890,r363891 cache: add missing numcache detrement on insertion failure cache: convert ncnegnash into a macro cache: reduce zone alignment to 8 bytes ------------------------------------------------------------------------ r364048 | mjg | 2020-08-07 16:32:42 -0700 (Fri, 07 Aug 2020) | 4 lines MFC r363931: vfs hash: annotate the lock with __exclusive_cache_line ------------------------------------------------------------------------ r364052 | se | 2020-08-08 09:41:28 -0700 (Sat, 08 Aug 2020) | 34 lines MFC: 362681, 362697, 362914, 362984, 362986, 362987, 363091, 363172, 363809, 363810, 363811, 363915 Import new 2-clause BSD licenced implementation of the bc and dc commands These implementations of the bc and dc programs offer a number of advantages compared to the current implementations in the FreeBSD base system: - They do not depend on external large number functions (i.e. no dependency on OpenSSL or any other large-number library) - They implements all features found in GNU bc/dc (with the exception of the forking of sub-processes in dc, which the author of this version considers a security issue). - They are significantly faster than the current code in base (more than 2 orders of magnitude in some of my tests, e.g. for 12345^100000). - They should be fully compatible with all features and the behavior of the current implementations in FreeBSD (not formally verified). - They support POSIX message catalogs and come with localized messages in Chinese, Dutch, English, French, German, Japanese, Polish, Portuguese, and Russian. - They offer very detailed man-pages that provide far more information than the current ones. This code is not built and installed in FreeBSD-12, unless WITH_GH_BC=yes is set (e.g. in src.conf) during builworld and installworld. It has been imported and made the default in FreeBSD-CURRENT, and all improvements and changes requested for the version in -CURRENT are included in this initial import into a stable branch. ------------------------------------------------------------------------ r364059 | mav | 2020-08-09 17:43:43 -0700 (Sun, 09 Aug 2020) | 5 lines MFC r364013: Allow ACPI APEI driver build without PCI. On x86 it seems difficult to build ACPI without PCI, but some aarch64 users appears to be doing it. ------------------------------------------------------------------------ r364060 | markj | 2020-08-09 19:39:42 -0700 (Sun, 09 Aug 2020) | 3 lines MFC r363880 (by lwhsu): Appease gcc's -Wparentheses (and -Werror) ------------------------------------------------------------------------ r364061 | gbe | 2020-08-09 23:19:33 -0700 (Sun, 09 Aug 2020) | 8 lines MFC r364021: grep(1): correct typos for 'if a name patches' to 'if a name matches' PR: 237635 Submitted by: durin42 Reviewed by: kevans Approved by: kevans Differential Revision: https://reviews.freebsd.org/D25994 ------------------------------------------------------------------------ r364074 | kib | 2020-08-10 03:52:54 -0700 (Mon, 10 Aug 2020) | 3 lines MFC r363813: Add SOL_LOCAL symbolic constant for unix socket option level. ------------------------------------------------------------------------ r364084 | dim | 2020-08-10 10:35:58 -0700 (Mon, 10 Aug 2020) | 11 lines MFC r363988: Fix clang 11 -Wformat warnings in yp_mkdb: usr.sbin/yp_mkdb/yp_mkdb.c:91:40: error: format specifies type 'char *' but the argument has type 'void *' [-Werror,-Wformat] printf("%.*s %.*s\n", (int)key.size, key.data, (int)data.size, ~~~~ ^~~~~~~~ usr.sbin/yp_mkdb/yp_mkdb.c:92:7: error: format specifies type 'char *' but the argument has type 'void *' [-Werror,-Wformat] data.data); ^~~~~~~~~ ------------------------------------------------------------------------ r364085 | vmaffione | 2020-08-10 10:53:09 -0700 (Mon, 10 Aug 2020) | 16 lines MFC r363378 iflib: initialize netmap with the correct number of descriptors In case the network device has a RX or TX control queue, the correct number of TX/RX descriptors is contained in the second entry of the isc_ntxd (or isc_nrxd) array, rather than in the first entry. This case is correctly handled by iflib_device_register() and iflib_pseudo_register(), but not by iflib_netmap_attach(). If the first entry is larger than the second, this can result in a panic. This change fixes the bug by introducing two helper functions that also lead to some code simplification. PR: 247647 Differential Revision: https://reviews.freebsd.org/D25541 ------------------------------------------------------------------------ r364087 | brooks | 2020-08-10 11:26:18 -0700 (Mon, 10 Aug 2020) | 13 lines MFC r363966: Preserve ASLR vm_map flags across fork In the most common case (fork+execve) this doesn't matter, but further attempts to apply entropy would fail in (e.g.) a pre-fork server. Reported by: Alfredo Mazzinghi Reviewed by: kib, markj Obtained from: CheriBSD Sponsored by: DARPA Differential Revision: https://reviews.freebsd.org/D25966 ------------------------------------------------------------------------ r364093 | mav | 2020-08-10 17:41:48 -0700 (Mon, 10 Aug 2020) | 7 lines MFC r363852: Remove extra memset() left after r342388. This memset() wiped MPI2_FUNCTION_SCSI_TASK_MGMT set by mprsas_alloc_tm(), that broke target reset on device removal, making later re-insertion into the same slot impossible, since firmware was still waiting for the driver to finish with the removed device. ------------------------------------------------------------------------ r364097 | rmacklem | 2020-08-10 22:10:01 -0700 (Mon, 10 Aug 2020) | 15 lines MFC: r363210 Fix the pNFS flexible file layout client for servers with small write size. The code in nfscl_dofflayout() loops when a flexible file layout server provides a small write data limit (no extant server is known to do this). If/when it looped, it erroneously reused the "drpc" argument for the mirror worker thread, corrupting it. This patch fixes the problem by only using the calling thread after the first loop iteration. Found during testing by simulating a server with a small write size. Since no extant pNFS server is known to provide a small write size, this fix it not needed in practice at this time. ------------------------------------------------------------------------ r364105 | gbe | 2020-08-11 03:41:36 -0700 (Tue, 11 Aug 2020) | 8 lines MFC r363830: iovctl.conf(5): Use Lk macro for the URL of the UCL website PR: 248334 Submitted by: chuck at tuffli dot net Reviewed by: bcr, 0mp Approved by: bcr, 0mp Differential Revision: https://reviews.freebsd.org/D25891 ------------------------------------------------------------------------ r364106 | gbe | 2020-08-11 03:56:44 -0700 (Tue, 11 Aug 2020) | 13 lines MFC r363829: directory(3): Add an ERRORS section - Add an ERRORS section for opendir(3) and closedir(3) - Document also the errors of readdir(3), readdir_r(3) and telldir(3) - Convert the code sample into an EXAMPLES section PR: 75711 Submitted by: abc Reviewed by: 0mp, bcr, jilles Approved by: 0mp, bcr, jilles Obtained from: partial from OpenBSD Differential Revision: https://reviews.freebsd.org/D25892 ------------------------------------------------------------------------ r364107 | eugen | 2020-08-11 04:32:44 -0700 (Tue, 11 Aug 2020) | 19 lines MFC r363064,363067,363081,363136: optimize install(1) a bit. Currently, "install -s -S" behaviour is inefficient for upgrade. First it finds that destination file already exists and copies source file to temporary file. Then it calls strip(1) with name of temporary file as single agrument and our strip(1) creates another temporary file in the /tmp (or TMPDIR) making another copy that is finally copied to DESTDIR third time. Meantime, strip(1) has an option "-o dst" to specify destination so install(1) is allowed to skip initial copying from obj to DESTDIR. This change makes it do so. This optimization descreases total amount of data sent to both of /tmp and DESTDIR during "make installworld" by 32% or so. See the differential for details. Differential Revision: https://reviews.freebsd.org/D25551 ------------------------------------------------------------------------ r364111 | markj | 2020-08-11 06:51:48 -0700 (Tue, 11 Aug 2020) | 3 lines MFC r363841: Remove an incorrect assertion from in6p_lookup_mcast_ifp(). ------------------------------------------------------------------------ r364114 | trasz | 2020-08-11 08:05:02 -0700 (Tue, 11 Aug 2020) | 6 lines MFC r355130: Fix typos. Sponsored by: Klara, Inc. ------------------------------------------------------------------------ r364115 | trasz | 2020-08-11 08:07:27 -0700 (Tue, 11 Aug 2020) | 8 lines MFC r355751: Add 'sesutil show' subcommand to show enclosure and its contents in a user-friendly way. Relnotes: yes Sponsored by: Klara, Inc. ------------------------------------------------------------------------ r364116 | trasz | 2020-08-11 08:08:32 -0700 (Tue, 11 Aug 2020) | 7 lines MFC r362807: Fix misplaced voltages/temperatures labels in 'sesutil show'. PR: bin/247384 Reported by: brd ------------------------------------------------------------------------ r364126 | gshapiro | 2020-08-11 10:51:31 -0700 (Tue, 11 Aug 2020) | 3 lines MFC: Mirror recommendation from Handbook to avoid linking conflicts when pulling in SASL libraries. (r363750) ------------------------------------------------------------------------ r364128 | markj | 2020-08-11 10:54:10 -0700 (Tue, 11 Aug 2020) | 5 lines MFC r350885 (by avos): rtwn_pci: add device ID for RTL8192CE. PR: 239795 ------------------------------------------------------------------------ r364136 | mav | 2020-08-11 19:05:33 -0700 (Tue, 11 Aug 2020) | 2 lines MFC r364037: Add some more checks to make APEI driver more robust. ------------------------------------------------------------------------ r364142 | gbe | 2020-08-12 00:00:06 -0700 (Wed, 12 Aug 2020) | 12 lines MFC r363907: environ(7): Update the description and include some more environment variables - Add a better introduction to the DESCRIPTION section - Add a description for MANPATH and POSIXLY_CORRECT - Asorted improvements for the usage of some macros PR: 43823 Submitted by: Lyndon Nerenberg Reviewed by: 0mp, bcr Approved by: 0mp, bcr Differential Revision: https://reviews.freebsd.org/D25912 ------------------------------------------------------------------------ r364150 | kaktus | 2020-08-12 03:03:10 -0700 (Wed, 12 Aug 2020) | 4 lines MFC userland part of r351729 Add sysctlbyname system call ------------------------------------------------------------------------ r364151 | eugen | 2020-08-12 03:11:34 -0700 (Wed, 12 Aug 2020) | 5 lines MFC r363889: bsnmptools: make it print protocol errors to stderr instead of stdout Reviewed by: syrinx, bz Differential Revision: https://reviews.freebsd.org/D25911 ------------------------------------------------------------------------ r364156 | ae | 2020-08-12 04:42:36 -0700 (Wed, 12 Aug 2020) | 3 lines MFC r363904: Fix SIGSEGV in ipfw(8) when NAT64 prefix length is omitted. ------------------------------------------------------------------------ r364157 | ae | 2020-08-12 04:43:43 -0700 (Wed, 12 Aug 2020) | 3 lines MFC r363900: Fix typo. ------------------------------------------------------------------------ r364158 | ae | 2020-08-12 04:48:19 -0700 (Wed, 12 Aug 2020) | 17 lines MFC r363888: Handle delayed checksums if needed in NAT64. Upper level protocols defer checksums calculation in hope we have checksums offloading in a network card. CSUM_DELAY_DATA flag is used to determine that checksum calculation was deferred. And IP output routine checks for this flag before pass mbuf to lower layer. Forwarded packets have not this flag. NAT64 uses checksums adjustment when it translates IP headers. In most cases NAT64 is used for forwarded packets, but in case when it handles locally originated packets we need to finish checksum calculation that was deferred to correctly adjust it. Add check for presence of CSUM_DELAY_DATA flag and finish checksum calculation before adjustment. ------------------------------------------------------------------------ r364159 | ae | 2020-08-12 04:49:35 -0700 (Wed, 12 Aug 2020) | 3 lines MFC r363906: Add m__getjcl SDT probe. ------------------------------------------------------------------------ r364169 | mav | 2020-08-12 09:16:17 -0700 (Wed, 12 Aug 2020) | 5 lines MFC r356321 (by markj): Take the ifnet's address lock in igmp_v3_cancel_link_timers(). inm_rele_locked() may remove the multicast address associated with inm. ------------------------------------------------------------------------ r364183 | mav | 2020-08-12 17:40:40 -0700 (Wed, 12 Aug 2020) | 2 lines MFC r363955: Add Intel Apollo Lake AHCI ID. ------------------------------------------------------------------------ r364184 | mav | 2020-08-12 17:42:09 -0700 (Wed, 12 Aug 2020) | 9 lines MFC r363979: Add CTL support for REPORT IDENTIFYING INFORMATION command. It allows to report to initiator LU identifying information, preset via "ident_info" and "text_ident_info" options. Unfortunately it is impossible to implement SET IDENTIFYING INFORMATION, since we have no persistent storage it requires, so the information is read-only for initiator and has to be set out-of-band. ------------------------------------------------------------------------