<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/contrib, branch release/11.3.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F11.3.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F11.3.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2019-07-02T23:59:45Z</updated>
<entry>
<title>Import tzdata 2019b.</title>
<updated>2019-07-02T23:59:45Z</updated>
<author>
<name>Gordon Tetlow</name>
<email>gordon@FreeBSD.org</email>
</author>
<published>2019-07-02T23:59:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a3c83fa574d1a879f9f82511202074af767a8180'/>
<id>urn:sha1:a3c83fa574d1a879f9f82511202074af767a8180</id>
<content type='text'>
Approved by:	so
Approved by:	re (implicit)
Security:	FreeBSD-EN-19:12.tzdata
</content>
</entry>
<entry>
<title>MFH (r313975, r315909, r317827, r344533): upgrade to latest OpenPAM</title>
<updated>2019-06-12T01:53:14Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2019-06-12T01:53:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=42e4c59abadfa6d18eaee4d2b600735480388fc2'/>
<id>urn:sha1:42e4c59abadfa6d18eaee4d2b600735480388fc2</id>
<content type='text'>
Approved by:	re (gjb)
</content>
</entry>
<entry>
<title>MFC r347990:</title>
<updated>2019-06-04T10:35:54Z</updated>
<author>
<name>Martin Matuska</name>
<email>mm@FreeBSD.org</email>
</author>
<published>2019-06-04T10:35:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b8a9d3fd247a71bd502f043724133864963efa53'/>
<id>urn:sha1:b8a9d3fd247a71bd502f043724133864963efa53</id>
<content type='text'>
Sync libarchive with vendor.

Relevant vendor changes:
  Issue #795: XAR - do not try to add xattrs without an allocated name
  PR #812: non-recursive option for extract and list
  PR #958: support reading metadata from compressed files
  PR #999: add --exclude-vcs option to bsdtar
  Issue #1062: treat empty archives with a GNU volume header as valid
  PR #1074: Handle ZIP files with trailing 0s in the extra fields
            (Android APK archives)
  PR #1109: Ignore padding in Zip extra field data (Android APK archives)
  PR #1167: fix problems related to unreadable directories
  Issue #1168: fix handling of strtol() and strtoul()
  PR #1172: RAR5 - fix invalid window buffer read in E8E9 filter
  PR #1174: ZIP reader - fix of MSZIP signature parsing
  PR #1175: gzip filter - fix reading files larger than 4GB from memory
  PR #1177: gzip filter - fix memory leak with repeated header reads
  PR #1180: ZIP reader - add support for Info-ZIP Unicode Path Extra Field
  PR #1181: RAR5 - fix merge_block() recursion
            (OSS-Fuzz 12999, 13029, 13144, 13478, 13490)
  PR #1183: fix memory leak when decompressing ZIP files with LZMA
  PR #1184: fix RAR5 OSS-Fuzz issues 12466, 14490, 14491, 12817
    OSS-Fuzz 12466: RAR5 - fix buffer overflow when parsing huffman tables
    OSS-Fuzz 14490, 14491: RAR5 - fix bad shift-left operations
    OSS-Fuzz 12817: RAR5 - handle a case with truncated huffman tables
  PR #1186: RAR5 - fix invalid type used for dictionary size mask
            (OSS-Fuzz 14537)
  PR #1187: RAR5 - fix integer overflow (OSS-Fuzz 14555)
  PR #1190: RAR5 - RAR5 don't try to unpack entries marked as directories
            (OSS-Fuzz 14574)
  PR #1196: RAR5 - fix a potential SIGSEGV on 32-bit builds
  OSS-Fuzz 2582: RAR - fix use after free if there is an invalid entry
  OSS-Fuzz 14331: RAR5 - fix maximum owner name length
  OSS-Fuzz 13965: RAR5 - use unsigned int for volume number + range check

  Additional RAR5 reader changes:
    - support symlinks, hardlinks, file owner, file group, versioned files
    - change ARCHIVE_FORMAT_RAR_V5 to 0x100000
    - set correct mode for readonly directories
    - support readonly, hidden and system Windows file attributes

MFC r347999:
Install missing data file for
lib.libarchive.functional_test.test_read_format_zip_utf8_paths

Approved by:	re (gjb blanket)
</content>
</entry>
<entry>
<title>MFC r347642:</title>
<updated>2019-05-29T19:11:09Z</updated>
<author>
<name>Cy Schubert</name>
<email>cy@FreeBSD.org</email>
</author>
<published>2019-05-29T19:11:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2ed0cd4570c7cd1e1f51a12f80fe5065f2bd78d0'/>
<id>urn:sha1:2ed0cd4570c7cd1e1f51a12f80fe5065f2bd78d0</id>
<content type='text'>
The driver list prints "(null)" for the NDIS driver when -h (help) or
an unknown switch is passed outputting the command usage. This is
because the NDIS driver is uninitialized when usage help is printed.
To resolve this we initialize the driver prior to the possibility of
printing the usage help message.

Approved by:	re (gjb@)
</content>
</entry>
<entry>
<title>MFC r348288:</title>
<updated>2019-05-29T18:32:43Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2019-05-29T18:32:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1c9bc978756fd56d3cfc80b3e6ef7347d6e4d63f'/>
<id>urn:sha1:1c9bc978756fd56d3cfc80b3e6ef7347d6e4d63f</id>
<content type='text'>
Pull in r361696 from upstream llvm trunk (by Sanjay Patel):

  [SelectionDAG] soften assertion when legalizing narrow vector FP ops

  The test based on PR42010:
  https://bugs.llvm.org/show_bug.cgi?id=42010

  ...may show an inaccuracy for PPC's target defs, but we should not be
  so aggressive with an assert here. There's no telling what
  out-of-tree targets look like.

This fixes an assertion when building the graphics/mesa-dri port for
PowerPC64.

Approved by:	re (kib)
Reported by:	Mark Millard &lt;marklmi26-fbsd@yahoo.com&gt;
PR:		238082
</content>
</entry>
<entry>
<title>MFC r347244:</title>
<updated>2019-05-25T01:58:00Z</updated>
<author>
<name>Xin LI</name>
<email>delphij@FreeBSD.org</email>
</author>
<published>2019-05-25T01:58:00Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=54d5d0ad34bdebbb00e713c3b25ec0407d801a94'/>
<id>urn:sha1:54d5d0ad34bdebbb00e713c3b25ec0407d801a94</id>
<content type='text'>
Move contrib/zlib to sys/contrib/zlib so that we can use it in kernel.
This is a prerequisite of unifying kernel zlib instances.

Submitted by:	Yoshihiro Ota &lt;ota at j.email.ne.jp&gt;
Approved by:	re (kib)
</content>
</entry>
<entry>
<title>MFC r347311:</title>
<updated>2019-05-16T18:18:22Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-05-16T18:18:22Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bb16f4bd35b2de62d1ec54cb33ef690dd80a283e'/>
<id>urn:sha1:bb16f4bd35b2de62d1ec54cb33ef690dd80a283e</id>
<content type='text'>
Add ConnectX-6 DX HCA ID to libmlx5.

In addition, add "ConnectX family mlx5Gen Virtual Function" device ID.
Every new HCA VF will be identified with this device ID.

Submitted by:	slavash@
Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r347302:</title>
<updated>2019-05-16T18:09:34Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-05-16T18:09:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=92245d44faa63bd166e5ad5f766023442a826321'/>
<id>urn:sha1:92245d44faa63bd166e5ad5f766023442a826321</id>
<content type='text'>
Add support for 200Gbit speeds to libibverbs.

Submitted by:	slavash@
Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r347243:</title>
<updated>2019-05-11T09:56:59Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2019-05-11T09:56:59Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2574e7c87574adbc8478ba4a5a49c42e9875db29'/>
<id>urn:sha1:2574e7c87574adbc8478ba4a5a49c42e9875db29</id>
<content type='text'>
Pull in r360099 from upstream llvm trunk (by Eli Friedman):

  [ARM] Glue register copies to tail calls.

  This generally follows what other targets do. I don't completely
  understand why the special case for tail calls existed in the first
  place; even when the code was committed in r105413, call lowering
  didn't work in the way described in the comments.

  Stack protector lowering breaks if the register copies are not glued
  to a tail call: we have to insert the stack protector check before
  the tail call, and we choose the location based on the assumption
  that all physical register dependencies of a tail call are adjacent
  to the tail call. (See FindSplitPointForStackProtector.) This is sort
  of fragile, but I don't see any reason to break that assumption.

  I'm guessing nobody has seen this before just because it's hard to
  convince the scheduler to actually schedule the code in a way that
  breaks; even without the glue, the only computation that could
  actually be scheduled after the register copies is the computation of
  the call address, and the scheduler usually prefers to schedule that
  before the copies anyway.

  Fixes https://bugs.llvm.org/show_bug.cgi?id=41417

  Differential Revision: https://reviews.llvm.org/D60427

This should fix several instances of "Bad machine code: Using an
undefined physical register", when compiling ports such as
multimedia/vlc, audio/alsa-lib and devel/avro-c for armv6, with
-fstack-protector-strong.

Reported by:	jbeich
PR:		237074, 237783, 237784
</content>
</entry>
<entry>
<title>MFC r347139:</title>
<updated>2019-05-08T15:48:55Z</updated>
<author>
<name>Cy Schubert</name>
<email>cy@FreeBSD.org</email>
</author>
<published>2019-05-08T15:48:55Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a92358064d6e5bddfe7a017d0081ac110623b055'/>
<id>urn:sha1:a92358064d6e5bddfe7a017d0081ac110623b055</id>
<content type='text'>
MFV r347136: Update sqlite3-3.27.2 (3270200) --&gt; sqlite3-3.28.0 (3280000)

Security:	CVE-2019-9937, CVE-2019-9936
</content>
</entry>
</feed>
