[tcpdump-workers] buildbot failure in OpenCSW Buildbot on tcpdump-solaris10-amd64
The Buildbot has detected a new failure on builder tcpdump-solaris10-amd64 while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-amd64/builds/503 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10x Build Reason: scheduler Build Source Stamp: [branch master] be03cc0b4ae9370ea0483d1504f4a950b22625d3 Blamelist: Hannes Gredler BUILD FAILED: failed shell_2 sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot failure in OpenCSW Buildbot on tcpdump-solaris10-i386
The Buildbot has detected a new failure on builder tcpdump-solaris10-i386 while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-i386/builds/533 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10x Build Reason: scheduler Build Source Stamp: [branch master] be03cc0b4ae9370ea0483d1504f4a950b22625d3 Blamelist: Hannes Gredler BUILD FAILED: failed shell_2 sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot failure in OpenCSW Buildbot on tcpdump-solaris10-sparcv9
The Buildbot has detected a new failure on builder tcpdump-solaris10-sparcv9 while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-sparcv9/builds/505 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10s Build Reason: scheduler Build Source Stamp: [branch master] be03cc0b4ae9370ea0483d1504f4a950b22625d3 Blamelist: Hannes Gredler BUILD FAILED: failed shell_2 sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot failure in OpenCSW Buildbot on tcpdump-solaris10-sparc
The Buildbot has detected a new failure on builder tcpdump-solaris10-sparc while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-sparc/builds/542 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10s Build Reason: scheduler Build Source Stamp: [branch master] be03cc0b4ae9370ea0483d1504f4a950b22625d3 Blamelist: Hannes Gredler BUILD FAILED: failed shell_2 sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot success in OpenCSW Buildbot on tcpdump-solaris10-amd64
The Buildbot has detected a restored build on builder tcpdump-solaris10-amd64 while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-amd64/builds/504 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10x Build Reason: scheduler Build Source Stamp: [branch master] ce1470b1ac57864cd20b577afe15a4a33dc29bdb Blamelist: Francois-Xavier Le Bail Build succeeded! sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot success in OpenCSW Buildbot on tcpdump-solaris10-i386
The Buildbot has detected a restored build on builder tcpdump-solaris10-i386 while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-i386/builds/534 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10x Build Reason: scheduler Build Source Stamp: [branch master] ce1470b1ac57864cd20b577afe15a4a33dc29bdb Blamelist: Francois-Xavier Le Bail Build succeeded! sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot success in OpenCSW Buildbot on tcpdump-solaris10-sparcv9
The Buildbot has detected a restored build on builder tcpdump-solaris10-sparcv9 while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-sparcv9/builds/506 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10s Build Reason: scheduler Build Source Stamp: [branch master] ce1470b1ac57864cd20b577afe15a4a33dc29bdb Blamelist: Francois-Xavier Le Bail Build succeeded! sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] buildbot success in OpenCSW Buildbot on tcpdump-solaris10-sparc
The Buildbot has detected a restored build on builder tcpdump-solaris10-sparc while building tcpdump. Full details are available at: https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-sparc/builds/543 Buildbot URL: https://buildfarm.opencsw.org/buildbot/ Buildslave for this Build: unstable10s Build Reason: scheduler Build Source Stamp: [branch master] ce1470b1ac57864cd20b577afe15a4a33dc29bdb Blamelist: Francois-Xavier Le Bail Build succeeded! sincerely, -The Buildbot ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] BPF_COP support for libpcap
On 18/05/2015 9:31 AM, Mindaugas Rasiukevicius wrote: Michael Richardson wrote: Mindaugas Rasiukevicius wrote: > A while ago NetBSD gained support for BPF_COP instruction, see [1] > for more details. However, now there are use cases of it outside > the NetBSD kernel, e.g. standalone NPF packet filter running as a > program on Linux. Hence I would like to add the support for the > BPF_COP instruction to the pcap_compile() and pcap_dump() of the > libpcap library. It seems like a good thing to have to evolve BPF forward, particularly in light of more and more complex 802.1q and "metro-ethernet" ring layer-2 formats, and walking IPv6 header chains. Yes. It seems that we really wind up needing a registry of co-processor function indexes... which begin to seem like new instructions in some sense. Perhaps the difference is that they are better defined, and more dynamic. If libpcap/bpf goes down the path of having "BPF_COP" as part of the instruction set but not defining any functions then how does libpcap use it? Or not? Is it better to think of BPF_COP as being a "vendor private" instruction? Does having a "vendor private" instruction allow for better compatibility with hardware vendors that produce hardware based packet sniffers? The thought here is that BPF_COP suggests that the vendor private thing should be a coprocessor but if the instruction is just BPF_PRIVATE then it allows the vendor to do with it whatever they wish, without imposing any expectations. Well, the patch just provides the capability to invoke the coprocessor. The benefit of BPF_COP approach is that the vendors can implement their custom coprocessor and use through libpcap/tcpdump without polluting the instruction space. I think the RISC-like coprocessor approach (think of MIPS) is both clean and powerful compared to adding complex instructions. This would suggest that "BPF_COP" is really a "vendor private" thing. Why burden it with meaning something special such as coprocessor? It would be good to have some general purpose coprocessor (for walking IPv6 header chain and other operations), but that would probably be difficult to agree and standardise amongst the vendors. Which speaks to BPF needing new instructions or a new instruction set that can handle those tasks. Cheers, Darren ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
