Besides the upstream update, the following changes were made:
1. Disabled CONFIG_INTEL_IOMMU_DEFAULT_ON option as well as a few others
that might have caused boot problems.
2. Made CONFIG_CRYPTO* and some other options closer to what Fedora
uses, just in case.
3. Updated AUFS to version "4.1.13+-20160223".
4. Added a patch to fix WiFi hard-block issues on some HP laptops.
https://bugzilla.kernel.org/show_bug.cgi?id=69131
Additional changes:
* Added a patch to fix bug #6410 (alx).
* Added a patch for audit to make it less verbose in the logs (bug #6235).
* config: Enabled bpf() syscall.
It seems, rpm does not like it when the name of the package ends with,
say, "-3.14". For example, it does not process the update from
kernel-nrj-desktop-3.14-3.14.57-2 to
kernel-nrj-desktop-3.14-3.14.57-3 correctly: the former package is not
removed as both are installed as a result.
kernel-nrj-desktop-3.14-latest-3.14.57-2 and
kernel-nrj-desktop-3.14-latest-3.14.57-3 seem to be processed OK, so let
us use this variant.
kernel-{flavour}-{major}.{minor} will require the latest kernel package
for kernel {major}.{minor}.x series.
kernel-{flavour}-{major}.{minor}-devel will do the same for -devel
packages.
This should allow the users to keep, say, kernel 4.1.x and get updates
for it even if 4.2.x is in the repositories.
If it is desired to have the latest of the available kernels,
kernel-{flavour}-latest should be used, the same way as before.
The tag had to contain both the version and the release of the package.
This is inconvenient when mass rebuilds are in action: the release is
incremented automatically then.
Using the top of the appropriate branch is safer. It is also possible to
specify any other revision, so this scheme is more flexible as well.
The tag had to contain both the version and the release of the package.
This is inconvenient when mass rebuilds are in action: the release is
incremented automatically then.
Using the top of the appropriate branch is safer. It is also possible to
specify any other revision, so this scheme is more flexible as well.
Besides the updates from the upstream, the following changes were made:
* added fixes for CVE-2014-3647, CVE-2015-4036, CVE-2015-2666;
* updated AUFS patches;
* updated BFQ patches to version v7r8;
* re-enabled SPI.
It is no longer required to upload each archive
kernel-patches-and-configs.* to FileStore. They are now retrieved from
https://abf.io/soft/kernel-patches-and-configs/ according to the git
tags.
If you are going to build kernel version X.Y.Z release R, you need to
tag the appropriate commit in kernel-patches-and-configs git repo as
"X.Y.Z-R", without quotes.
For experiments and testing, one may still upload the archives with the
pacthes and configs to FileStore and probably edit the URL in SOURCE100
in the spec.
Most external components have been removed to simplify maintenance.
The following ones are kept because they are more important and/or
maintained well in upstream:
- BFQ
- AUFS
- ndiswrapper
- several bug fixes
reiser4 is kept too but disabled by default until its maintainers update
it for kernel 4.x.
Without it, the DKMS-modules built before might have been missed.
For the same reason, kernel-<...>-devel package is now in Requires(post)
for kernel-<...>. The former must be installed completely before we call
depmod for the latter.
