All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Matthew Wilcox <willy@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Joe Perches <joe@perches.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Mon, 3 May 2021 11:25:21 +0200	[thread overview]
Message-ID: <CAK8P3a0kV4ZfMEFh0DcMDjXqxA0yhj8a8CL-YFGV6B4pszHeGg@mail.gmail.com> (raw)
In-Reply-To: <YI+nhMcPSTs/5Ydp@ada-deb-carambola.ifak-system.com>

On Mon, May 3, 2021 at 9:35 AM Alexander Dahl <ada@thorsis.com> wrote:
>
> Desktops and servers are all nice, however I just want to make you
> aware, there are embedded users forced to stick to older cross
> toolchains for different reasons as well, e.g. in industrial
> environment. :-)
>
> This is no show stopper for us, I just wanted to let you be aware.

Can you be more specific about what scenarios you are thinking of,
what the motivations are for using an old compiler with a new kernel
on embedded systems, and what you think a realistic maximum
time would be between compiler updates?

One scenario that I've seen previously is where user space and
kernel are built together as a source based distribution (OE, buildroot,
openwrt, ...), and the compiler is picked to match the original sources
of the user space because that is best tested, but the same compiler
then gets used to build the kernel as well because that is the default
in the build environment.

There are two problems I see with this logic:

- Running the latest kernel to avoid security problems is of course
  a good idea, but if one runs that with ten year old user space that
  is never updated, the system is likely to end up just as insecure.
  Not all bugs are in the kernel.

- The same logic that applies to ancient user space staying with
  an ancient compiler (it's better tested in this combination) also
  applies to the kernel: running the latest kernel on an old compiler
  is something that few people test, and tends to run into more bugs
  than using the compiler that other developers used to test that
  kernel.

       Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Matthew Wilcox <willy@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 Segher Boessenkool <segher@kernel.crashing.org>,
	Joe Perches <joe@perches.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	 Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
	 Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	 Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	 Paul Mackerras <paulus@samba.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	 linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Mon, 3 May 2021 11:25:21 +0200	[thread overview]
Message-ID: <CAK8P3a0kV4ZfMEFh0DcMDjXqxA0yhj8a8CL-YFGV6B4pszHeGg@mail.gmail.com> (raw)
In-Reply-To: <YI+nhMcPSTs/5Ydp@ada-deb-carambola.ifak-system.com>

On Mon, May 3, 2021 at 9:35 AM Alexander Dahl <ada@thorsis.com> wrote:
>
> Desktops and servers are all nice, however I just want to make you
> aware, there are embedded users forced to stick to older cross
> toolchains for different reasons as well, e.g. in industrial
> environment. :-)
>
> This is no show stopper for us, I just wanted to let you be aware.

Can you be more specific about what scenarios you are thinking of,
what the motivations are for using an old compiler with a new kernel
on embedded systems, and what you think a realistic maximum
time would be between compiler updates?

One scenario that I've seen previously is where user space and
kernel are built together as a source based distribution (OE, buildroot,
openwrt, ...), and the compiler is picked to match the original sources
of the user space because that is best tested, but the same compiler
then gets used to build the kernel as well because that is the default
in the build environment.

There are two problems I see with this logic:

- Running the latest kernel to avoid security problems is of course
  a good idea, but if one runs that with ten year old user space that
  is never updated, the system is likely to end up just as insecure.
  Not all bugs are in the kernel.

- The same logic that applies to ancient user space staying with
  an ancient compiler (it's better tested in this combination) also
  applies to the kernel: running the latest kernel on an old compiler
  is something that few people test, and tends to run into more bugs
  than using the compiler that other developers used to test that
  kernel.

       Arnd

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Matthew Wilcox <willy@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 Segher Boessenkool <segher@kernel.crashing.org>,
	Joe Perches <joe@perches.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	 Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
	 Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	 Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	 Paul Mackerras <paulus@samba.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	 linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Mon, 3 May 2021 11:25:21 +0200	[thread overview]
Message-ID: <CAK8P3a0kV4ZfMEFh0DcMDjXqxA0yhj8a8CL-YFGV6B4pszHeGg@mail.gmail.com> (raw)
In-Reply-To: <YI+nhMcPSTs/5Ydp@ada-deb-carambola.ifak-system.com>

On Mon, May 3, 2021 at 9:35 AM Alexander Dahl <ada@thorsis.com> wrote:
>
> Desktops and servers are all nice, however I just want to make you
> aware, there are embedded users forced to stick to older cross
> toolchains for different reasons as well, e.g. in industrial
> environment. :-)
>
> This is no show stopper for us, I just wanted to let you be aware.

Can you be more specific about what scenarios you are thinking of,
what the motivations are for using an old compiler with a new kernel
on embedded systems, and what you think a realistic maximum
time would be between compiler updates?

One scenario that I've seen previously is where user space and
kernel are built together as a source based distribution (OE, buildroot,
openwrt, ...), and the compiler is picked to match the original sources
of the user space because that is best tested, but the same compiler
then gets used to build the kernel as well because that is the default
in the build environment.

There are two problems I see with this logic:

- Running the latest kernel to avoid security problems is of course
  a good idea, but if one runs that with ten year old user space that
  is never updated, the system is likely to end up just as insecure.
  Not all bugs are in the kernel.

- The same logic that applies to ancient user space staying with
  an ancient compiler (it's better tested in this combination) also
  applies to the kernel: running the latest kernel on an old compiler
  is something that few people test, and tends to run into more bugs
  than using the compiler that other developers used to test that
  kernel.

       Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-05-03  9:26 UTC|newest]

Thread overview: 146+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:15 ` Masahiro Yamada
2021-05-01 15:15 ` Masahiro Yamada
2021-05-01 15:15 ` Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 15:52   ` Miguel Ojeda
2021-05-01 15:52   ` Miguel Ojeda
2021-05-01 15:52   ` Miguel Ojeda
2021-05-01 17:38   ` Christophe Leroy
2021-05-01 17:38     ` Christophe Leroy
2021-05-01 17:38     ` Christophe Leroy
2021-05-01 17:38     ` Christophe Leroy
2021-05-02  2:41   ` Joe Perches
2021-05-02  2:41     ` Joe Perches
2021-05-02  2:41     ` Joe Perches
2021-05-02  2:41     ` Joe Perches
2021-05-02 18:30     ` Segher Boessenkool
2021-05-02 18:30       ` Segher Boessenkool
2021-05-02 18:30       ` Segher Boessenkool
2021-05-02 18:30       ` Segher Boessenkool
2021-05-02 20:00       ` Joe Perches
2021-05-02 20:00         ` Joe Perches
2021-05-02 20:00         ` Joe Perches
2021-05-02 20:00         ` Joe Perches
2021-05-02 20:32         ` Segher Boessenkool
2021-05-02 20:32           ` Segher Boessenkool
2021-05-02 20:32           ` Segher Boessenkool
2021-05-02 20:32           ` Segher Boessenkool
2021-05-02 21:05           ` Ali Kaasinen
2021-05-02 21:05             ` Ali Kaasinen
2021-05-02 21:05             ` Ali Kaasinen
2021-05-02 21:05             ` Ali Kaasinen
2021-05-02 21:08           ` Linus Torvalds
2021-05-02 21:08             ` Linus Torvalds
2021-05-02 21:08             ` Linus Torvalds
2021-05-02 21:08             ` Linus Torvalds
2021-05-02 22:30             ` Matthew Wilcox
2021-05-02 22:30               ` Matthew Wilcox
2021-05-02 22:30               ` Matthew Wilcox
2021-05-02 22:30               ` Matthew Wilcox
2021-05-03  7:34               ` Alexander Dahl
2021-05-03  7:34                 ` Alexander Dahl
2021-05-03  7:34                 ` Alexander Dahl
2021-05-03  7:34                 ` Alexander Dahl
2021-05-03  8:54                 ` Joe Perches
2021-05-03  8:54                   ` Joe Perches
2021-05-03  8:54                   ` Joe Perches
2021-05-03  8:54                   ` Joe Perches
2021-05-03  9:25                 ` Arnd Bergmann [this message]
2021-05-03  9:25                   ` Arnd Bergmann
2021-05-03  9:25                   ` Arnd Bergmann
2021-05-03  9:25                   ` Arnd Bergmann
2021-05-03 12:20                   ` David Laight
2021-05-03 12:20                     ` David Laight
2021-05-03 12:20                     ` David Laight
2021-05-03 13:10                     ` Miguel Ojeda
2021-05-03 13:10                       ` Miguel Ojeda
2021-05-03 13:10                       ` Miguel Ojeda
2021-05-03 13:10                       ` Miguel Ojeda
2021-05-04  5:30                   ` Alexander Dahl
2021-05-04  5:30                     ` Alexander Dahl
2021-05-04  5:30                     ` Alexander Dahl
2021-05-04  5:30                     ` Alexander Dahl
2021-05-04  6:33                     ` Christophe Leroy
2021-05-04  6:33                       ` Christophe Leroy
2021-05-04  6:33                       ` Christophe Leroy
2021-05-04 12:07                     ` Arnd Bergmann
2021-05-04 12:07                       ` Arnd Bergmann
2021-05-04 12:07                       ` Arnd Bergmann
2021-05-04 12:07                       ` Arnd Bergmann
2021-05-04 13:25                   ` Andy Shevchenko
2021-05-04 13:25                     ` Andy Shevchenko
2021-05-04 13:25                     ` Andy Shevchenko
2021-05-04 13:25                     ` Andy Shevchenko
2021-05-03 11:35               ` Arnd Bergmann
2021-05-03 11:35                 ` Arnd Bergmann
2021-05-03 11:35                 ` Arnd Bergmann
2021-05-03 11:35                 ` Arnd Bergmann
2021-05-03  9:49             ` Kirill A. Shutemov
2021-05-03  9:49               ` Kirill A. Shutemov
2021-05-03  9:49               ` Kirill A. Shutemov
2021-05-03  9:49               ` Kirill A. Shutemov
2021-05-02 21:23           ` Joe Perches
2021-05-02 21:23             ` Joe Perches
2021-05-02 21:23             ` Joe Perches
2021-05-02 21:23             ` Joe Perches
2021-05-03  0:44             ` Segher Boessenkool
2021-05-03  0:44               ` Segher Boessenkool
2021-05-03  0:44               ` Segher Boessenkool
2021-05-03  0:44               ` Segher Boessenkool
2021-05-03  9:57               ` Arnd Bergmann
2021-05-03  9:57                 ` Arnd Bergmann
2021-05-03  9:57                 ` Arnd Bergmann
2021-05-03  9:57                 ` Arnd Bergmann
2021-05-04  7:56     ` Ben Dooks
2021-05-04  7:56       ` Ben Dooks
2021-05-04  7:56       ` Ben Dooks
2021-05-04  7:56       ` Ben Dooks
2021-05-04  8:38       ` Miguel Ojeda
2021-05-04  8:38         ` Miguel Ojeda
2021-05-04  8:38         ` Miguel Ojeda
2021-05-04  8:38         ` Miguel Ojeda
2021-05-04  9:22         ` Michal Suchánek
2021-05-04  9:22           ` Michal Suchánek
2021-05-04  9:22           ` Michal Suchánek
2021-05-04  9:22           ` Michal Suchánek
2021-05-04 12:09           ` Miguel Ojeda
2021-05-04 12:09             ` Miguel Ojeda
2021-05-04 12:09             ` Miguel Ojeda
2021-05-04 12:09             ` Miguel Ojeda
2021-05-04 12:17             ` Michal Suchánek
2021-05-04 12:17               ` Michal Suchánek
2021-05-04 12:17               ` Michal Suchánek
2021-05-04 12:17               ` Michal Suchánek
2021-05-04 12:26               ` Christophe Leroy
2021-05-04 12:26                 ` Christophe Leroy
2021-05-04 12:26                 ` Christophe Leroy
2021-05-04 12:26                 ` Christophe Leroy
2021-05-02 18:37 ` Segher Boessenkool
2021-05-02 18:37   ` Segher Boessenkool
2021-05-02 18:37   ` Segher Boessenkool
2021-05-02 18:37   ` Segher Boessenkool
2021-05-03  6:16 ` Christophe Leroy
2021-05-03  6:16   ` Christophe Leroy
2021-05-03  6:16   ` Christophe Leroy
2021-05-03  6:16   ` Christophe Leroy
2021-05-04  2:13   ` Masahiro Yamada
2021-05-04  2:13     ` Masahiro Yamada
2021-05-04  2:13     ` Masahiro Yamada
2021-05-04  2:13     ` Masahiro Yamada
2021-05-04 13:18   ` Andy Shevchenko
2021-05-04 13:18     ` Andy Shevchenko
2021-05-04 13:18     ` Andy Shevchenko
2021-05-04 13:18     ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-03 12:27   ` David Sterba
2021-05-03 12:27   ` David Sterba
2021-05-03 12:27   ` David Sterba
2021-05-15  7:14 ` Pavel Machek
2021-05-15  7:14   ` Pavel Machek
2021-05-15  7:14   ` Pavel Machek
2021-05-15  7:14   ` Pavel Machek
2021-05-15  7:27   ` Joe Perches
2021-05-15  7:27     ` Joe Perches
2021-05-15  7:27     ` Joe Perches
2021-05-15  7:27     ` Joe Perches

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=CAK8P3a0kV4ZfMEFh0DcMDjXqxA0yhj8a8CL-YFGV6B4pszHeGg@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=aou@eecs.berkeley.edu \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masahiroy@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    /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.