From: Nathan Chancellor <nathan@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Kees Cook <kees@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
llvm@lists.linux.dev
Subject: Re: [LLVM/Clang] Known issues with Linux v6.12.39 and CFI
Date: Sat, 19 Jul 2025 13:10:25 -0400 [thread overview]
Message-ID: <20250719171025.GA2048381@ax162> (raw)
In-Reply-To: <CA+icZUV_NGd5R3=YdE9zg7HeBK1adhj_j7Kpp5-GhOMJLsXyWw@mail.gmail.com>
On Thu, Jul 17, 2025 at 09:54:24PM +0200, Sedat Dilek wrote:
> Hi LLVM/Clang folks,
>
> Hope you are well.
>
> Writing from a Windows host...
>
> So, Debian/trixie aka version 13 is FROZEN and will be released soon.
>
> I was using LLVM toolchains from kernel.org - my last Linux-kernel was
> version 6.12.11 compiled with LLVM-19.1.6 released 17-Dec-2024,
>
> Normally, I use Debian's kernel-config - modified to Clang-CFI and
> using mostly ZSTD settings where possible (ZRAM, (de)compress
> initramfs, etc.).
>
> Are there additional patches necessary - kernel-side - planning with
> v6.12.39 released some hours ago?
> As you can see I did not follow Kernel development for a while - 6 months or so.
As Sami noted, there should be no kCFI regressions from 6.12.11 to
6.12.39. We are not carrying any patches for 6.12 in CI right now, so
everything else should be fine as well but bugs are always welcome.
Cheers,
Nathan
next prev parent reply other threads:[~2025-07-19 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 19:54 [LLVM/Clang] Known issues with Linux v6.12.39 and CFI Sedat Dilek
2025-07-18 15:09 ` Sami Tolvanen
2025-07-19 17:10 ` Nathan Chancellor [this message]
2025-11-02 15:43 ` Sedat Dilek
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=20250719171025.GA2048381@ax162 \
--to=nathan@kernel.org \
--cc=kees@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=samitolvanen@google.com \
--cc=sedat.dilek@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox