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:03:32 +0100 [thread overview]
Message-ID: <463be980baf66b967031e3294c3b9745b07aa058.camel@sipsolutions.net> (raw)
In-Reply-To: <87cfca1e-3f53-4935-a274-0920bce86373@cambridgegreys.com>
On Thu, 2024-03-07 at 09:54 +0000, Anton Ivanov wrote:
>
> PCAP is not feasible to incorporate into the build system at present.
> It has grown all kinds of warts over the years and brings a lot of dependencies.
> IMHO we should remove it from the tree. It has reached a point where it cannot
> be built on a modern system.
I suppose it might be possible to call pcap-config? But agree that it
doesn't seem really worth investing in.
> The users who need the same functionality can produce a bpf filter using tcpdump
> and load it as "firmware" into the vector/raw driver.
>
> I am working on a pure python bpf compiler which takes the same syntax as PCAP.
> It is showing signs of life and it can do some of the simpler use cases. Once
> that is ready, it should be possible to use that instead of pcap/tcpdump.
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?
johannes
next prev parent reply other threads:[~2024-03-07 10:03 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 [this message]
2024-03-07 10:27 ` Anton Ivanov
2024-03-07 10:29 ` Johannes Berg
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=463be980baf66b967031e3294c3b9745b07aa058.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
all inboxes | Powered by JetHome®