aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Prepare to release linux (4.19.13-1).debian/4.19.13-1Salvatore Bonaccorso2018-12-301-2/+2
|
* Update to 4.19.13Salvatore Bonaccorso2018-12-294-185/+49
| | | | | | | | | | Drop iomap-Revert-fs-iomap.c-get-put-the-page-in-iomap_pa.patch Drop usb-hso-fix-oob-memory-access-in-hso_probe-hso_get_config_data.patch Add bug closer for #917569 Cleanup debian/changelog file
* Fix pycodestyle "inalid escape sequence" warningsBen Hutchings2018-12-284-3/+4
|
* Fix pycodestyle "line break after binary operator" warningsBen Hutchings2018-12-286-32/+33
|
* debian/lib/python/debian_linux/debian.py: Fix deprecated import of MutableSetBen Hutchings2018-12-282-1/+4
| | | | | | | Python 3.7 warns: .../debian/lib/python/debian_linux/debian.py:403: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working class PackageArchitecture(collections.MutableSet):
* [rt] Update to 4.19.10-rt8Romain Perier2018-12-28259-290/+556
|
* Update patch headers with git-format-patch-for-debianSalvatore Bonaccorso2018-12-271-10/+10
| | | | Gbp-Dch: Ignore
* USB: hso: Fix OOB memory access in hso_probe/hso_get_config_data ↵Salvatore Bonaccorso2018-12-273-0/+72
| | | | (CVE-2018-19985)
* Add Forwarded field to powerpcspe build fixBen Hutchings2018-12-261-0/+1
|
* [riscv64] tools uapi: fix RISC-V 64-bit supportBen Hutchings2018-12-264-23/+72
| | | | Apply Aurelien's patch instead of mine.
* [powerpcspe] Fix -mcpu= options for SPE-only compilerBen Hutchings2018-12-263-0/+43
|
* [powerpc,powerpcspe,ppc64] linux-config: Eliminate config.*_bootwrapper.gz filesBen Hutchings2018-12-252-3/+5
| | | | | | | | | | | | | | On powerpc architectures that may use a bootwrapper, we create a temporary build_<arch>_<featureset>_<flavour>_bootwrapper directory for each kernel configuration to hold the related tools which we won't install for real (because they are always native). This directory is then matched by the wildcard used in building linux-config, causing linux-config packages to contain spurious (empty) kconfig files based on these directories in addition to the real kconfig files. Rename the temporary directory to avoid matching that wildcard.
* [riscv64] tools/include/.../bitsperlong.h: Add support for riscvBen Hutchings2018-12-253-0/+23
|
* [ia64,m68k] libbpf: Don't build on architectures without performance eventsBen Hutchings2018-12-252-2/+3
|
* linux-image-*-unsigned: Remove Provides field (Closes: #916927)Ben Hutchings2018-12-252-1/+4
| | | | | | | | | | | | | | | | | In unstable, linux-image-*-unsigned packages and any corresponding metapackage updates tend to be available a few hours before the corresponding signed packages. An automatic upgrade with aptitude (at least) may then install the unsigned kernel where a signed kernel was previously used, resulting in boot failure. I gave the linux-image-*-unsigned packages a Provides relation to the unsuffixed (i.e. signed) package name because I thought packages built by module-assistant generally depended on the corresponding kernel package. That may have been true once but doesn't appear to be so now. So the Provides field can be harmful and doesn't appear to be useful, and should be removed.
* Change Origin fields for ena patches from bare commit hashes to URLsBen Hutchings2018-12-2518-18/+18
|
* [armhf] enable some kconfig items for Allwinner SoCsUwe Kleine-König2018-12-232-0/+17
|
* Prepare to release linux (4.19.12-1).debian/4.19.12-1Salvatore Bonaccorso2018-12-221-2/+2
|
* iomap: Revert "fs/iomap.c: get/put the page in iomap_page_create/release()"Salvatore Bonaccorso2018-12-213-0/+116
|
* debian/changelog: Add back one relevant entry ("fs/iomap.c: get/put the page ↵Salvatore Bonaccorso2018-12-211-0/+1
| | | | | | | | | in iomap_page_create/release()") This patch needs to be reverted for now as per upstream in https://git.kernel.org/linus/a837eca2412051628c0529768c9bc4f3580b040e Gbp-Dch: Ignore
* Add ABI reference for 4.19.0-1 (mipsel)Salvatore Bonaccorso2018-12-214-0/+63049
| | | | Gbp-Dch: Ignore
* Update to 4.19.12Salvatore Bonaccorso2018-12-211-1/+60
| | | | Cleanup debian/changelog file
* Remove not-enabled features from changelogRomain Perier2018-12-201-7/+0
|
* Add ABI reference for 4.19.0-1 (mips64el)Salvatore Bonaccorso2018-12-203-0/+46969
| | | | Gbp-Dch: Ignore
* Update to 4.19.11Salvatore Bonaccorso2018-12-203-56/+42
| | | | | | Drop ARM-dts-bcm2837-Fix-polarity-of-wifi-reset-GPIOs.patch Cleanup debian/changelog file
* Add ABI reference for 4.19.0-1 (sh4)Salvatore Bonaccorso2018-12-202-0/+29266
| | | | Gbp-Dch: Ignore
* Add ABI reference for 4.19.0-1 (hppa, mips)Salvatore Bonaccorso2018-12-196-0/+90765
| | | | Gbp-Dch: Ignore
* Ignore various ABI changesBastian Blank2018-12-182-0/+9
|
* Merge branch 'noahm/linux-4.19.5+ena202' into sidBastian Blank2018-12-1820-0/+3952
|\ | | | | | | | | | | Backport Amazon ENA ethernet driver version 2.0.2 from Linux 4.20 See merge request kernel-team/linux!77
| * drivers/net/ethernet/amazon: Backport v2.0.2 from Linux 4.20Noah Meyerhans2018-12-1720-0/+3953
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backport Amazon ENA ethernet driver version 2.0.2 from Linux 4.20 This mostly ammounts to cherry-picking the commits in the range described by git log v4.19.5..v4.20-rc7 drivers/net/ethernet/amazon Change e641e99f261f5203a911a9e0db54a214460d2cc4 introduced changes outside the ena directory, but only removed a redundant #include and was trivial to scope down. Upstream dealt with merge conflicts in d864991b220b7c62e81d21209e1fd978fd67352c; the resolution here was identical to upstream.
* | Merge branch 'master' into sidBastian Blank2018-12-182-4/+103
|\ \
| * | [rt] rebase to 4.19.10 and reenableUwe Kleine-König2018-12-182-4/+4
| | |
| * | [rt] Disable rt until the patchset reapply onto 4.19.10Romain Perier2018-12-181-1/+1
| | |
| * | Update to 4.19.10Romain Perier2018-12-181-1/+101
| |/
* | [arm] Fix reset polarity of the wifi device on Raspberry Pi 3Uwe Kleine-König2018-12-183-0/+55
| |
* | linux-perf: Fix installation directories for BPF headers and examplesBen Hutchings2018-12-182-1/+3
| | | | | | | | Closes: #916774
* | linux-perf: Fix build-time check for unversioned filesBen Hutchings2018-12-182-1/+5
| | | | | | | | | | | | | | | | | | | | The current check has never worked because the find -path predicate matches against the whole path, including the given root. In this case that is $DESTDIR which always includes the version string. Change to use cd before find. Also, check all non-directories rather than all entries with "perf" in the name.
* | Merge branch 'sid' of https://salsa.debian.org/kernel-team/linuxUwe Kleine-König2018-12-1820-0/+349853
|\ \ | |/ |/|
| * Add ABI reference for 4.19.0-1 (except not yet build architectures)Salvatore Bonaccorso2018-12-1820-0/+349853
| | | | | | | | Gbp-Dch: Ignore
* | [arm] Fix probing of 3rd gpio device on Armada 370.Uwe Kleine-König2018-12-173-0/+48
|/
* Prepare to release linux (4.19.9-1)debian/4.19.9-1Bastian Blank2018-12-161-2/+2
|
* Enable EFI_BOOTLOADER_CONTROL, EFI_CAPSULE_LOADERBastian Blank2018-12-162-0/+3
|
* [x86] Enable DRM_XEN_FRONTENDBastian Blank2018-12-162-0/+7
|
* Enable netfilter flow table supportBastian Blank2018-12-162-0/+6
|
* Enable IP_VS_MHBastian Blank2018-12-162-1/+3
|
* Enable NFT_CONNLIMIT, NFT_TUNNEL, NFT_SOCKET, NFT_OSF, NFT_TPROXYBastian Blank2018-12-162-0/+8
|
* Clean up kconfig orderBastian Blank2018-12-164-25/+24
|
* Add changelog entry for CVE-2018-19824Salvatore Bonaccorso2018-12-161-0/+2
|
* Merge branch '4.19-feature-xen-pvh' into 'master'Ben Hutchings2018-12-147-0/+681
|\ | | | | | | | | [x86] Support booting a Xen PVH guest via Grub2 See merge request kernel-team/linux!84
| * [x86] Support booting a Xen PVH guest via Grub2Hans van Kranenburg2018-12-147-0/+681
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tl;dr: Xen PVH is the perfect upgrade path from PV and in combination with grub2 support, it's the Xen "killer feature" we really should have in Buster. Background info about Xen PVH: https://wiki.xen.org/wiki/Virtualization_Spectrum#Almost_fully_PV:_PVH_mode PVH mode in Xen, a.k.a. "HVM without having to run qemu" is a Xen guest type best supported since Xen 4.11 and Linux kernel 4.17. Just like when using PV mode, the guest does not have an emulated BIOS and the guest kernel is directly started by the dom0. Buster will ship with Xen 4.11. Why is PVH interesting? 1. When the whole Meltdown/Spectre story started, it quickly became apparent that 64-bit PV is the most problematic virtualization mode to protect and to protect from, since address space from the hypervisor and other guests (including dom0) is reachable from a 64-bit PV domU. To mitigate this, XPTI (the Xen variant of PTI) has been implemented in the hypervisor, but with a performance hit. HVM (so, also PVH) guests are better isolated from the hypervisor and other guests. Inside the guest a choice can be made about which mitigations to enable or not. Also see https://xenbits.xen.org/xsa/advisory-254.html 2. Unlike HVM, it's not needed to have a boot loader/sector, partitions, and a qemu process in the dom0 (using cpu and memory and having an attack surface). Also, when running a largeish amount of domUs on a physical server, not having all the qemu processes is an advantage. 3. Unlike PV, PVH makes use of all hardware features that accelerate virtualization. The upgrade path from PV to PVH is super optimal. It's just setting type='pvh' in the guest file and doing a full restart of the domU! Unless... (insert Monty Python's Dramatic Chord!) Unless... grub2 was used to boot the PV guests. Why is it interesting to be able to use grub? Without using grub in between, the guest kernel and initrd have to be copied out of the guest onto the dom0 filesystem, because the guest has to be booted with them directly. Currently, we already have the grub-xen packages in Debian, which provide grub images which can be used as kernel for a PV guest, after which it can load the actual linux kernel that is symlinked from /vmlinuz on the guest filesystem at that moment. The final changes to the Linux kernel for grub+PVH are in Linux 4.20. This request, to carry a few patches from Linux 4.20, provides one half of the dots that need to be connected to make the full thing happen for Buster. Since we'll have Xen 4.11 in Buster, PVH is supported. The related grub2 patchset was committed to the grub master branch on Dec 12 2018 (yup, today). So, I'll also start contacting the debian grub team soon to ask (and help) to get the current grub-xen functionality in Debian to be extended with PVH capabilities as well. Test reports: https://lists.xenproject.org/archives/html/xen-devel/2018-10/msg01913.html https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03312.html
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-22 05:16:10 +0000