Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: KUnit failure after merge of the mm-nonmm-unstable tree
Date: Sun, 5 Jul 2026 13:27:23 +0100	[thread overview]
Message-ID: <akpNqwC2M1MMzR8P@sirena.co.uk> (raw)
In-Reply-To: <afc8f908-4add-4da8-816c-9a6c06619b18@p183>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

On Sat, Jul 04, 2026 at 07:55:40AM +0300, Alexey Dobriyan wrote:
> On Fri, Jul 03, 2026 at 05:39:59PM +0100, Mark Brown wrote:

> > > [14:22:11] [FAILED] cmdline_test_memparse
> > > [14:22:11]     # module: cmdline_kunit

> > bisect tells me it's due to:

> >   e595545005616 (Revert "lib: fix _parse_integer_limit() to handle overflow")

> No, it is due to

> 	commit 9a4580db6e9f83428813f671a79486469684069f
> 	lib: fix memparse() to handle overflow

> memparse should be rewritten with _parse_integer().

Huh, that was my first guess when I looked at the log but I didn't spot
the relevance so wanted to check then it seems the bisect got confused
somehow.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-07-05 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 14:43 linux-next: KUnit failure after merge of the mm-nonmm-unstable tree Mark Brown
2026-07-03 16:39 ` Mark Brown
2026-07-04  4:55   ` Alexey Dobriyan
2026-07-05 12:27     ` Mark Brown [this message]

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=akpNqwC2M1MMzR8P@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox