All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Jackman <jackmanb@google.com>
To: syzbot ci <syzbot+cie262549d3c7e101a@syzkaller.appspotmail.com>,
	 <akpm@linux-foundation.org>, <jackmanb@google.com>,
	 <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<urezki@gmail.com>
Cc: <syzbot@lists.linux.dev>, <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot ci] Re: mm/vmalloc: clarify why vmap_range_noflush() might sleep
Date: Tue, 09 Dec 2025 02:56:45 +0000	[thread overview]
Message-ID: <DETCJPVHXE8O.2A2XQ73M2QOGK@google.com> (raw)
In-Reply-To: <693691ac.a70a0220.38f243.009a.GAE@google.com>

On Mon Dec 8, 2025 at 8:51 AM UTC, syzbot ci wrote:
> kernel build error
>
> tree:      mm-new
> URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base:      3f43be96f919cc611dcb2a4e38dd464831f4513e
> arch:      amd64

Um, so apparently I didn't even compile this code for x86? Sorry about
this.

FWIW, I do test my patches [0]! Apparently in this case I just decided
to post it without actually checking the results.

[0] https://github.com/bjackman/limmat-kernel-nix


  reply	other threads:[~2025-12-09  2:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  5:19 [PATCH] mm/vmalloc: clarify why vmap_range_noflush() might sleep Brendan Jackman
2025-12-08  6:41 ` Anshuman Khandual
2025-12-08  7:39   ` Brendan Jackman
2025-12-08 17:32     ` Uladzislau Rezki
2025-12-08  8:51 ` [syzbot ci] " syzbot ci
2025-12-09  2:56   ` Brendan Jackman [this message]
2025-12-09  1:10 ` [PATCH] " kernel test robot
2025-12-09  1:52 ` kernel test robot

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=DETCJPVHXE8O.2A2XQ73M2QOGK@google.com \
    --to=jackmanb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+cie262549d3c7e101a@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=urezki@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 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.