public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kvm@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: Fw: [linux-next:master] BUILD REGRESSION 9ce08dd7ea24253aac5fd2519f9aea27dfb390c9
Date: Wed, 18 Jan 2023 19:53:10 +0000	[thread overview]
Message-ID: <Y8hOJhFVn2sv0tsF@google.com> (raw)
In-Reply-To: <20230117132800.b18b01c3895c26e8d3d003aa@linux-foundation.org>

+Kees, I'm guessing this came in through a hardening branch[*].  I assume using
__DECLARE_FLEX_ARRAY isn't an option since this is a uapi header. :-/

[*] https://lore.kernel.org/all/20230105190548.never.323-kees@kernel.org


On Tue, Jan 17, 2023, Andrew Morton wrote:
> a KVM build error here.
> 
> Begin forwarded message:
> 
> Date: Wed, 18 Jan 2023 00:44:23 +0800
> From: kernel test robot <lkp@intel.com>
> To: Andrew Morton <akpm@linux-foundation.org>
> Cc: netdev@vger.kernel.org, linux-scsi@vger.kernel.org, linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org, Linux Memory Management List <linux-mm@kvack.org>
> Subject: [linux-next:master] BUILD REGRESSION 9ce08dd7ea24253aac5fd2519f9aea27dfb390c9
> 
> 
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 9ce08dd7ea24253aac5fd2519f9aea27dfb390c9  Add linux-next specific files for 20230117
> 
> Error/Warning reports:
> 
> https://lore.kernel.org/oe-kbuild-all/202301100332.4EaKi4d1-lkp@intel.com
> https://lore.kernel.org/oe-kbuild-all/202301171414.xpf8WpXn-lkp@intel.com
> https://lore.kernel.org/oe-kbuild-all/202301171511.4ZszviYP-lkp@intel.com
> 
> Error/Warning: (recently discovered and may have been fixed)
> 
> Documentation/mm/unevictable-lru.rst:186: WARNING: Title underline too short.
> ERROR: modpost: "kunit_running" [drivers/gpu/drm/vc4/vc4.ko] undefined!
> arch/arm/kernel/entry-armv.S:485:5: warning: "CONFIG_ARM_THUMB" is not defined, evaluates to 0 [-Wundef]
> drivers/gpu/drm/ttm/ttm_bo_util.c:364:32: error: implicit declaration of function 'vmap'; did you mean 'kmap'? [-Werror=implicit-function-declaration]
> drivers/gpu/drm/ttm/ttm_bo_util.c:429:17: error: implicit declaration of function 'vunmap'; did you mean 'kunmap'? [-Werror=implicit-function-declaration]
> drivers/scsi/qla2xxx/qla_mid.c:1094:51: warning: format '%ld' expects argument of type 'long int', but argument 5 has type 'unsigned int' [-Wformat=]
> drivers/scsi/qla2xxx/qla_mid.c:1189:6: warning: no previous prototype for 'qla_trim_buf' [-Wmissing-prototypes]
> drivers/scsi/qla2xxx/qla_mid.c:1221:6: warning: no previous prototype for '__qla_adjust_buf' [-Wmissing-prototypes]
> libbpf: failed to find '.BTF' ELF section in vmlinux
> usr/include/asm/kvm.h:508:17: error: expected specifier-qualifier-list before '__DECLARE_FLEX_ARRAY'

  reply	other threads:[~2023-01-18 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 21:28 Fw: [linux-next:master] BUILD REGRESSION 9ce08dd7ea24253aac5fd2519f9aea27dfb390c9 Andrew Morton
2023-01-18 19:53 ` Sean Christopherson [this message]
2023-01-18 19:55   ` Kees Cook

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=Y8hOJhFVn2sv0tsF@google.com \
    --to=seanjc@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=kvm@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