linux-kernel - Re: Linux 6.13

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 for Android: free password hash cracker in your pocket

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

Message-ID: <8f6624e2-de02-4fa1-a76f-64c2a7c86acc@roeck-us.net>
Date: Mon, 20 Jan 2025 06:23:28 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 6.13

On Sun, Jan 19, 2025 at 04:52:53PM -0800, Linus Torvalds wrote:
> So nothing horrible or unexpected happened last week, so I've tagged
> and pushed out the final 6.13 release.
> 
> It's mostly some final driver fixes (gpu and networking dominating -
> normal), with some doc updates too. And various little stuff all over.
> The shortlog is appended for people who want to see the details (and,
> as always, it's just the shortlog for the last week, the full 6.13 log
> is obviously much too big).
> 

Here is the final test verdict:

Build results:
	total: 161 pass: 161 fail: 0
Qemu test results:
	total: 544 pass: 544 fail: 0
Unit test results:
	pass: 470848 fail: 0

There is one left-over runtime backtrace introduced since 6.12.

[ BUG: Invalid wait context ]
6.13.0 #1 Not tainted

This is seen on sparc64 systems. The problem is known, and the fix is
queued in linux-next.

Guenter