<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys, branch upstream/10.4.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=upstream%2F10.4.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=upstream%2F10.4.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2017-09-29T00:01:06Z</updated>
<entry>
<title>Update releng/10.4 to -RELEASE status in preparation for the final</title>
<updated>2017-09-29T00:01:06Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-29T00:01:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=afca0a021557f29db51c980fc9710b851d16f3bd'/>
<id>urn:sha1:afca0a021557f29db51c980fc9710b851d16f3bd</id>
<content type='text'>
10.4-RELEASE builds.

Approved by:	re (implicit)
</content>
</entry>
<entry>
<title>Update releng/10.4 to RC2 again so the revision of sys/conf/newvers.sh</title>
<updated>2017-09-22T15:27:50Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-22T15:27:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=45d97b32dbe484c88d58a2a12b334b76cac3dd31'/>
<id>urn:sha1:45d97b32dbe484c88d58a2a12b334b76cac3dd31</id>
<content type='text'>
will reflect the (hopefully) final 10.4-RC2 builds.

Approved by:	re (implicit)
</content>
</entry>
<entry>
<title>Revert releng/10.4 to RC1 again.</title>
<updated>2017-09-22T15:27:02Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-22T15:27:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b5fbaaf760d0461fb1e0ada51b797cc8c057fb34'/>
<id>urn:sha1:b5fbaaf760d0461fb1e0ada51b797cc8c057fb34</id>
<content type='text'>
Approved by:	re (implicit)
</content>
</entry>
<entry>
<title>Update releng/10.4 to RC2 in preparation for 10.4-RC2 builds.</title>
<updated>2017-09-22T00:16:46Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-22T00:16:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0f252937030a506ab0997646e7f5faa8821e09a6'/>
<id>urn:sha1:0f252937030a506ab0997646e7f5faa8821e09a6</id>
<content type='text'>
Approved by:	re (implicit)
</content>
</entry>
<entry>
<title>MF10: r323871</title>
<updated>2017-09-21T20:29:14Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-21T20:29:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=441e391a0200e674ab8d016dfad662e3bf2453fd'/>
<id>urn:sha1:441e391a0200e674ab8d016dfad662e3bf2453fd</id>
<content type='text'>
MFC: r285215

remove _NORMAL flag which isn't suppose to be used w/ _alloc_ctx...

MFC: r285289

address an issue where consumers, like IPsec, can reuse the same
session in multiple threads w/o locking..  There was a single fpu
context shared per session, if multiple threads were using the session,
and both migrated away, they could corrupt each other's fpu context...

MFC: r285297

upon further examination, it turns out that _unregister_all already
provides the guarantee that no threads will be in the _newsession code..

MFC: r298332

aesni(4): Initialize error before use [1]

Reported by:	Coverity [1]
CID:		1331554 [1]

Approved by:	re (gjb, kib)
</content>
</entry>
<entry>
<title>MF10: r323870, MFC: r275751</title>
<updated>2017-09-21T20:13:03Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-21T20:13:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0b2ec6e69608eb77a5cf1a7f84a53e6834c91a19'/>
<id>urn:sha1:0b2ec6e69608eb77a5cf1a7f84a53e6834c91a19</id>
<content type='text'>
Add _NEW flag to mtx(9), sx(9), rmlock(9) and rwlock(9).
A _NEW flag passed to _init_flags() to avoid check for double-init.

Approved by:	re (gjb)
</content>
</entry>
<entry>
<title>MF10: r323830</title>
<updated>2017-09-20T22:14:50Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-20T22:14:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=55f826f99096541fea087d77dd3a76b0cda9e35f'/>
<id>urn:sha1:55f826f99096541fea087d77dd3a76b0cda9e35f</id>
<content type='text'>
Unbreak netmap(4) support in ixgbe(4) after r315333:
- Both ixgbe_netmap.c and ixv_netmap.c assumed a netmap(4) driver
  newer than what's actually in stable/10.
- Additionally, at the bottom line ixv_netmap.c did exactly the same
  as ixgbe_netmap.c, i. e. used IXGBE_TDH() as appropriate for PFs
  only instead of IXGBE_VFTDH() and tried to configure CRC stripping
  although the corresponding registers aren't available to VFs in the
  first place.

With these changes, the netmap(4) support in ixgbe(4) is in line
again with the code in sys/dev/netmap/ixgbe_netmap.h as of r295008.
Breakage reported by: Slawa Olhovchenkov

Just like r315333 that never existed in head, this is a direct commit
to stable/10. However, ixgbe(4) in head has a related bug in that it
assumes a netmap(4) driver API older than what's in head and also
does the wrong things for VFs as it uses the PF-only ixgbe_netmap.c
for both PFs and VFs in the first place.

MF10: r323835, MFC: r320916

Reset unsupported SFP tuneable back to original entry name.

Approved by:	re (gjb)
</content>
</entry>
<entry>
<title>- Copy stable/10@323601 to releng/10.4 in preparation for 10.4-RC1</title>
<updated>2017-09-15T00:31:25Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2017-09-15T00:31:25Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=683e74bedfccebf41f8aeb649e244fa4fab0a80c'/>
<id>urn:sha1:683e74bedfccebf41f8aeb649e244fa4fab0a80c</id>
<content type='text'>
  builds.
- Update newvers.sh to reflect RC1.
- Update __FreeBSD_version to reflect 10.4.
- Switch the pkg(8) repository to use the 10.4 release package set for
  DVD image creation.

Approved by:	re (implicit)
</content>
</entry>
<entry>
<title>MFC r320069: Add ZFS to Linux statfs ftype</title>
<updated>2017-09-09T14:30:16Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2017-09-09T14:30:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=fa468026221e7f8d8a23a3c5921126141badf0ed'/>
<id>urn:sha1:fa468026221e7f8d8a23a3c5921126141badf0ed</id>
<content type='text'>
PR:		220086
Approved by:	re (gjb)
Sponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>MFC r323002: zfs: do not advertise unsupported hash algorithms</title>
<updated>2017-09-08T20:41:49Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2017-09-08T20:41:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=48b0676d89bc673e7cc70c41cafa56d719c25d75'/>
<id>urn:sha1:48b0676d89bc673e7cc70c41cafa56d719c25d75</id>
<content type='text'>
illumos 4185 ("add new cryptographic checksums to ZFS: SHA-512, Skein,
Edon-R") was intentionally merged only partially in r289422, without
adding support for skein, sha512 and edonr on FreeBSD.

Support for skein and sha512 was added later on (in head), but none of
these are supported in stable/10. Prior to this commit zfs(8) correctly
rejected these algorithms, but with an error message that claimed
support:

fk@r500 ~ $zfs set checksum=edonr tank
cannot set property for 'tank': 'checksum' must be one of 'on | off |
  fletcher2 | fletcher4 | sha256 | sha512 | skein | edonr'

(This commit removes sha512 and skein in addition to edonr from the
merge of head's r323002.)

PR:		204055
Submitted by:	Fabian Keil
Approved by:	re (kib)
Obtained from:	ElectroBSD
</content>
</entry>
</feed>
