From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Waqar Hameed <waqar.hameed@axis.com>,
Ingo Molnar <mingo@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel@axis.com, Richard Weinberger <richard@nod.at>,
linux-um@lists.infradead.org
Subject: Re: pcap-dbus.o:undefined reference to `dbus_message_demarshal'
Date: Thu, 07 Mar 2024 11:29:45 +0100 [thread overview]
Message-ID: <a485fbdea26e19afe00f603bd65c83e2be20abe6.camel@sipsolutions.net> (raw)
In-Reply-To: <2cc222b7-618c-46a9-b78b-eb099d0f4be7@cambridgegreys.com>
On Thu, 2024-03-07 at 10:27 +0000, Anton Ivanov wrote:
> >
> > How's that required to be formatted and loaded? tcpdump itself can also
> > dump the filter in BPF format, with -d/-ddd (-dd is a C representation,
> > so probably not useful). Perhaps we could even automatically call
> > 'tcpdump' at runtime?
>
> That is one option.
>
> As far as common use cases are concerned, at present you can:
>
> tcpdump -ddd, convert it to raw binary (3 liner in a language of choice) and pass that to vecX as a bpffile=
>
> It may be worth it to make vecX also take the -ddd format directly by adding "format" options to bpffile.
>
> I'd rather do that instead of invoking tcpdump out of a device open. The -ddd notation (+/- a comma here and there) is
> standard - it is also used by iptables, etc. It can used by other code generators as well.
Yeah, that makes sense, this is all kind of special configuration
anyway, and given that it's been broken forever ...
I actually doubt anyone would scream if we just removed it, so maybe
just remove it and if they do scream, point to the above, including said
3-liner in the response?
johannes
next prev parent reply other threads:[~2024-03-07 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 15:11 kernel test robot
2024-03-06 16:14 ` Waqar Hameed
2024-03-07 9:54 ` Anton Ivanov
2024-03-07 10:03 ` Johannes Berg
2024-03-07 10:27 ` Anton Ivanov
2024-03-07 10:29 ` Johannes Berg [this message]
2024-03-07 10:49 ` Anton Ivanov
2024-03-07 11:31 ` Waqar Hameed
-- strict thread matches above, loose matches on Subject: below --
2024-04-26 10:13 kernel test robot
2024-02-14 5:02 kernel test robot
2024-01-07 18:07 kernel test robot
2023-10-10 0:52 kernel test robot
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=a485fbdea26e19afe00f603bd65c83e2be20abe6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
--cc=waqar.hameed@axis.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
Powered by JetHome