[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

linux-next: build failure after merge of the xen-tip tree

To: Val Packett <val@xxxxxxxxxxxxxxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Mark Brown <broonie@xxxxxxxxxx>
Date: Tue, 4 Aug 2026 17:28:36 +0100
Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=k20260515 header.d=kernel.org header.i="@kernel.org" header.h="Date:From:To:Cc:Subject"
Cc: Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>
Delivery-date: Tue, 04 Aug 2026 16:28:49 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hi all,

After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:

ERROR: modpost: "init_mm" [drivers/xen/xen-privcmd.ko] undefined!

Caused by commit

  64d26fb2ad1f2 (xen: privcmd: fix ioeventfd crash under PV domain)

I have used the tree from next-20260803 instead.

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: linux-next: build failure after merge of the xen-tip tree
  - From: Jürgen Groß
- Re: linux-next: build failure after merge of the xen-tip tree
  - From: Val Packett

Prev by Date: Re: [PATCH v1 1/6] tools/migration: introduce PAGE_DATA_LZ4 stream record type
Next by Date: Re: [PATCH 2/3] x86/alternatives: Rework get_ideal_nops()
Previous by thread: Re: [PATCH 2/5] vtd: Ensure context entry is cleared properly
Next by thread: Re: linux-next: build failure after merge of the xen-tip tree
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.