From: Eduard Zingerman <eddyz87@gmail.com>
To: Stephen Brennan <stephen.s.brennan@oracle.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Alan Maguire <alan.maguire@oracle.com>,
dwarves@vger.kernel.org, linux-debuggers@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix duplicated VAR and secinfo
Date: Thu, 20 Feb 2025 17:30:51 -0800 [thread overview]
Message-ID: <d3c1201ab0ff7831b03cf9cd00afb09696e6e40b.camel@gmail.com> (raw)
In-Reply-To: <875xl4kszj.fsf@oracle.com>
On Thu, 2025-02-20 at 17:05 -0800, Stephen Brennan wrote:
[...]
> Thank you for the testing (and the review). I haven't yet been able to
> reproduce this. But I see you're using clang. I'll spend the morning
> building & running selftests with clang to see whether that is the
> issue.
Right, should have pointed that out in the email.
Clang version is 19.1.7.
Just tried with gcc, and `./test_progs -n 1` indeed works.
Then re-tried with clang, same result as yesterday, test fails.
Thanks,
Eduard
next prev parent reply other threads:[~2025-02-21 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 0:49 [PATCH 0/3] Fix duplicated VAR and secinfo Stephen Brennan
2025-02-12 0:49 ` [PATCH 1/3] btf_encoder: move btf_encoder__add_decl_tag() Stephen Brennan
2025-02-12 0:49 ` [PATCH 2/3] btf_encoder: postpone VARs until encoding DATASEC Stephen Brennan
2025-02-19 23:51 ` Eduard Zingerman
2025-02-12 0:49 ` [PATCH 3/3] btf_encoder: don't encode duplicate variables Stephen Brennan
2025-02-12 17:57 ` Alan Maguire
2025-02-12 18:21 ` Stephen Brennan
2025-02-18 10:36 ` [PATCH 0/3] Fix duplicated VAR and secinfo Alan Maguire
2025-02-18 16:54 ` Stephen Brennan
2025-02-19 7:48 ` Eduard Zingerman
2025-02-20 2:26 ` Eduard Zingerman
2025-02-21 1:05 ` Stephen Brennan
2025-02-21 1:30 ` Eduard Zingerman [this message]
2025-02-25 1:16 ` Stephen Brennan
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=d3c1201ab0ff7831b03cf9cd00afb09696e6e40b.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=dwarves@vger.kernel.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=stephen.s.brennan@oracle.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