1. 04 7月, 2016 26 次提交
  2. 03 7月, 2016 1 次提交
    • R
      add consistent reserved fields in mips64/n32 termios structures · 7158481d
      Rich Felker 提交于
      the (unused) speed fields were omitted when these ports were first
      added (within this release cycle, so not present in any release yet)
      in accordance with how glibc defines the structure on mips archs.
      however their omission does not match existing musl practice/intent.
      
      glibc provides its own, mostly-unified termios structure definition
      and performs translation in userspace to match the kernel structure
      for the arch, but has gratuitous differences on a few archs like mips,
      presumably as a result of historical mistakes. some other libcs use
      the kernel definitions directly. musl essentially does that, by
      matching the kernel layout in the part of the structure the kernel
      will read/write, but leaves additional space at the end for
      extensibility. these are nominally the (nonstandard) speed fields and
      (on most archs) extra c_cc elements, but since they are not used they
      could be repurposed if there's ever a need.
      7158481d
  3. 02 7月, 2016 1 次提交
    • R
      fix posix_fadvise syscall args on powerpc, unify with arm fix · 3dd27f3a
      Rich Felker 提交于
      commit 6d38c9cf provided an
      arm-specific version of posix_fadvise to address the alternate
      argument order the kernel expects on arm, but neglected to address
      that powerpc (32-bit) has the same issue. instead of having arch
      variant files in duplicate, simply put the alternate version in the
      top-level file under the control of a macro defined in syscall_arch.h.
      3dd27f3a
  4. 01 7月, 2016 1 次提交
  5. 30 6月, 2016 2 次提交
  6. 29 6月, 2016 4 次提交
  7. 28 6月, 2016 2 次提交
    • R
      fix misaligned address buffers in gethostbyname[2][_r] results · 4da0bc5e
      Rich Felker 提交于
      mistakenly ordering strings before addresses in the result buffer
      broke the alignment that the preceding code had set up.
      4da0bc5e
    • R
      fix failure to obtain EOWNERDEAD status for process-shared robust mutexes · 384d103d
      Rich Felker 提交于
      Linux's documentation (robust-futex-ABI.txt) claims that, when a
      process dies with a futex on the robust list, bit 30 (0x40000000) is
      set to indicate the status. however, what actually happens is that
      bits 0-30 are replaced with the value 0x40000000, i.e. bits 0-29
      (containing the old owner tid) are cleared at the same time bit 30 is
      set.
      
      our userspace-side code for robust mutexes was written based on that
      documentation, assuming that kernel would never produce a futex value
      of 0x40000000, since the low (owner) bits would always be non-zero.
      commit d338b506 introduced this
      assumption explicitly while fixing another bug in how non-recoverable
      status for robust mutexes was tracked. presumably the tests conducted
      at that time only checked non-process-shared robust mutexes, which are
      handled in pthread_exit (which implemented the documented kernel
      protocol, not the actual one) rather than by the kernel.
      
      change pthread_exit robust list processing to match the kernel
      behavior, clearing bits 0-29 while setting bit 30, and use the value
      0x7fffffff instead of 0x40000000 to encode non-recoverable status. the
      choice of value here is arbitrary; any value with at least one of bits
      0-29 set should work just as well,
      384d103d
  8. 22 6月, 2016 1 次提交
  9. 10 6月, 2016 2 次提交
    • R
      avoid padding gaps in struct sockaddr_storage · 1e6fc0b6
      Rich Felker 提交于
      compilers are free not to copy, or in some cases to clobber, padding
      bytes in a structure. while it's an aliasing violation, and thus
      undefined behavior, to copy or manipulate other sockaddr types using
      sockaddr_storage, it seems likely that traditional code attempts to do
      so, and the original intent of the sockaddr_storage structure was
      probably to allow such usage.
      
      in the interest of avoiding silent and potentially dangerous breakage,
      ensure that there are no actual padding bytes in sockaddr_storage by
      moving and adjusting the size of the __ss_padding member so that it
      fits exactly.
      
      this change also removes a silent assumption that the alignment of
      long is equal to its size.
      1e6fc0b6
    • S
      update sys/socket.h to linux v4.6 · a0bb50a1
      Szabolcs Nagy 提交于
      kernel connection multiplexor macros AF_KCM, PF_KCM, SOL_KCM were
      added in linux commit ab7ac4eb9832e32a09f4e8042705484d2fb0aad3
      
      MSG_BATCH sendmsg flag for performance optimization was added
      in linux commit f092276d85b82504e8a07498f4e9e0c51f06745c
      
      SOL_* macros are now synced with linux socket.h which is not a uapi
      header and glibc did not have the macros either, but that has changed
      http://sourceware.org/ml/libc-alpha/2016-05/msg00322.html
      a0bb50a1
新手
引导
客服 返回
顶部