All of
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: Linus Torvalds <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Linux 6.8
Date: Mon, 11 Mar 2024 11:06:16 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Mar 10, 2024 at 02:06:37PM -0700, Linus Torvalds wrote:

[ ... ]

> everybody who sent in early pull requests, you know who you are. But
> before that excitement commences, please do spend a bit of time with
> the now boring old status quo and give 6.8 a good test, ok?

Build results:
	total: 158 pass: 158 fail: 0
Qemu test results:
	total: 549 pass: 549 fail: 0
Unit test results:
	pass: 215772 fail: 302

Nothing news, really. Unit test failures are retty much unchanged.
- mean_and_variance_test_2 and mean_and_variance_test_4 are still broken
  both in mainline and linux-next.
- m68k:q800:stackinit should be fixed in linux-next
- most of the IP checksum test failures are still present in mainline but
  fixed in linux-next. One notable and still unhandled checksum test
  failure is the failure seen in sh4 emulations. It is due to upstream
  commit cadc4e1a2b4d ("sh: Handle calling csum_partial with misaligned
  data") which is broken and would have to be either fixed or reverted.
  I added it to the regression tracker, so it should show up there in
  the near future. 

There are also still some warning backtraces.

- dev-addr-list-test with lock debugging triggers backtraces due to
  conceptual problems with kunit tests (locks are not necessarily
  requested and released from the same thread).
- WARNING: inconsistent lock state in stmmac code.
  Tracked in regression tracker.


  parent reply	other threads:[~2024-03-11 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 21:06 Linux 6.8 Linus Torvalds
2024-03-11  8:05 ` Build regressions/improvements in v6.8 Geert Uytterhoeven
2024-03-11 18:06 ` Guenter Roeck [this message]
2024-03-13 19:30 ` Linux 6.8 Frank Scheiner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.