BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
	bpf@vger.kernel.org,  ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kafai@meta.com,  kernel-team@meta.com,
	Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next v7] selftests/bpf: add BPF program dump in veristat
Date: Fri, 05 Sep 2025 14:43:44 -0700	[thread overview]
Message-ID: <84b34c685418234c21bb3c127bb966d5744efc59.camel@gmail.com> (raw)
In-Reply-To: <CAEf4BzawRYXXSJDiK4GzuYo=g-N_-QMgUXQAGN15eaPYuWXBWQ@mail.gmail.com>

On Fri, 2025-09-05 at 14:38 -0700, Andrii Nakryiko wrote:

[...]

> > > > Fun fact: if you do a minimal Fedora install (dnf group install core)
> > > >           "which" is not installed by default o.O
> > > >           (not suggesting any changes).
> > > 
> > > I switched to `command -v bpftool` for now, is there any gotcha with
> > > that one as well?
> > 
> > Should be fine, I guess:
> > 
> >   $ rpm -qf /usr/sbin/command
> >   bash-5.2.37-1.fc42.x86_64
> 
> command is actually a shell built-in ([0]). At least for Bourne shells, I think.
> 
>   [0] https://pubs.opengroup.org/onlinepubs/009695399/utilities/command.html
>

Yes, but looks like it's a separate binary, not a command:

  $ strace command -v ls 2>&1 | grep command
  execve("/usr/bin/command", ["command", "-v", "ls"], 0x7ffffeaef7b0 /* 65 vars */) = 0

(Not that it changes much).

[...]

  reply	other threads:[~2025-09-05 21:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 14:08 [PATCH bpf-next v7] selftests/bpf: add BPF program dump in veristat Mykyta Yatsenko
2025-09-05 19:00 ` Eduard Zingerman
2025-09-05 19:14   ` Andrii Nakryiko
2025-09-05 19:19     ` Eduard Zingerman
2025-09-05 21:38       ` Andrii Nakryiko
2025-09-05 21:43         ` Eduard Zingerman [this message]
2025-09-05 21:51           ` Andrii Nakryiko
2025-09-05 22:00             ` Eduard Zingerman

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=84b34c685418234c21bb3c127bb966d5744efc59.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kafai@meta.com \
    --cc=kernel-team@meta.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=yatsenko@meta.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