All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Brian Gerst" <brgerst@gmail.com>,
	"Uros Bizjak" <ubizjak@gmail.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	"Ingo Molnar" <mingo@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Borislav Petkov" <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	mwilck@suse.com, tiwai@suse.de, vbabka@suse.cz,
	denis.kirjanov@suse.com, nmorey@suse.com
Subject: Re: [PATCH v4 00/16] x86-64: Stack protector and percpu improvements
Date: Mon, 25 Mar 2024 16:26:40 +0100	[thread overview]
Message-ID: <871q7yxrgv.wl-tiwai@suse.de> (raw)
In-Reply-To: <ef640185-21e2-46a8-839c-d81030fb13f8@app.fastmail.com>

On Mon, 25 Mar 2024 15:51:30 +0100,
Arnd Bergmann wrote:
> 
> On Sat, Mar 23, 2024, at 18:06, Linus Torvalds wrote:
> > On Sat, 23 Mar 2024 at 09:16, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > The SLES situation seems somewhat similar, with SLES12 being 4.8.x and
> > SLES15 being 7.3. But again with a "Development Tools Module" setup.
> > So that *might* argue for 7.3.
> 
> According to https://distrowatch.com/table.php?distribution=sle, they
> also provide gcc-12.2.1 with the sp5 update, so we're probably fine.
> 
> On the other hand, I can see that OpenSUSE Leap 15.6 contains
> a fairly modern kernel (6.4.x) built with the gcc-7.3 system
> compiler, and I think this is the same one as in SLES.
> 
> Not sure if they plan to update the kernel release beyond that,
> or how inconvenient it would be for them to require
> using the other compiler for future updates, so I've added
> the developers that last touched the OpenSUSE kernel RPM
> package to Cc here.

SLE15-SP6 kernel (based on 6.4.x) is still built with gcc7, currently
gcc 7.5, indeed.  openSUSE Leap shares the very same kernel, so it's
with gcc 7.5, too.  Even though gcc-13 is provided as additional
compiler package, it's not used for the kernel package build.

AFAIK, it's not decided yet about SP7 kernel.  But since we take a
conservative approach for SLE, I guess SLE15-SP7 will be likely
sticking with the old gcc, unless forced to change by some reason.

SLE12 is built with the old gcc 4.8, and SLE12-SP5 (based on 4.12) is
still actively maintained, but only for a few months until October
2024.

The next generation of SLE is built with the latest gcc (gcc-13 for
now).  So SLE16 will be a totally different story.

openSUSE Tumbleweed always uses a bleeding edge compiler (gcc-13),
too.


Takashi

  reply	other threads:[~2024-03-25 15:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 16:52 [PATCH v4 00/16] x86-64: Stack protector and percpu improvements Brian Gerst
2024-03-22 16:52 ` [PATCH v4 01/16] x86/stackprotector/32: Remove stack protector test script Brian Gerst
2024-03-23 17:00   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 02/16] x86/stackprotector/64: " Brian Gerst
2024-03-23 17:01   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 03/16] x86/boot: Disable stack protector for early boot code Brian Gerst
2024-03-22 16:52 ` [PATCH v4 04/16] x86/pvh: Use fixed_percpu_data for early boot GSBASE Brian Gerst
2024-03-22 16:52 ` [PATCH v4 05/16] x86/relocs: Handle R_X86_64_REX_GOTPCRELX relocations Brian Gerst
2024-03-22 16:52 ` [PATCH v4 06/16] objtool: Allow adding relocations to an existing section Brian Gerst
2024-03-22 16:52 ` [PATCH v4 07/16] objtool: Convert fixed location stack protector accesses Brian Gerst
2024-03-22 16:52 ` [PATCH v4 08/16] x86/stackprotector/64: Convert to normal percpu variable Brian Gerst
2024-03-23 17:11   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 09/16] x86/percpu/64: Use relative percpu offsets Brian Gerst
2024-03-23 17:14   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 10/16] x86/percpu/64: Remove fixed_percpu_data Brian Gerst
2024-03-23 17:14   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 11/16] x86/boot/64: Remove inverse relocations Brian Gerst
2024-03-22 16:52 ` [PATCH v4 12/16] x86/percpu/64: Remove INIT_PER_CPU macros Brian Gerst
2024-03-23 17:15   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 13/16] percpu: Remove PER_CPU_FIRST_SECTION Brian Gerst
2024-03-23 17:17   ` Uros Bizjak
2024-03-22 16:52 ` [PATCH v4 14/16] percpu: Remove PERCPU_VADDR() Brian Gerst
2024-03-22 16:52 ` [PATCH v4 15/16] percpu: Remove __per_cpu_load Brian Gerst
2024-03-22 16:52 ` [PATCH v4 16/16] kallsyms: Remove KALLSYMS_ABSOLUTE_PERCPU Brian Gerst
2024-03-23 11:39 ` [PATCH v4 00/16] x86-64: Stack protector and percpu improvements Uros Bizjak
2024-03-23 13:22   ` Brian Gerst
2024-03-23 16:16     ` Linus Torvalds
2024-03-23 17:06       ` Linus Torvalds
2024-03-24 19:09         ` David Laight
2024-03-25 14:51         ` Arnd Bergmann
2024-03-25 15:26           ` Takashi Iwai [this message]
2024-03-25 18:08             ` Arnd Bergmann
2024-03-26  7:02               ` Uros Bizjak
2024-03-23 22:55       ` Arnd Bergmann
2024-03-25 15:14         ` Ard Biesheuvel
2024-03-24  2:25   ` Ingo Molnar
2024-03-24  3:51     ` Brian Gerst
2024-03-24  4:05       ` Ingo Molnar
2024-03-24  5:43         ` Brian Gerst
2024-03-24 10:53           ` Ingo Molnar
2024-03-24 12:34             ` Brian Gerst
2024-03-24 18:14               ` Ingo Molnar

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=871q7yxrgv.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=denis.kirjanov@suse.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mwilck@suse.com \
    --cc=nmorey@suse.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=ubizjak@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=x86@kernel.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.