All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/linux-headers: drop support for 5.x headers
Date: Tue, 18 Jun 2019 13:57:33 +0200	[thread overview]
Message-ID: <20190618115733.28551-4-peter@korsgaard.com> (raw)
In-Reply-To: <20190618115733.28551-1-peter@korsgaard.com>

The 5.0.x series is now EOL and vulnerable to the "TCP SACK PANIC" issue.
Drop support for it in linux-headers.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 Config.in.legacy                     | 7 +++++++
 linux/linux.hash                     | 1 -
 package/linux-headers/Config.in.host | 5 -----
 3 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/Config.in.legacy b/Config.in.legacy
index 2b8dc3b1ee..9d54026899 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -160,6 +160,13 @@ config BR2_KERNEL_HEADERS_4_20
 	  Version 4.20.x of the Linux kernel headers are no longer
 	  maintained upstream and are now removed.
 
+config BR2_KERNEL_HEADERS_5_0
+	bool "kernel headers version 5.0.x are no longer supported"
+	select BR2_LEGACY
+	help
+	  Version 5.0.x of the Linux kernel headers are no longer
+	  maintained upstream and are now removed.
+
 comment "Legacy options removed in 2019.05"
 
 config BR2_CSKY_DSP
diff --git a/linux/linux.hash b/linux/linux.hash
index 497e8e4d6f..205441dc25 100644
--- a/linux/linux.hash
+++ b/linux/linux.hash
@@ -1,6 +1,5 @@
 # From https://www.kernel.org/pub/linux/kernel/v5.x/sha256sums.asc
 sha256 11fd93207290272389ad284b8b042041d088fbee0ed5798e933bf8e91697d219  linux-5.1.11.tar.xz
-sha256 98d307a546c95a215dee675ffa4b63c2a7a29e7af839f0d8dfb96dbb61aac2d7  linux-5.0.21.tar.xz
 # From https://www.kernel.org/pub/linux/kernel/v4.x/sha256sums.asc
 sha256 266ee655620c3689ae94761970d6827fffc919760caf815427ad22730ba4381e  linux-4.19.52.tar.xz
 sha256 d7464c2379cdee46548ae9f848671f4669d4003af4034f3f738f2f0511ec75b3  linux-4.14.127.tar.xz
diff --git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
index 38ee0a6ac2..adf342fce0 100644
--- a/package/linux-headers/Config.in.host
+++ b/package/linux-headers/Config.in.host
@@ -49,10 +49,6 @@ config BR2_KERNEL_HEADERS_4_19
 	depends on !BR2_csky
 	select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_19
 
-config BR2_KERNEL_HEADERS_5_0
-	bool "Linux 5.0.x kernel headers"
-	select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
-
 config BR2_KERNEL_HEADERS_5_1
 	bool "Linux 5.1.x kernel headers"
 	select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1
@@ -305,7 +301,6 @@ config BR2_DEFAULT_KERNEL_HEADERS
 	default "4.9.182"	if BR2_KERNEL_HEADERS_4_9
 	default "4.14.127"	if BR2_KERNEL_HEADERS_4_14
 	default "4.19.52"	if BR2_KERNEL_HEADERS_4_19
-	default "5.0.21"	if BR2_KERNEL_HEADERS_5_0
 	default "5.1.11"	if BR2_KERNEL_HEADERS_5_1
 	default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
 	default "custom"	if BR2_KERNEL_HEADERS_CUSTOM_TARBALL
-- 
2.11.0

  parent reply	other threads:[~2019-06-18 11:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 11:57 [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.1.x series Peter Korsgaard
2019-06-18 11:57 ` [Buildroot] [PATCH 2/4] Config.in.legacy: add legacy entry for 4.20.x headers Peter Korsgaard
2019-06-20 11:28   ` Peter Korsgaard
2019-06-18 11:57 ` [Buildroot] [PATCH 3/4] amarula_vyasa_rk3288_defconfig: use same-as-kernel option for kernel headers Peter Korsgaard
2019-06-20 11:28   ` Peter Korsgaard
2019-06-18 11:57 ` Peter Korsgaard [this message]
2019-06-20 11:28   ` [Buildroot] [PATCH 4/4] package/linux-headers: drop support for 5.x headers Peter Korsgaard
2019-06-20 11:28 ` [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.1.x series Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190618115733.28551-4-peter@korsgaard.com \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.