Mailing list announcement:
the Multipath TCP Kernel v0.94.3 has been released, containing important
bug-fixes (thanks to syzkaller) and perf-improvements.
This release is based on Linux v4.14.105.
Everybody should update to the latest kernel.
Multipath TCP Linux Kernel v0.94.3
=====
Benjamin Hesmans <benjamin.hesmans@uclouvain.be> (1):
[3f01458be8cc] mptcp: checksum corner case
Christoph Paasch <cpaasch@apple.com> (21):
[287af08b7193] mptcp: Trigger sending when new subflow gets established
[a284ba1574f5] mptcp: Reinject data when the write-queue gets purged
[9ac97e3324ec] mptcp: Build-Fix for mptcp_push_pending_frames
[68e3b3cc6204] mptcp: Don't allow TCP_REPAIR on MPTCP-sockets
[6d58ca87a125] mptcp: Rework mptcp_disconnect
[1b142d9b94f9] mptcp: Initialize IPv6-fields even more correctly
[247a77e1d4e0] mptcp: Fully disable MD5SIG
[97543fe0b8b8] mptcp: Reset icsk_bind_hash to NULL to avoid use-after-free in inet_put_port
[d307e46cc3f9] mptcp: Initialize meta_tp after potentially failing instructions
[da42a64cf11e] mptcp: Don't free mpcb when mptcp_alloc_mpcb succeeded
[71b3bf995bcd] mptcp: Prevent circular locking dependency on tcp_close()
[444bf8c76806] mptcp: Ensure proper free'ing of master_sk upon failure
[15afe58a959e] mptcp: Handle error-case for MPTCP-Fastopen
[73db90da684c] mptcp: Unify usage of rcu_read_lock_bh,...
[f266d120c091] mptcp: Fix error-cases in TCP_SYNCOOKIES path
[872427427624] mptcp: Support randomized Timestamps on SYN-Cookies
[c3e29b9cace0] mptcp: Do not lock in tcp_get_info for MPTCP_INFO
[1bc2adaf003d] mptcp: Trigger meta-retransmission always when the timer fired
[a947ef46d5e1] mptcp: Don't update meta-RTO from subflows that are retransmitting
[619d44cae638] mptcp: Reevalute and reschedule meta-level RTO for new subflows
[310b6838cab0] mptcp: Stable Release v0.94.3
Matthieu Baerts <matthieu.baerts@tessares.net> (1):
[34154a943635] mptcp: Build-Fix with CONFIG_MEMCG
How to install (if you have our bintray repositories setup)
=====
The config-file of these pre-compiled images has also been updated with more
complete configurations, including also CONFIG_MEMCG (cfr.:
https://github.com/multipath-tcp/mptcp/issues/321).
The current approach will fail when enough time has passed. We ideally
want to be reproducible even in a few years of time. So we should pick
the sources of patches wisely as otherwise we can not do that.
Ensure that only module-related targets from the project's Makefile are
built.
Co-authored-by: elseym <elseym@me.com>
Co-authored-by: Franz Pletz <fpletz@fnordicwalking.de>
Bump to the latest stable version. Be aware that cryptsetup changed the
default LUKS header format with this version. When porting this to a
stable distribution you should supply the configure flag
`--with-default-luks-format=LUKS1` to preserve the user experience
there.
The full changelog can be seen at [0].
[0] https://gitlab.com/cryptsetup/cryptsetup/blob/master/docs/v2.1.0-ReleaseNotes
* 30.pre2 source is no longer available, apparently
Since changelog seems to be only inside the sources,
here's the diff from pre2 to pre9's CHANGELOG.h:
---
o When using takeover, redo probing in case eth0 was in use [ifrename]
o Update Hotplug documentation, add uDev bits [HOTPLUG-UDEV.txt]
o Add ESSID bug patches and documentation [ESSID-BUG.txt]
o Make wireless.21.h LGPL as promised a long time ago [wireless.21.h]
---
(Bug reported by Shaddy Baddah)
o Fix unaligned access on SPARC in the 64->32 bit workaround [iwlib.c]
---
(From Maxime Charpenne <maxime.charpenne@free.fr>)
o Mise à jour de la traduction en francais des pages manuel [fr/*]
---
o Use wireless.22.h, make it LGPL [iwlib.h/wireless.22.h]
o Show Scanning Capabilities in "iwlist event" [iwlist]
(Bug reported by Nikita Zhernosenko)
o Fix parsing of retry/power when modifier is used [iwconfig]
(Bug reported by Alexis Phoenix)
o Remove trailing '/' in INSTALL_* that fooled checkinstall [Makefile]
(From Dan Williams <dcbw@redhat.com>)
o Scan capabilities in struct iw_range [wireless.h]
(From Guus Sliepen <guus@debian.org>)
o Install localised man page [Makefile]
---
o Fix #define that broke 32->64 bit workaround [wireless.22.h]
o Workaround kernel bug when getting ESSID [iwlib/iwconfig/iwgetid]
(From Gerald Pfeifer <gerald@pfeifer.com>)
o Fix gramar in man page, add about hidden networks [iwlist.8]
---
(From Reinette Chatre <reinette.chatre@intel.com>)
o Enable scan buffer to grow up to 65535 instead of 32768 [iwlist]
o Return a proper error if scan result exceed buffer max [iwlist]
(From Jean Tourrilhes)
o Do above two fixes for the simple scan API [iwlib]
(From Claudio Ferronato <claiudio@libero.it>)
o Spelling and typos in [iwconfig.8]
---
o Create iwlib-private.h to minimise namespace pollution [iwlib]
o More fix to the 64->32bit band-aid for encode [iwlib]
o Update udev rule to remove a warning [19-udev-ifrename.rules]
(from Ritesh Raj Sarraf <rrs@researchut.com> and Guus Sliepen)
o Propagate error codes out of main for get [iwconfig/iwlist/iwspy]
(From Guus Sliepen <guus@debian.org>)
o Remove spurious commands from Czech iwconfig manpage.
nvidia_x11 and persistenced were modified to provide binaries which can be
mounted inside a docker-container to be executed there.
most ldconfig-based discovery of bundled nvidia libraries is patched out
ldconfig itself is patched to be able to deal with patchelf'ed libraries
See https://sourceware.org/bugzilla/show_bug.cgi?id=23964
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
To quote block/Kconfig:
> Builds Logic for interfacing with Opal enabled controllers.
> Enabling this option enables users to setup/unlock/lock
> Locking ranges for SED devices using the Opal protocol.
Without `BLK_SED_OPAL`, it is impossible to resume from sleep when using
a locked self-encrypting drive.
This configuration option appeared in earlier kernels, but only reached
maturity in 4.14 according to discussion at:
- https://github.com/Drive-Trust-Alliance/sedutil/issues/90 and
- https://github.com/Drive-Trust-Alliance/sedutil/pull/190
This kernel option is enabled in the default kernels shipped with
Fedora, Debian, and other mainstream Linux distributions.
The only outside-curl uses of `fetchurlBoot` left are `stdenv`
and `apple-source-releases`. The latter one can probably be removed
too, but I can't test it.
Pros:
- Aggregates all behind-the-scenes insanity in a single place.
Cons:
- At the cost of 10 more derivations (but 0 new outpaths).
