linux-kernel - Re: Linux 6.17-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aJnuQXzFxiFPkk6T@black.igk.intel.com>
Date: Mon, 11 Aug 2025 15:21:05 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 6.17-rc1

On Sun, Aug 10, 2025 at 08:08:47PM +0300, Linus Torvalds wrote:
> So two weeks have passed, and depending on how you see it, rc1 is
> either earlier than usual (it's only Sunday morning back home in the
> usual timezone) or later than usual (because it's getting to be Sunday
> evening here in Finland where I'm cutting the release). I decided to
> basically split the difference on my usual "early Sunday afternoon"
> schedule.
> 
> Anyway, due to travels, I wanted to do most of the heavy lifting the
> first week, and I can happily report that that part worked out well. I
> wouldn't want to do this most merge windows, but the bulk of the work
> was done before travel, and that meant that the straggler pulls were
> manageable while traveling. Thanks to everybody who got their pulls in
> early - you know who you are.
> 
> And the late stragglers then got a slightly more annoyed Linus as a
> result. Sorry about that.
> 
> Anyway, the merge window did end up looking fairly healthy, despite me
> having to go through a couple of bisections for trouble spots (one
> during travels with a laptop - not optimal, but thankfully it was at
> least one of the "reliable symptoms that bisect right to the culprit"
> kind). The stats look pretty normal both in patch size and in number
> of commits. That number being large enough that - as always - you only
> get the mergelog below as a kind of "view from 10,000ft" of the
> development process this time around.
> 
> Please do get started testing and fixing,

FWIW, it's broken in c couple of places for `make W=1` builds, details below.

ext4:
commit 261a2abe20b0 ("ext4: fix unused variable warning in ext4_init_new_dir")
in Linux Next, but missed rc1

timers, etc (clang only):
discussion and partial fix is here
https://lore.kernel.org/all/aIo18KZpmKuR4hVZ@black.igk.intel.com/
https://lore.kernel.org/lkml/20250804220955.1453135-1-dan.j.williams@intel.com/

(haven't tested full allyesconfig and allmodconfig, though)

-- 
With Best Regards,
Andy Shevchenko