BPF List
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Alan Maguire <alan.maguire@oracle.com>,
	bpf@vger.kernel.org, Martin KaFai Lau <martin.lau@linux.dev>
Cc: Nilay Shroff <nilay@linux.ibm.com>
Subject: Re: Kernel build fails if both CONFIG_DEBUG_INFO_BTF and CONFIG_KCSAN are enabled
Date: Tue, 18 Nov 2025 08:47:03 -0800	[thread overview]
Message-ID: <7161e3e3-7bd0-47ec-892d-72a58b06df33@acm.org> (raw)
In-Reply-To: <d296ec97-933a-4b19-aa75-714e69b3ac4f@oracle.com>

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

On 11/18/25 4:07 AM, Alan Maguire wrote:
> hi Bart, thanks for the report! Not a know issue to me at least; I tried
> to reproduce it with pahole v1.31 + gcc 12 and no luck. Would you mind
> sharing a few additional details:
> 
> - compiler version
> - pahole version
> - full .config

Hi Alan,

My answers to your questions are as follows:
* Compiler version: gcc version 14.2.0 (Debian 14.2.0-19+build5)
* pahole version: v1.30
* Kernel config: has been attached to this email.

Thanks,

Bart.

[-- Attachment #2: btf-kcsan-kernel-config.txt.gz --]
[-- Type: application/gzip, Size: 23114 bytes --]

  reply	other threads:[~2025-11-18 16:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 20:40 Kernel build fails if both CONFIG_DEBUG_INFO_BTF and CONFIG_KCSAN are enabled Bart Van Assche
2025-11-18 12:07 ` Alan Maguire
2025-11-18 16:47   ` Bart Van Assche [this message]
2025-11-20 14:20     ` Alan Maguire
2025-11-20 17:53       ` Kernel build fails if both CONFIG_DEBUG_INFO_BTF and CONFIG_CHELSIO_T4=y (was CONFIG_KCSAN) Alan Maguire
2025-11-20 18:05         ` Potnuri Bharat Teja
2025-11-20 22:18           ` Alan Maguire
2025-11-21 17:22             ` Bart Van Assche
2025-11-21 18:15               ` Alan Maguire
2025-11-24 11:48                 ` Potnuri Bharat Teja

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=7161e3e3-7bd0-47ec-892d-72a58b06df33@acm.org \
    --to=bvanassche@acm.org \
    --cc=alan.maguire@oracle.com \
    --cc=bpf@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=nilay@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox