FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F11.1.0 2017-06-07T11:39:52Z 2017-06-07T11:39:52Z Konstantin Belousov kib@FreeBSD.org 2017-06-07T11:39:52Z urn:sha1:e92e3cdd9bda98398402501dd666e744e7fe495b Use __BSD_VISIBLE test instead checking for absense of _POSIX_SOURCE. Approved by: re (marius) 2017-06-01T14:49:53Z Eric van Gyzen vangyzen@FreeBSD.org 2017-06-01T14:49:53Z urn:sha1:bfccc82170863098c1277c536e8e3d42a9a229d8 libthr: fix warnings at WARNS=6 Fix warnings about the following when WARNS=6 (which I will commit soon): - casting away const - no previous 'extern' declaration for non-static variable - others as explained by #pragmas and comments - unused parameters libthr: disable thread-safety warnings These warnings don't make sense for code that implements the locking primitives. libthr: change CHECK_AND_INIT_RWLOCK to an inline function This was prompted by a compiler warning about 'ret' shadowing a local variable in the callers of the macro. libthr: Use CLI flags instead of pragmas to disable warnings People tweaking the build system or compilers tend to look into the Makefile and not into the source. Having some warning controls in the Makefile and some in the source code is surprising. Pragmas have the advantage that they leave the warnings enabled for more code, but that advantage isn't very relevant in these cases. libthr: fix warnings from GCC when WARNS=6 Fix warnings about: - redundant declarations - a local variable shadowing a global function (dlinfo) - an old-style function definition (with an empty parameter list) - a variable that is possibly used uninitialized libthr: prevent setcontext() from masking SIGTHR __thr_setcontext() mistakenly tested for the presence of SIGCANCEL in its local ucontext_t instead of the parameter. Therefore, if a thread calls setcontext() with a context whose signal mask contains SIGTHR (a.k.a. SIGCANCEL), that signal will be blocked, preventing the thread from being cancelled or suspended. Sponsored by: Dell EMC 2017-05-31T06:47:56Z Xin LI delphij@FreeBSD.org 2017-05-31T06:47:56Z urn:sha1:4e19e4c1ec30d9b617ce6c66287366c465739123 Add timingsafe_bcmp and timingsafe_memcmp. Obtained from: OpenBSD Reviewed by: trasz 2017-05-11T20:55:11Z Marius Strobl marius@FreeBSD.org 2017-05-11T20:55:11Z urn:sha1:95813581551be5c9ec332e609ad6a9f77a169f12 r315845, 315430, r317981, r315466 o Fix some overly long lines, whitespace and other bugs according to style(9) as well as spelling etc. in mmc(4), mmcsd(4) and sdhci(4). o In the mmc(4) bridges and sdhci(4) (bus) front-ends: - Remove redundant assignments of the default bus_generic_print_child device method, - use DEVMETHOD_END, - use NULL instead of 0 for pointers. o Trim/adjust includes. o Add and use a MMC_DECLARE_BRIDGE macro for declaring mmc(4) bridges as kernel drivers and their dependency onto mmc(4). o Add support for eMMC "partitions". Besides the user data area, i. e. the default partition, eMMC v4.41 and later devices can additionally provide up to: 1 enhanced user data area partition 2 boot partitions 1 RPMB (Replay Protected Memory Block) partition 4 general purpose partitions (optionally with a enhanced or extended attribute) Besides simply subdividing eMMC devices, some Intel NUCs having UEFI code in the boot partitions etc., another use case for the partition support is the activation of pseudo-SLC mode, which manufacturers of eMMC chips typically associate with the enhanced user data area and/ or the enhanced attribute of general purpose partitions. CAVEAT EMPTOR: Partitioning eMMC devices is a one-time operation. o Now that properly issuing CMD6 is crucial (so data isn't written to the wrong partition for example), make a step into the direction of correctly handling the timeout for these commands in the MMC layer. Also, do a SEND_STATUS when CMD6 is invoked with an R1B response as recommended by relevant specifications. o Add an IOCTL interface to mmcsd(4); this is sufficiently compatible with Linux so that the GNU mmc-utils can be ported to and used with FreeBSD (note that due to the remaining deficiencies outlined above SANITIZE operations issued by/with `mmc` currently most likely will fail). These latter have been added to ports as sysutils/mmc-utils. Among others, the `mmc` tool of mmc-utils allows for partitioning eMMC devices (tested working). o For devices following the eMMC specification v4.41 or later, year 0 is 2013 rather than 1997; so correct this for assembling the device ID string properly. o Let mmcsd.ko depend on mmc.ko. Additionally, bump MMC_VERSION as at least for some of the above a matching pair is required. o In the ACPI front-end of sdhci(4) describe the Intel eMMC and SDXC controllers as such in order to match the PCI one. Additionally, in the entry for the 80860F14 SDXC controller remove the eMMC-only SDHCI_QUIRK_INTEL_POWER_UP_RESET. 2017-05-01T01:36:54Z Eric van Gyzen vangyzen@FreeBSD.org 2017-05-01T01:36:54Z urn:sha1:3b3087ea2755ac3b562228f06bbee0a64dd28e90 Add clock_nanosleep() Add a clock_nanosleep() syscall, as specified by POSIX. Make nanosleep() a wrapper around it. Attach the clock_nanosleep test from NetBSD. Adjust it for the FreeBSD behavior of updating rmtp only when interrupted by a signal. I believe this to be POSIX-compliant, since POSIX mentions the rmtp parameter only in the paragraph about EINTR. This is also what Linux does. (NetBSD updates rmtp unconditionally.) Copy the whole nanosleep.2 man page from NetBSD because it is complete and closely resembles the POSIX description. Edit, polish, and reword it a bit, being sure to keep any relevant text from the FreeBSD page. Regenerate syscall files. Relnotes: yes Sponsored by: Dell EMC 2017-04-23T20:32:46Z Konstantin Belousov kib@FreeBSD.org 2017-04-23T20:32:46Z urn:sha1:57c8b92b8710a9cbcdab4c0ba2130d6621276fa4 Implement the memset_s(3) function as specified by the C11 ISO/IEC 9899:2011 Appendix K 3.7.4.1. MFC r316258: Only activate __EXT1_VISIBLE block when using sys/errno.h in userspace. 2017-03-14T20:14:57Z Pedro F. Giffuni pfg@FreeBSD.org 2017-03-14T20:14:57Z urn:sha1:0685b1047a24502ae7061889c18f282bce657dca Make use of clang nullability attributes in C headers. Replace uses of the GCC __nonnull__ attribute with the clang nullability qualifiers. These are starting to get use in clang's static analyzer. Replacement should be transparent for developers using clang. GCC ports from older FreeBSD versions may need updating if the compiler was built before r312860 (Jan-27-2017). Hinted by: Apple's Libc-1158.20.4, Bionic libc Relnotes: yes 2017-03-14T17:52:43Z Eric van Gyzen vangyzen@FreeBSD.org 2017-03-14T17:52:43Z urn:sha1:93e7f040518764e5e15761a19ac23ed097073661 Add sem_clockwait_np() This function allows the caller to specify the reference clock and choose between absolute and relative mode. In relative mode, the remaining time can be returned. The API is similar to clock_nanosleep(3). Thanks to Ed Schouten for that suggestion. While I'm here, reduce the sleep time in the semaphore "child" test to greatly reduce its runtime. Also add a reasonable timeout. Relnotes: yes Sponsored by: Dell EMC 2017-02-19T21:08:10Z Pedro F. Giffuni pfg@FreeBSD.org 2017-02-19T21:08:10Z urn:sha1:b90e6af77351b4f3fa431f494fb4a5e7f7d4e2c4 Remove outdated claim. Despite wishful thinking the removal of these old functions hasn't happened yet. 2017-01-18T14:13:28Z Andriy Gapon avg@FreeBSD.org 2017-01-18T14:13:28Z urn:sha1:ad1d7256f28c46d2a19f5ca54becad8235efaf21 fwmem and vmm Sponsored by: Panzura