public inbox for dwarves@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	dwarves@vger.kernel.org
Subject: Re: [PATCH dwarves 1/2] tests/flexible_arrays: redirect stderr to avoid warnings
Date: Thu, 24 Oct 2024 10:45:44 -0300	[thread overview]
Message-ID: <ZxpPiOgly-lbDT5L@x1> (raw)
In-Reply-To: <74f2a4bd-27c9-4f5b-963f-2d1a492c9eec@oracle.com>

On Thu, Oct 24, 2024 at 02:01:21PM +0100, Alan Maguire wrote:
> On 24/10/2024 13:13, Arnaldo Carvalho de Melo wrote:
> > 
> > On Thu, Oct 24, 2024, 8:26 AM Alan Maguire <alan.maguire@oracle.com
> > <mailto:alan.maguire@oracle.com>> wrote:
> > 
> >     With recent kernel, saw
> > 
> >       2: Flexible arrays accounting: WARNING: still unsuported
> >     BTF_KIND_DECL_TAG(bpf_fastcall) for bpf_cast_to_kern_ctx already
> >     with attribute (bpf_kfunc), ignoring
> >     WARNING: still unsuported BTF_KIND_DECL_TAG(bpf_fastcall) for
> >     bpf_rdonly_cast already with attribute (bpf_kfunc), ignoring
> >     Ok
> > 
> >     Redirect pahole output to avoid seeing the stderr messaging.
> > 
> > 
> > 
> > This is something I kinda expect from these tests, now I want to get
> > hold of such a vmlinux to understand what's needed to address the warning. 
> >  
> > Maybe have a quiet mode for testing just what's supported in a released
> > version when tested by packagers?
> > 
> > Maybe not, as knowing that they have a kernel with a feature unsupported
> > by pahole may be important and should elicit measures to either get a
> > newer version of pahole or disable a still experimental feature in their
> > kernel? 
> > 
> > WDYT?
> > 
> 
> Good point on the visibility of warnings being useful. We have VERBOSE
> already so it seems like having QUIET (implying stderr > /dev/null)
> would be easiest to add at this stage rather than having to add multiple
> levels to VERBOSE. Maybe QUIET isn't even needed though as the above is
> still clearly a test pass, and the messaging doesn't interfere with test
> success.
> 
> Probably best to drop this one for now anyway..

That is what I did, agreed.

I adapted the second one to this fact and applied it, thanks!

- Arnaldo

> > 
> > 
> >     Signed-off -by: Alan Maguire <alan.maguire@oracle.com
> >     <mailto:alan.maguire@oracle.com>>
> >     ---
> >      tests/flexible_arrays.sh | 2 +-
> >      1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> >     diff --git a/tests/flexible_arrays.sh b/tests/flexible_arrays.sh
> >     index 7c21253..e9e3cb0 100755
> >     --- a/tests/flexible_arrays.sh
> >     +++ b/tests/flexible_arrays.sh
> >     @@ -20,7 +20,7 @@ pretty=$(mktemp /tmp/flexible_arrays.data.sh
> >     <http://flexible_arrays.data.sh>.XXXXXX.c)
> > 
> >      echo -n "Flexible arrays accounting: "
> > 
> >     -for struct in $(pahole -F btf --sizes --
> >     with_embedded_flexible_array $vmlinux | cut -f1) ; do
> >     +for struct in $(pahole -F btf --sizes --
> >     with_embedded_flexible_array $vmlinux 2>/dev/null| cut -f1) ; do
> >             pahole $struct > $pretty
> > 
> >             # We need to check for just one tab before the comment as
> >     when expanding unnamed
> >     -- 
> >     2.43.5
> > 

  reply	other threads:[~2024-10-24 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 11:26 [PATCH dwarves 0/2] flexible_arrays tests fixes Alan Maguire
2024-10-24 11:26 ` [PATCH dwarves 1/2] tests/flexible_arrays: redirect stderr to avoid warnings Alan Maguire
     [not found]   ` <CA+JHD923mvOrr9JoKeVkeB1k2PTGSHsi7=6HPrV4tVNF1R=GWA@mail.gmail.com>
2024-10-24 13:01     ` Alan Maguire
2024-10-24 13:45       ` Arnaldo Carvalho de Melo [this message]
2024-10-24 11:26 ` [PATCH dwarves 2/2] tests/flexible_arrays: print flex array struct from same vmlinux Alan Maguire

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=ZxpPiOgly-lbDT5L@x1 \
    --to=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=dwarves@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