GitHub pull request #2885 of commit ceb458d6a07a42d8d6d3c16a3b8e387b5131d610, has merge conflicts.sha1ceb458d6a07a42d8d6d3c16a3b8e387b5131d610ghprbActualCommitceb458d6a07a42d8d6d3c16a3b8e387b5131d610ghprbActualCommitAuthorghprbActualCommitAuthorEmailghprbAuthorRepoGitUrlhttps://github.com/sabbene/bcc.gitghprbTriggerAuthorghprbTriggerAuthorEmailghprbTriggerAuthorLoginyonghong-songghprbTriggerAuthorLoginMention@yonghong-songghprbPullId2885ghprbTargetBranchmasterghprbSourceBranchmasterGIT_BRANCHmasterghprbPullAuthorEmailghprbPullAuthorLoginsabbeneghprbPullAuthorLoginMention@sabbeneghprbPullDescriptionGitHub pull request #2885 of commit ceb458d6a07a42d8d6d3c16a3b8e387b5131d610, has merge conflicts.ghprbPullTitleadd support for nfs version 3 to nfsdist.pyghprbPullLinkhttps://github.com/iovisor/bcc/pull/2885ghprbPullLongDescriptionAdding an option to explicitly trace nfs version 3 or 4 operations.ghprbCommentBody[buildbot, test this please]ghprbGhRepositoryiovisor/bccghprbCredentialsId6d3daf13-69b8-48b1-9c8f-ec5353264113471ceb458d6a07a42d8d6d3c16a3b8e387b5131d610ceb458d6a07a42d8d6d3c16a3b8e387b5131d610detachedceb458d6a07a42d8d6d3c16a3b8e387b5131d610ceb458d6a07a42d8d6d3c16a3b8e387b5131d610detachedceb458d6a07a42d8d6d3c16a3b8e387b5131d610ceb458d6a07a42d8d6d3c16a3b8e387b5131d610detachedhttps://github.com/iovisor/bcc.gitfalse<a title="add support for nfs version 3 to nfsdist.py" href="https://github.com/iovisor/bcc/pull/2885">PR #2885</a>: add support for nfs version...#47116063867460664bcc-pr #471471false4713776SUCCESS1588729217933https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/471/- tests/cc/test_usdt_probes.ccsrc/cc/libbpf.cc6a3f0298ebf0ec1cb1c455320876da5b4a0b07b1579623538000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comRemove namespace code from libbpf to fix USDT
This removes the namespace code from libbpf, as they are no longer necessary
since #2324 was merged, and have caused regressions on older Kernels that do
not use the new API for creating probes. This also deletes the dead code for
namespace handling in libbpf, as this was the last use of it.
This also introduces regression tests to ensure that processes in containers
can be USDT probed, by adding tests that unshare the mount and process
namespaces.
2020-01-21 08:18:58 -0800c6a3f0298ebf0ec1cb1c455320876da5b4a0b07bRemove namespace code from libbpf to fix USDTeditsrc/cc/libbpf.cedittests/cc/test_usdt_probes.cc
- examples/networking/simulation.pydbfb18851866254a7b127146c8a9c2d76260ee781579714917000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comfix a bug in networking/simulation.py
test test_brb.py failed on fc31 with the following error messages:
Traceback (most recent call last):
File "./test_brb.py", line 162, in test_brb
disable_ipv6=True)
File "/home/yhs/work/bcc/tests/python/simulation.py", line 94, in _create_ns
disable_ipv6)
File "/home/yhs/work/bcc/tests/python/simulation.py", line 68, in _ns_add_ifc
ns_ipdb.interfaces.lo.up().commit()
File "/usr/local/lib/python3.7/site-packages/pyroute2/ipdb/interfaces.py", line 1078, in commit
raise error
File "/usr/local/lib/python3.7/site-packages/pyroute2/ipdb/interfaces.py", line 859, in commit
transaction.wait_all_targets()
File "/usr/local/lib/python3.7/site-packages/pyroute2/ipdb/transactional.py", line 507, in wait_all_targets
raise CommitException('target %s is not set' % key)
pyroute2.ipdb.exceptions.CommitException: target state is not set
The reason is in networking/simulation.py, if the interface 'lo'
inside the namespace is already up and it is tried to commit
to 'up' state again, the pyroute2 library will cause an exception.
The fix is to avoid to 'up' interface 'lo' again if the interface
is already in 'up' state.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-01-22 09:41:57 -0800dbfb18851866254a7b127146c8a9c2d76260ee78fix a bug in networking/simulation.pyeditexamples/networking/simulation.py
- tools/profile.py0cafe5571865d4dcab8ff2bd398b41dbc10b42f41579752366000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comfix line TypeError
./profile.py -adf -p `pgrep -n main` 5
Traceback (most recent call last):
File "./profile.py", line 342, in <module>
print("%s %d" % (b";".join(line).decode('utf-8', 'replace'), v.value))
TypeError: sequence item 5: expected a bytes-like object, str found
2020-01-22 20:06:06 -08000cafe5571865d4dcab8ff2bd398b41dbc10b42f4fix line TypeErroredittools/profile.py
- src/cc/libbpfsrc/cc/libbpf.csrc/cc/compat/linux/virtual_bpf.hintrospection/bps.cdocs/kernel-versions.md83b67c2a05b107ffc27cb9b8cec0bec9f5c43a841580166073000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comsync to latest libbpf repo
Sync to latest libbpf repo. New helper bpf_jiffies64
and new program type BPF_PROG_TYPE_EXT is added.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-01-27 15:01:13 -080083b67c2a05b107ffc27cb9b8cec0bec9f5c43a84sync to latest libbpf repoeditsrc/cc/compat/linux/virtual_bpf.heditsrc/cc/libbpf.ceditintrospection/bps.ceditsrc/cc/libbpfeditdocs/kernel-versions.md
- .gitignore.github/workflows/bcc-test.ymltests/wrapper.sh.intests/python/test_stackid.pytests/python/test_debuginfo.pytests/python/test_trace3.pytests/python/test_tools_smoke.pytests/python/utils.pytests/cc/test_c_api.cctests/python/test_brb2.pytests/python/test_usdt2.pytests/python/test_usdt.pytests/python/test_usdt3.pyexamples/networking/simulation.pyDockerfile.teststests/cc/test_usdt_probes.cca47c44fa0d570b64d8cb06449052db4f363e80a41580314798000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comRun BCC test suite with github actions
With this commit, pushes to branches can trigger tests directly on
Github Actions.
Here it will be able to test against kernel 4.14 and 5.0.0, which correspond
to the latest Ubuntu LTS kernel releases.
Tests are run for both Debug and Release modes.
Tests run inside docker, in an ubuntu 19.04 container base.
For the github workflow:
- The test_libbcc suite is run first, to potentially fail fast on these faster
unit tests.
- The Python test suite is run
Some of these tests are allowed to fail, but the failure is still reported:
- In catch2 tests, using the [!mayfail] tag, where this will be displayed in
the test summary
- In Python unittests, using the `@mayFail("Reason")` decorator, which is
introduce for consistency with catch2. These will report the reason for the
failure, and log this to an artifact of the test.
2020-01-29 08:19:58 -0800a47c44fa0d570b64d8cb06449052db4f363e80a4Run BCC test suite with github actionseditexamples/networking/simulation.pyedittests/python/test_trace3.pyaddDockerfile.testsedittests/cc/test_usdt_probes.ccedittests/wrapper.sh.inadd.github/workflows/bcc-test.ymledittests/cc/test_c_api.ccedittests/python/utils.pyedittests/python/test_tools_smoke.pyedit.gitignoreedittests/python/test_usdt2.pyedittests/python/test_debuginfo.pyedittests/python/test_usdt.pyedittests/python/test_brb2.pyedittests/python/test_usdt3.pyedittests/python/test_stackid.py
- src/cc/api/BPF.cctests/python/test_usdt3.pytests/python/test_usdt.pytests/python/test_usdt2.pysrc/cc/usdt.hsrc/cc/api/BPF.hb090f5f9eee62796829184ec862e3378a3b7e4251580351171000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comMake inode-only matching default, reverse USDT kludge
2020-01-29 18:26:11 -0800b090f5f9eee62796829184ec862e3378a3b7e425Make inode-only matching default, reverse USDT kludgeeditsrc/cc/api/BPF.ccedittests/python/test_usdt3.pyedittests/python/test_usdt.pyedittests/python/test_usdt2.pyeditsrc/cc/usdt.heditsrc/cc/api/BPF.h
- README.md215b7243a074afc454d5cc092e9e45350ee2a6671580425436000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comremove dead link
solves #2722
2020-01-30 15:03:56 -0800215b7243a074afc454d5cc092e9e45350ee2a667remove dead linkeditREADME.md
- tools/klockstat.py90b2382b2068031930704d42205829b356f41ffb1580434301000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools/klockstat.py: Do not display symbol twice for stack
Currently we display the caller symbol in stack,
which ends up with output below when we enable stack:
Caller Avg Hold Count Max hold Total hold
b'flush_to_ldisc+0x22' 56112 2 103914 112225
b'flush_to_ldisc+0x22'
b'process_one_work+0x1b0'
b'worker_thread+0x50'
b'kthread+0xfb'
Skipping one more symbol in stack to fix that:
Caller Avg Hold Count Max hold Total hold
b'flush_to_ldisc+0x22' 1893 2 2765 3787
b'process_one_work+0x1b0'
b'worker_thread+0x50'
b'kthread+0xfb'
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-01-30 17:31:41 -080090b2382b2068031930704d42205829b356f41ffbtools/klockstat.py: Do not display symbol twice for stackedittools/klockstat.py
- src/cc/frontends/clang/b_frontend_action.cc0e63c5c1ad267281f8d0b652eaf87dd494ddba041580434349000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comfix compilation error due to latest llvm change
llvm 11.0 required explicit conversion from StringRef to std::string.
The patch is
https://github.com/llvm/llvm-project/commit/777180a32b61070a10dd330b4f038bf24e916af1
This patch made a compatible change which works for old llvm
as well.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-01-30 17:32:29 -08000e63c5c1ad267281f8d0b652eaf87dd494ddba04fix compilation error due to latest llvm changeeditsrc/cc/frontends/clang/b_frontend_action.cc
- src/cc/frontends/clang/b_frontend_action.ccsrc/cc/api/BPFTable.hdocs/reference_guide.mdsrc/cc/api/BPF.ccsrc/cc/api/BPF.hsrc/cc/export/helpers.hsrc/python/bcc/table.pysrc/cc/api/BPFTable.cc46965c6b3790a51ba288093c68b16fab71914f881580492211000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comAdd XSKMAP support (#2730)
* add XSKMAP support
* enable lookup for XSKMAP available from kernel 5.3
* add section for XSKMAP in reference guide
2020-01-31 09:36:51 -080046965c6b3790a51ba288093c68b16fab71914f88Add XSKMAP support (#2730)editsrc/cc/api/BPFTable.cceditsrc/cc/frontends/clang/b_frontend_action.cceditsrc/cc/api/BPF.heditsrc/python/bcc/table.pyeditsrc/cc/api/BPFTable.heditsrc/cc/export/helpers.heditdocs/reference_guide.mdeditsrc/cc/api/BPF.cc
- src/python/bcc/__init__.pyf727a00fb4a388f30ab0f637b43f27345b0f6da71580788905000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.combcc.BPF.cleanup(): Ensure self.funcs items get deleted during cleanup
Since commit 115b959d86
("Fix a file descriptor leak when module is deleted (#2530)"), we
observe the following exceptions during python exit:
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 1366, in cleanup
os.close(fn.fd)
OSError: [Errno 9] Bad file descriptor
which occurs for python programs issuing a call to 'cleanup()', or using
the 'with bcc.BPF(...)' code pattern.
BPF's 'cleanup' is registered to be invoked atexit. Alas, commit
115b959d86 introduced an 'os.close(fn.fd)' call for each func loaded (to
prevent accidental FD leakage).
Problem is, that the 'self.funcs' dict entries are NOT deleted, making
subsequent calls to 'cleanup' to attempt closing the same 'fn.fd' again
and again.
It is expected from 'cleanup' to operate correctly when called
repeatedly; Therefore, it should "nullify" references to closed
resources.
Fix, by deleting the reference to each unloaded function from the
'self.func' dictionary.
Fixes: 115b959d86 ("Fix a file descriptor leak when module is deleted (#2530)")
Reported-by: Dana Rubin <drubin@metanetworks.com>
Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
2020-02-03 20:01:45 -0800f727a00fb4a388f30ab0f637b43f27345b0f6da7bcc.BPF.cleanup(): Ensure self.funcs items get deleted during cleanupeditsrc/python/bcc/__init__.py
- src/cc/export/helpers.h68789499f281c73d0ef9956dd88100c48558050e1580833707000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comdefine CC_USING_FENTRY if CONFIG_FUNCTION_TRACER is defined
Fix issue #2734.
In 4.18 and later, when CONFIG_FUNCTION_TRACER is defined, kernel Makefile adds
-DCC_USING_FENTRY. Let do the same for bpf programs.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-02-04 08:28:27 -080068789499f281c73d0ef9956dd88100c48558050edefine CC_USING_FENTRY if CONFIG_FUNCTION_TRACER is definededitsrc/cc/export/helpers.h
- snapcraft/bcc-wrappersnap/README.mdsnap/local/bcc-wrappersrc/python/setup.py.insnap/snapcraft.yamlsnapcraft/README.mdsnapcraft/Makefilesnapcraft/snapcraft.yaml685ec23ecaa9c55409a21b5cd3c919fe1206fb201581009398000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comsnap: update and cleanup snapcraft.yaml
A couple of issues fixed:
- put snapcraft.yaml in the snap directory so it is
picked up by snapcraft when run from the project root.
- use snap/local for local snapcraft assets.
- setup.py.in should not add root for sdist targets
- cleanup snap/README.md.
- re-arrange parts in snapcraft.yaml and move to python3.
Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
2020-02-06 09:16:38 -0800685ec23ecaa9c55409a21b5cd3c919fe1206fb20snap: update and cleanup snapcraft.yamldeletesnapcraft/README.mddeletesnapcraft/bcc-wrapperdeletesnapcraft/snapcraft.yamldeletesnapcraft/Makefileaddsnap/snapcraft.yamladdsnap/local/bcc-wrappereditsrc/python/setup.py.inaddsnap/README.md
- src/cc/frontends/clang/b_frontend_action.cctools/tcptop.pya4834a6cacd14f251e72695f08766a16216642b21581020611000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comprevent rewriting for array element type
Fix issue #2352.
Corresponding llvm bug: https://bugs.llvm.org/show_bug.cgi?id=41918.
If the element type is array type, the rewriter may generate code like
addr = ({ typeof(__u8 [16]) _val; __builtin_memset(&_val, 0, sizeof(_val));
bpf_probe_read(&_val, sizeof(_val), (u64)&daddr->s6_addr); _val; })
for something like
addr = daddr->s6_addr;
where s6_addr is an array.
The above code has an issue then as addr is pointing to some data
which is out of scope, which meaning compiler is free to use the space.
Let us disable such transformation until we find a good solution.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-02-06 12:23:31 -0800a4834a6cacd14f251e72695f08766a16216642b2prevent rewriting for array element typeeditsrc/cc/frontends/clang/b_frontend_action.ccedittools/tcptop.py
- src/cc/frontends/clang/b_frontend_action.ccf149ca5d774aa81d8b78cfcd5be6f5cf58cbdab71581023742000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comDo not rewrite array subscripts if invalid sourceloc range
Fix #2739.
The issue exposed an issue that to rewrite
CODE1: __u8 byte = daddr->s6_addr[4];
will segfault and to rewrite
CODE2: __u8 byte = (daddr->s6_addr)[4];
will be okay.
For CODE1, the clang did not give enough information to find the text
which contains the left bracket "[", given base "daddr->s6_addr"
and subscript "4". For CODE2, the clang is able to get the information
successfuly.
I think if we really go inside the base "daddr->s6_addr" and gets to
its member field "s6_addr", we can find the needed information
for the text range containing "[". Let us fix the segfault first
and if really desirable, we can try to enhance later for CODE1 patterns.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-02-06 13:15:42 -0800f149ca5d774aa81d8b78cfcd5be6f5cf58cbdab7Do not rewrite array subscripts if invalid sourceloc rangeeditsrc/cc/frontends/clang/b_frontend_action.cc
- tools/offwaketime.py0a7da74e2580150002131aebbe9eaa2d5e2c9b621581092194000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comFix offwaketime regression introduced by #ac00ac5
2020-02-07 08:16:34 -08000a7da74e2580150002131aebbe9eaa2d5e2c9b62Fix offwaketime regression introduced by #ac00ac5edittools/offwaketime.py
- src/cc/api/BPFTable.htests/cc/CMakeLists.txtsrc/cc/frontends/clang/b_frontend_action.ccsrc/cc/api/BPF.ccsrc/cc/bpf_module.ccsrc/cc/api/BPF.htests/cc/test_cg_storage.ccsrc/cc/export/helpers.hsrc/cc/bpf_module.htests/cc/test_sock_table.ccsrc/cc/api/BPFTable.cc6cacc41462bae12b1c38aabc7a6b85f40783da9a1581181989000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comsupport sockmap/sockhash/cgroup_local_storage maps
This patch supports sockmap, sockhash and cgroup_local_storage
maps. Two C++ APIs, attach_func and detach_func are also
added to allow to attach program to cgroups. So this makes
using C++ APIs for cgroup based networking applications
easier to integrate with bpf programs.
The unit testing is rough as it needs some work to set up
cgroups and establish TCP connections to really test the
result of map operations. But still all supported map
operations in kernel and in C++ APIs are tested syntacically.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-02-08 09:13:09 -08006cacc41462bae12b1c38aabc7a6b85f40783da9asupport sockmap/sockhash/cgroup_local_storage mapseditsrc/cc/api/BPFTable.hedittests/cc/CMakeLists.txteditsrc/cc/api/BPFTable.ccaddtests/cc/test_cg_storage.cceditsrc/cc/bpf_module.heditsrc/cc/api/BPF.cceditsrc/cc/api/BPF.heditsrc/cc/frontends/clang/b_frontend_action.cceditsrc/cc/bpf_module.cceditsrc/cc/export/helpers.haddtests/cc/test_sock_table.cc
- debian/control397ff3708f6b0d17ae0a6e2d7edf13c7d0801d831581233483000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbcc debian package is architecture-dependent
2020-02-08 23:31:23 -0800397ff3708f6b0d17ae0a6e2d7edf13c7d0801d83libbcc debian package is architecture-dependenteditdebian/control
- INSTALL.md0f92c845a7deb60e97f49425f181d7b7e9daf56b1581268355000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comcorrectly describe installation situation for Ubuntu
2020-02-09 09:12:35 -08000f92c845a7deb60e97f49425f181d7b7e9daf56bcorrectly describe installation situation for UbuntueditINSTALL.md
- snap/snapcraft.yamlc82aa514babba5d34e3794a76bf464fdd28ae4231581518920000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comsnapcraft: add missing libfl-dev dependency
Also need libfl-dev to build on other non-x86 targets
Signed-off-by: Colin Ian King <colin.king@canonical.com>
2020-02-12 06:48:40 -0800c82aa514babba5d34e3794a76bf464fdd28ae423snapcraft: add missing libfl-dev dependencyeditsnap/snapcraft.yaml
- libbpf-tools/bin/bpftool4281c62f9f04962bed05a326f68102b6ee8a54641581541170000https://buildbot.iovisor.org/jenkins/user/andriinandriinandriin@fb.comlibbpf tools: check in bpftool for use by libbpf-based tool build
Check in bpftool binary to be used for BPF skeleton generation for
libbpf-based tools.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-02-12 12:59:30 -08004281c62f9f04962bed05a326f68102b6ee8a5464libbpf tools: check in bpftool for use by libbpf-based tool buildaddlibbpf-tools/bin/bpftool
- libbpf-tools/vmlinux.hlibbpf-tools/vmlinux_505.h7fcb335b6c068dded2af10918753ead35ad875321581541254000https://buildbot.iovisor.org/jenkins/user/andriinandriinandriin@fb.comtools: add vmlinux.h header with all kernel types
Check in vmlinux.h generated from Linux 5.5 version with default config. This
is used from libbpf-based tools.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-02-12 13:00:54 -08007fcb335b6c068dded2af10918753ead35ad87532tools: add vmlinux.h header with all kernel typesaddlibbpf-tools/vmlinux.haddlibbpf-tools/vmlinux_505.h
- CMakeLists.txt2d099cd8c5cb1598d6e911c0b389132ebc7c101b1581554521000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comAllow specifying clang base directory
2020-02-12 16:42:01 -08002d099cd8c5cb1598d6e911c0b389132ebc7c101bAllow specifying clang base directoryeditCMakeLists.txt
- libbpf-tools/runqslower.clibbpf-tools/runqslower_example.txtlibbpf-tools/runqslower.bpf.clibbpf-tools/README.mdman/man8/runqslower.8libbpf-tools/runqslower.hlibbpf-tools/.gitignorelibbpf-tools/Makefilee1496e15a749fa700315f759dfca4ac79f3f64281581570874000https://buildbot.iovisor.org/jenkins/user/andriinandriinandriin@fb.comtools: add libbpf-based tools to BCC w/ runqslower as first converted tool
Add runqslower as a first tool converted from BCC to libbpf, utilizing BPF
CO-RE (Compile Once - Run Everywhere) approach and BPF skeleton for
interfacing with BPF programs. Current set up is Makefile based and is set up
in such a way as to enable easy addition for more tools, based on a simple and
convenient naming pattern. General build infrastructure takes case of BPF
skeleton generation, tracking dependencies, clean up, etc.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-02-12 21:14:34 -0800e1496e15a749fa700315f759dfca4ac79f3f6428tools: add libbpf-based tools to BCC w/ runqslower as first converted tooladdlibbpf-tools/README.mdaddlibbpf-tools/runqslower_example.txteditman/man8/runqslower.8addlibbpf-tools/runqslower.caddlibbpf-tools/runqslower.haddlibbpf-tools/runqslower.bpf.caddlibbpf-tools/.gitignoreaddlibbpf-tools/Makefile
- tools/tcpconnlat.pya28ad059edf6f74acc124fde4b4934a2fc410a351581892852000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comfix pid filter bug
1. Wirte a simple go, just print pid and get some website.
func main() {
pid := os.Getpid()
fmt.Println(pid)
response, err := http.Get("http://www.baidu.com")
....
}
./main
3581
2. But when run `tcpconnlat`, we just go tid 3585, (not pid 3581)
#./tcpconnlat
PID COMM IP SADDR DADDR DPORT LAT(ms)
3585 main 4 10.0.2.15 180.101.49.11 80 60.68
3. So run `./tcpconnlat -p 3581` not work
I have tested this situation under kernel 3.10 and 5.0.9.
2020-02-16 14:40:52 -0800a28ad059edf6f74acc124fde4b4934a2fc410a35fix pid filter bugedittools/tcpconnlat.py
- tools/stackcount.pytools/stackcount_example.txt9b6a0e357c30b52e115f803bb6babb3ffc4fdabf1582069705000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools/stackcount: Fix address resolution for user-space stack
This patch fixes issue #2748. The bug was that address-to-symbol resolution
didn't work for user-space stacks without the `-P` (per-pid) flag when tracing
single, isolated processes. The current documentation of the `-P` option
indicates that it's used to "display stacks separately for each process",
and this doesn't match with the intended usage.
This patch has two parts:
- Fix `tools/stackcount.py` to explicitly set perpid to True if `-p <pid>`
is used
- Remove the `-P` option from the example of tracing single, isolated process
in `tools/stackcount_example.txt`, since the usage of the option can
be confusing (and unnecessary after the current change)
2020-02-18 15:48:25 -08009b6a0e357c30b52e115f803bb6babb3ffc4fdabftools/stackcount: Fix address resolution for user-space stackedittools/stackcount.pyedittools/stackcount_example.txt
- examples/tracing/dddos.py1332e68676fe0f1365dccd5ebffc05259b67abc11582084033000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comUpdate dddos.py
Fix a few more typos
2020-02-18 19:47:13 -08001332e68676fe0f1365dccd5ebffc05259b67abc1Update dddos.pyeditexamples/tracing/dddos.py
- tests/python/test_tools_smoke.pytools/bindsnoop_example.txttools/bindsnoop.pyman/man8/bindsnoop.8README.md8dd4b5a521602d86a9331b5c6c6bdd53a8b4ed721582084151000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.combindsnoop BCC tool (#2749)
bindsnoop BCC utility
bindsnoop tool traces the kernel function performing socket binding and
print socket options set before the system call invocation that might
impact bind behavior and bound interface
2020-02-18 19:49:11 -08008dd4b5a521602d86a9331b5c6c6bdd53a8b4ed72bindsnoop BCC tool (#2749)edittests/python/test_tools_smoke.pyaddman/man8/bindsnoop.8addtools/bindsnoop_example.txtaddtools/bindsnoop.pyeditREADME.md
- src/cc/libbpf51be481a7957b8d84bd02487f66f819f79e94f4a1582087366000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comsync to latest libbpf
sync to latest libbpf (libbpf release v0.0.7) to
prepare bcc release.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-02-18 20:42:46 -080051be481a7957b8d84bd02487f66f819f79e94f4async to latest libbpfeditsrc/cc/libbpf
- tools/profile.py29aa61985c98456177d52a5f00cba092b572e7781582128592000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comtools/profile: fix kernel delimiter when folding (#2758)
retain delimiter with folding enabled
2020-02-19 08:09:52 -080029aa61985c98456177d52a5f00cba092b572e778tools/profile: fix kernel delimiter when folding (#2758)edittools/profile.py
- tools/execsnoop.pyb26b429cf38b0e1afe915ceee0a1f0172e803ea41582132188000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: fix confusion between execsnoop and opensnoop
The execsnoop documentation mispelled 'execsnoop' as 'opensnoop'.
Bug introduced by https://github.com/iovisor/bcc/pull/2651
2020-02-19 09:09:48 -0800b26b429cf38b0e1afe915ceee0a1f0172e803ea4tools: fix confusion between execsnoop and opensnoopedittools/execsnoop.py
- debian/changelog942227484d3207f6a42103674001ef01fb5335a01582174809000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comdebian changelog for v0.13.0 tag
* Support for kernel up to 5.5
* bindsnoop tool to track tcp/udp bind information
* added compile-once run-everywhere based libbpf-tools, currently
only runqslower is implemented.
* new map support: sockhash, sockmap, sk_storage, cgroup_storage
* enable to run github actions on the diff
* cgroupmap based cgroup filtering for opensnoop, execsnoop and bindsnoop.
* lots of bug fixes.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-02-19 21:00:09 -0800942227484d3207f6a42103674001ef01fb5335a0debian changelog for v0.13.0 tageditdebian/changelog
- docs/filtering_by_cgroups.mdtools/tcpaccept.pytools/tcptracer.pytools/tcpconnect.pytools/tcpaccept_example.txttools/tcpconnect_example.txttools/tcptracer_example.txt1ce868fbb4b4cd45f9d3d043c6d697f45fc6268d1582247124000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: add option --cgroupmap to tcp tools
List of tcp tools updated: tcpaccept, tcpconnect, tcptracer
2020-02-20 17:05:24 -08001ce868fbb4b4cd45f9d3d043c6d697f45fc6268dtools: add option --cgroupmap to tcp toolsedittools/tcpaccept_example.txtedittools/tcpconnect.pyedittools/tcpaccept.pyedittools/tcpconnect_example.txteditdocs/filtering_by_cgroups.mdedittools/tcptracer.pyedittools/tcptracer_example.txt
- man/man8/tcpaccept.8man/man8/tcpconnect.8man/man8/execsnoop.8man/man8/tcptracer.8man/man8/opensnoop.85e3f9e4915fab83effccf3d20d3fbee715d96f6c1582247124000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comman pages: add documentation about --cgroupmap
2020-02-20 17:05:24 -08005e3f9e4915fab83effccf3d20d3fbee715d96f6cman pages: add documentation about --cgroupmapeditman/man8/opensnoop.8editman/man8/execsnoop.8editman/man8/tcptracer.8editman/man8/tcpaccept.8editman/man8/tcpconnect.8
- src/cc/api/BPF.ccsrc/cc/libbpf.csrc/cc/api/BPF.hsrc/cc/libbpf.h5681ea9edb5763c6199c2e2e7956bdfa7c13ea361582247758000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comc++ api: add wrapper for raw tracepoints
2020-02-20 17:15:58 -08005681ea9edb5763c6199c2e2e7956bdfa7c13ea36c++ api: add wrapper for raw tracepointseditsrc/cc/libbpf.ceditsrc/cc/api/BPF.cceditsrc/cc/api/BPF.heditsrc/cc/libbpf.h
- examples/cpp/RandomRead.cc2a2e7290b60fdc420baa93954c20af8338fa6fae1582247758000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comcpp examples: use a raw tracepoint for RandomRead
2020-02-20 17:15:58 -08002a2e7290b60fdc420baa93954c20af8338fa6faecpp examples: use a raw tracepoint for RandomReadeditexamples/cpp/RandomRead.cc
- libbpf-tools/README.md7ad17638acd9c1d82264451c9b0800ecf5ce4f591582265941000https://buildbot.iovisor.org/jenkins/user/andriinandriinandriin@fb.comlibbpf-tools: add links to BPF CO-RE posts
Add links to BPF CO-RE blog posts, explainint what it is, how to use it, and
giving practical recommendations on how to convert BCC BPF program to
libbpf-based one.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-02-20 22:19:01 -08007ad17638acd9c1d82264451c9b0800ecf5ce4f59libbpf-tools: add links to BPF CO-RE postseditlibbpf-tools/README.md
- man/man8/execsnoop.8tools/execsnoop.pytools/execsnoop_example.txtc949f613315f19fce1fe5e6dacb1f0e5759c91c91582302172000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: execsnoop add -U and -u flags
Add flags to display UID and filter by UID
2020-02-21 08:22:52 -0800c949f613315f19fce1fe5e6dacb1f0e5759c91c9tools: execsnoop add -U and -u flagsedittools/execsnoop.pyedittools/execsnoop_example.txteditman/man8/execsnoop.8
- tools/oomkill.py9edbae394f1827a2f5d549795848dc892c6531bf1582609928000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools/oomkill: output PID instead of thread ID (user's view)
2020-02-24 21:52:08 -08009edbae394f1827a2f5d549795848dc892c6531bftools/oomkill: output PID instead of thread ID (user's view)edittools/oomkill.py
- examples/networking/http_filter/http-parse-complete.py6f3c33b01ce72a44c89a6dcccd3f1cbd99fe19491582610424000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comFix the python part of the http-parse-complete example
The example wasn't working on my machine, just like in issue #2169
2020-02-24 22:00:24 -08006f3c33b01ce72a44c89a6dcccd3f1cbd99fe1949Fix the python part of the http-parse-complete exampleeditexamples/networking/http_filter/http-parse-complete.py
- docs/reference_guide.md08de253fbbc2603d59c19618a3e9f18f5bff7bff1582674495000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comFix a table of contents of maps
Signed-off-by: Masanori Misono <m.misono760@gmail.com>
2020-02-25 15:48:15 -080008de253fbbc2603d59c19618a3e9f18f5bff7bffFix a table of contents of mapseditdocs/reference_guide.md
- tests/cc/CMakeLists.txt18da40cd186296d277e193fa92dec1791a888b8c1582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comFix bpf linking if specified via LIBBPF_LIBRARIES variable
We need to use LIBBPF_LIBRARIES variable instead of just using bpf
for libbpf linking, so it user specified library gets linked in.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -080018da40cd186296d277e193fa92dec1791a888b8cFix bpf linking if specified via LIBBPF_LIBRARIES variableedittests/cc/CMakeLists.txt
- src/cc/frontends/clang/b_frontend_action.ccsrc/cc/bpf_module.ccsrc/cc/libbpf.csrc/cc/CMakeLists.txtsrc/cc/bcc_btf.ccsrc/cc/bcc_libbpf_inc.h1e7862fdfd8b428e6b2e3ea23f63a1469c3fabf31582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comUnite libbpf includes
Currently we include headers from local libbpf subpackage,
which does not work if user specify LIBBPF_INCLUDE_DIR.
Adding HAVE_EXTERNAL_LIBBPF macro, that gets defined when
user specifies libbpf header path. This macro is checked
in bcc_libbpf_inc.h and proper files are included.
Using bcc_libbpf_inc.h in place of libbpf includes.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -08001e7862fdfd8b428e6b2e3ea23f63a1469c3fabf3Unite libbpf includeseditsrc/cc/bcc_btf.cceditsrc/cc/bpf_module.ccaddsrc/cc/bcc_libbpf_inc.heditsrc/cc/libbpf.ceditsrc/cc/CMakeLists.txteditsrc/cc/frontends/clang/b_frontend_action.cc
- src/cc/bpf_module.ccsrc/cc/libbpf.c550706a220da1636fafd322f0366cfde2a188d161582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comDo not initialize kern_version for TRACING/EXT programs
The TRACING/EXT programs use attach_btf_id and attach_prog_fd
fields from struct bpf_load_program_attr.
The attach_prog_fd field shares space with kern_version,
so by setting kern_version unconditionally we also set
attach_prog_fd to bogus value and kernel fails the load
because it tries to look it up.
Setting kern_version only for programs other than TRACING/EXT
type.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -0800550706a220da1636fafd322f0366cfde2a188d16Do not initialize kern_version for TRACING/EXT programseditsrc/cc/libbpf.ceditsrc/cc/bpf_module.cc
- docs/reference_guide.mdsrc/cc/libbpf.csrc/python/bcc/__init__.pysrc/cc/libbpf.hsrc/cc/export/helpers.h572478b2083651f25c4e278f8c34ff3d16e3be6a1582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comIntroduce {attach|detach}_kfunc API
Kernel added new probe called trampoline allowing to probe
almost any kernel function when BTF info is available in
the system.
Adding the interface to define trampoline function for given
kernel function via BPF_PROG macro, like:
KFUNC_PROBE(do_sys_open, int dfd, const char *filename, int flags, int mode)
{
...
}
which defines trampoline function with the 'kfunc__do_sys_open'
name, that instruments do_sys_open kernel function before the
function is executed.
or:
KRETFUNC_PROBE(do_sys_open, int dfd, const char *filename, int flags, int mode, int ret)
{
...
}
which defines trampoline function with the 'kfunc__do_sys_open'
name, that instruments do_sys_open kernel function after the
function is executed.
The main benefit is really lower overhead for trampolines (please
see following commit for klockstat.py with perf comparison).
Another benefit is the ability of kretfunc probe to access
function arguments, so some tools might need only one program
instead of entry/exit ones (please see following commit for
opensnoop.py changes).
Currently the interface does not allow to define function
of different name than:
kfunc__<function_name> or kretfunc__<function_name>
which is sufficient by now, and can be easily changed in future
if needed.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -0800572478b2083651f25c4e278f8c34ff3d16e3be6aIntroduce {attach|detach}_kfunc APIeditsrc/cc/export/helpers.heditsrc/python/bcc/__init__.pyeditdocs/reference_guide.mdeditsrc/cc/libbpf.ceditsrc/cc/libbpf.h
- src/python/bcc/__init__.pysrc/cc/libbpf.hsrc/cc/libbpf.c1ad2656a1d9ca1e451ebad5af1330863c66a40351582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comAdd support_kfunc function to BPF object
Adding support_kfunc function to BPF object to return
state of kfunc trampolines support.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -08001ad2656a1d9ca1e451ebad5af1330863c66a4035Add support_kfunc function to BPF objecteditsrc/python/bcc/__init__.pyeditsrc/cc/libbpf.heditsrc/cc/libbpf.c
- tools/opensnoop.pyc347fe6c9f75d6740cf45f80312009daba275f761582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comSupport kfunc in opensnoop.py
Adding kfunc return trampoline probe if available instead of
kprobe/kretprobe probes.
The return trampoline has access to function entry arguments,
so we are good with just single eBPF program.
The kfunc trampolines are also faster - less intrusive.
Below are stats for compiling linux kernel while running
opensnoop.py on the background for kprobes and kfuncs.
Without opensnoop.py:
Performance counter stats for 'system wide':
849,741,782,765 cycles:k
162.235646336 seconds time elapsed
With opensnoop.py using kprobes:
Performance counter stats for 'system wide':
941,615,199,769 cycles:k
164.355032879 seconds time elapsed
With opensnoop.py using trampolines:
Performance counter stats for 'system wide':
913,437,005,488 cycles:k
163.742914795 seconds time elapsed
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -0800c347fe6c9f75d6740cf45f80312009daba275f76Support kfunc in opensnoop.pyedittools/opensnoop.py
- tools/klockstat.pyda7cac733c931f06801cc3ce118140892fcb80661582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comSupport kfunc in klockstat.py
Adding kfunc return trampoline probe if available instead of
kprobe/kretprobe probes.
The kfunc trampolines are faster - less intrusive. The benchmark
without klockstat.py script on background:
$ perf bench sched messaging -l 50000
# Running 'sched/messaging' benchmark:
# 20 sender and receiver processes per group
# 10 groups == 400 processes run
Total time: 18.571 [sec]
With kprobe tracing:
$ perf bench sched messaging -l 50000
# Running 'sched/messaging' benchmark:
# 20 sender and receiver processes per group
# 10 groups == 400 processes run
Total time: 183.395 [sec]
With kfunc tracing:
$ perf bench sched messaging -l 50000
# Running 'sched/messaging' benchmark:
# 20 sender and receiver processes per group
# 10 groups == 400 processes run
Total time: 39.773 [sec]
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -0800da7cac733c931f06801cc3ce118140892fcb8066Support kfunc in klockstat.pyedittools/klockstat.py
- tools/vfsstat.py2fa54c0bd388898fdda58f30dcfe5a68d6715efc1582782477000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comSupport kfunc in vfsstat.py
Adding kfunc return trampoline probe if available instead of
kprobe/kretprobe probes.
The kfunc trampolines are faster - less intrusive.
Below are stats for running perf bench sched pipe benchamark while
running vfsstat.py on the background for kprobes and kfuncs.
With kprobes:
Performance counter stats for './perf bench sched pipe -l 5000000' (3 runs):
112,520,853,574 cycles:k
48.674 +- 0.672 seconds time elapsed ( +- 1.38% )
With kfuncs:
Performance counter stats for './perf bench sched pipe -l 5000000' (3 runs):
106,304,165,424 cycles:k
46.820 +- 0.197 seconds time elapsed ( +- 0.42% )
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-02-26 21:47:57 -08002fa54c0bd388898fdda58f30dcfe5a68d6715efcSupport kfunc in vfsstat.pyedittools/vfsstat.py
- src/cc/bcc_exception.h6de96c71f11ace5091651c6cdf645a2d3426214b1582783313000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comUpdate StatusTuple to use enum Code
2020-02-26 22:01:53 -08006de96c71f11ace5091651c6cdf645a2d3426214bUpdate StatusTuple to use enum Codeeditsrc/cc/bcc_exception.h
- INSTALL.md440016f70b24e2913860e21eb2c2a6bbca970f0d1582784233000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comdoc: add python3 doc to "Ubuntu - Source" section in INSTALL.md
2020-02-26 22:17:13 -0800440016f70b24e2913860e21eb2c2a6bbca970f0ddoc: add python3 doc to "Ubuntu - Source" section in INSTALL.mdeditINSTALL.md
- src/python/bcc/usdt.pyc46c7b3d4203adbbc964c25451b918c0df5d94ff1583172362000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comusdt.py: improve error messags for enable_probe()
2020-03-02 10:06:02 -0800c46c7b3d4203adbbc964c25451b918c0df5d94ffusdt.py: improve error messags for enable_probe()editsrc/python/bcc/usdt.py
- libbpf-tools/bin/bpftool17ff39223a4dd2ff28f63239cb82f785e47ba45c1583277540000https://buildbot.iovisor.org/jenkins/user/andriinandriinandriin@fb.comlibbpf-tools: update bpftool
Newer bpftool generates vmlinux.h with header guard `#define`, which plays
nicely with bpf_tracing.h header and PT_REGS_PARM macros.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-03 15:19:00 -080017ff39223a4dd2ff28f63239cb82f785e47ba45clibbpf-tools: update bpftooleditlibbpf-tools/bin/bpftool
- libbpf-tools/drsnoop.clibbpf-tools/drsnoop.bpf.csnap/snapcraft.yamllibbpf-tools/drsnoop_example.txtlibbpf-tools/trace_helpers.ctools/drsnoop.pyman/man8/drsnoop.8libbpf-tools/trace_helpers.hlibbpf-tools/drsnoop.hman/man8/compactsnoop.8libbpf-tools/Makefilec42197080dda3f565280b918b9bd5223f5e509d61583353326000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: covert BCC drsnoop to BPF CO-RE version
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
2020-03-04 12:22:06 -0800c42197080dda3f565280b918b9bd5223f5e509d6libbpf-tools: covert BCC drsnoop to BPF CO-RE versionaddlibbpf-tools/drsnoop.haddlibbpf-tools/drsnoop_example.txtaddlibbpf-tools/trace_helpers.heditman/man8/compactsnoop.8edittools/drsnoop.pyeditlibbpf-tools/Makefileaddlibbpf-tools/drsnoop.bpf.caddlibbpf-tools/drsnoop.caddlibbpf-tools/trace_helpers.ceditman/man8/drsnoop.8editsnap/snapcraft.yaml
- src/python/bcc/usdt.pyaeea0e9fce7e868f27cac45f5d6ab4f67c383c621583521117000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comusdt.py: print errors to stderr in enable_probe_or_bail()
2020-03-06 10:58:37 -0800aeea0e9fce7e868f27cac45f5d6ab4f67c383c62usdt.py: print errors to stderr in enable_probe_or_bail()editsrc/python/bcc/usdt.py
- src/cc/usdt/usdt_args.cctests/cc/test_usdt_args.ccsrc/cc/usdt.h5011f992b3167c162b5a0ad57fd3fa23c9ea76b31583625697000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comusdt: fix parsing sp register in arguments on AArch64
One of the USDT probes for OpenJDK on AArch64 has an argument as an
offset from the stack pointer register like "8@[sp, 112]". This causes
the argument parser to fail:
Parse error:
8@x22 8@x20 8@x23 8@x0 8@x26 8@x27 8@[sp, 112] 8@[sp, 120]
------------------------------------------^
The error message then repeats forever.
Changed ArgumentParser_aarch64::parse_register so it accepts either
"xNN" or "sp" and outputs the register name rather than the register
number. The stack pointer is in a separate field `sp` in `struct
pt_regs` rather than in the `regs[]` array [1].
Note that the parser currently accepts "x31" and converts that into a
reference to `regs[31]' but that array only has 31 elements. Made x31 an
alias for `sp` to avoid undefined behaviour from reading past the end of
the array.
[1]: https://elixir.bootlin.com/linux/latest/source/arch/arm64/include/asm/ptrace.h#L160
Change-Id: I88b6ff741914b5d06ad5798a55bd21ea03f69825
Signed-off-by: Nick Gasson <nick.gasson@arm.com>
2020-03-07 16:01:37 -08005011f992b3167c162b5a0ad57fd3fa23c9ea76b3usdt: fix parsing sp register in arguments on AArch64edittests/cc/test_usdt_args.cceditsrc/cc/usdt.heditsrc/cc/usdt/usdt_args.cc
- src/cc/api/BPFTable.hsrc/cc/api/BPF.ccsrc/cc/bpf_module_rw_engine.ccsrc/cc/frontends/b/type_check.ccsrc/cc/frontends/b/printer.ccsrc/cc/frontends/b/codegen_llvm.ccsrc/cc/api/BPFTable.cce508059878525159ccff8c3672d36ecb03b27dac1583639107000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comReplace StatusTuple(0) with StatusTuple::OK()
With the following shell command:
$ find src -type f -regex '.*\.\(h\|cc\)' -exec sed -i 's/StatusTuple(0)/StatusTuple::OK()/' {} \;
2020-03-07 19:45:07 -0800e508059878525159ccff8c3672d36ecb03b27dacReplace StatusTuple(0) with StatusTuple::OK()editsrc/cc/api/BPF.cceditsrc/cc/frontends/b/printer.cceditsrc/cc/frontends/b/codegen_llvm.cceditsrc/cc/bpf_module_rw_engine.cceditsrc/cc/api/BPFTable.cceditsrc/cc/frontends/b/type_check.cceditsrc/cc/api/BPFTable.h
- src/python/bcc/table.py98c18b640117b10f923c8697be8bfff8ad39834b1583639793000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comprint error messages to stderr and exit(1) instead of exit(0) for fatal errors
2020-03-07 19:56:33 -080098c18b640117b10f923c8697be8bfff8ad39834bprint error messages to stderr and exit(1) instead of exit(0) for fatal errorseditsrc/python/bcc/table.py
- .github/workflows/bcc-test.ymlDockerfile.ubuntucf20a499655583a985eb959f98fae9c2e7ecf1891583646711000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comGitHub Actions: optionally publish container image
This is optional: this GitHub Action will only attempt to publish the
container image if the GitHub repository has been configured with GitHub
secrets (e.g. https://github.com/iovisor/bcc/settings/secrets).
The GitHub secrets can be configured as follows:
- DOCKER_PUBLISH = 1
- DOCKER_IMAGE = docker.io/myorg/bcc
- DOCKER_USERNAME = username
- DOCKER_PASSWORD = password
This is intended to make it easy for anyone to fork iovisor/bcc on
GitHub and publish custom container images with bcc.
2020-03-07 21:51:51 -0800cf20a499655583a985eb959f98fae9c2e7ecf189GitHub Actions: optionally publish container imageeditDockerfile.ubuntuedit.github/workflows/bcc-test.yml
- libbpf-tools/trace_helpers.clibbpf-tools/trace_helpers.hlibbpf-tools/Makefilelibbpf-tools/.gitignoreb7541d0b9497e5bca4de28d894d18cc8578ccdc41583646738000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: optimize ksyms cache
Re-implement internals of ksyms cache to minimize memory overhead and
allocations. Addr is also changed to be unsigned long.
fscanf() can be further optimized into manual parsing, but it's low enough
overhead right now that I felt like readibility is more important.
Benchmarking ksyms loading/parsing parts:
BEFORE:
$ /usr/bin/time ./test
0.03user 0.04system 0:00.08elapsed 98%CPU (0avgtext+0avgdata 6968maxresident)k
0inputs+0outputs (0major+1512minor)pagefaults 0swaps
AFTER:
$ /usr/bin/time ./test
0.02user 0.03system 0:00.06elapsed 100%CPU (0avgtext+0avgdata 9508maxresident)k
0inputs+0outputs (0major+2106minor)pagefaults 0swaps
RSS goes down from 9.5MB to <7MB, while CPU time went up about 20ms.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-07 21:52:18 -0800b7541d0b9497e5bca4de28d894d18cc8578ccdc4libbpf-tools: optimize ksyms cacheeditlibbpf-tools/trace_helpers.heditlibbpf-tools/Makefileeditlibbpf-tools/.gitignoreeditlibbpf-tools/trace_helpers.c
- src/python/bcc/usdt.pysrc/python/bcc/libbcc.pytests/python/test_usdt3.py37cd183a71f19c25c08a2a93d271450b392bdca51583731633000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.compython binding: allow fully-specified probe names for enable_probe()
2020-03-08 22:27:13 -070037cd183a71f19c25c08a2a93d271450b392bdca5python binding: allow fully-specified probe names for enable_probe()edittests/python/test_usdt3.pyeditsrc/python/bcc/usdt.pyeditsrc/python/bcc/libbcc.py
- tools/trace.pysrc/cc/usdt/usdt.ccsrc/python/bcc/usdt.pysrc/cc/bcc_usdt.hsrc/python/bcc/libbcc.py21625167988a5ed1e07046e8048b4de59e9fd0231583731633000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtrace.py: support an optional provider name for the probe spec
2020-03-08 22:27:13 -070021625167988a5ed1e07046e8048b4de59e9fd023trace.py: support an optional provider name for the probe speceditsrc/python/bcc/usdt.pyeditsrc/cc/usdt/usdt.ccedittools/trace.pyeditsrc/cc/bcc_usdt.heditsrc/python/bcc/libbcc.py
- tools/softirqs.py9465f8cf2a19d28dcc8bce5845b5e8017ee9feb81583734192000https://buildbot.iovisor.org/jenkins/user/edwardwuedwardwuedwardwu@realtek.comsoftirqs: Combined CPU as part of the key is necessary to avoid amiss value.
In the environment of massive software interrupts.
<idle>-0 [003] ..s1 106.421020: softirq_entry: vec=6 [action=TASKLET]
<idle>-0 [000] ..s1 106.421063: softirq_entry: vec=3 [action=NET_RX]
<idle>-0 [003] ..s1 106.421083: softirq_exit: vec=6 [action=TASKLET]
Follow the above ftrace logs, we know the correct vec-6 start timestamp is replaced with incorrect vec-3.
Because PID is idle-0. It will produce the wrong result after calculating delta.
2020-03-09 14:09:52 +08009465f8cf2a19d28dcc8bce5845b5e8017ee9feb8softirqs: Combined CPU as part of the key is necessary to avoid amiss value.edittools/softirqs.py
- tools/capable.pytools/capable_example.txtman/man8/capable.815e998db6ea8617ae8798a09b9d8115ce5e954731583734946000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: add option --cgroupmap to capable.py
Documentation (man page and example text) updated.
2020-03-08 23:22:26 -070015e998db6ea8617ae8798a09b9d8115ce5e95473tools: add option --cgroupmap to capable.pyeditman/man8/capable.8edittools/capable.pyedittools/capable_example.txt
- tools/capable.pytools/capable_example.txtman/man8/capable.89d7feeed87c5e2977e0e996cc097dcd9d3001c0d1583734946000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: add option --unique to capable.py
Some processes can do a lot of security capability checks, generating a
lot of ouput. In this case, the --unique option is useful to only print
once the same set of capability, pid (or cgroup if --cgroupmap is used)
and kernel/user stacks (if -K or -U are used).
# ./capable.py -K -U --unique
Documentation (man page and example text) updated.
2020-03-08 23:22:26 -07009d7feeed87c5e2977e0e996cc097dcd9d3001c0dtools: add option --unique to capable.pyeditman/man8/capable.8edittools/capable.pyedittools/capable_example.txt
- Dockerfile.ubuntuc9cfb52f3bc39fd78f40e3c3de5e066239ce19041583735919000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comReduce container image size with multi-stage builds
Before this patch, Dockerfile.ubuntu was generating an oversized image.
Uncompressed size Compressed size
Before this patch: 1.3GB 390MB
After this patch: 250MB 110MB
2020-03-08 23:38:39 -0700c9cfb52f3bc39fd78f40e3c3de5e066239ce1904Reduce container image size with multi-stage buildseditDockerfile.ubuntu
- libbpf-tools/opensnoop.bpf.clibbpf-tools/opensnoop.clibbpf-tools/opensnoop.hlibbpf-tools/Makefile5e123df1dd33cdff5798560e4f0390c69cdba00f1583772382000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comlibbpf-tools: add CO-RE opensnoop (#2778)
* libbpf-tools: add CO-RE opensnoop
* libbpf-tools/opensnoop: feedback
2020-03-09 09:46:22 -07005e123df1dd33cdff5798560e4f0390c69cdba00flibbpf-tools: add CO-RE opensnoop (#2778)addlibbpf-tools/opensnoop.haddlibbpf-tools/opensnoop.bpf.caddlibbpf-tools/opensnoop.ceditlibbpf-tools/Makefile
- man/man8/tcptop.8tools/tcptop_example.txttools/tcptop.py7d62656805cca60ff9d6f5e9b8b5b8d096cf226a1583783734000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: add option --cgroupmap to tcptop
2020-03-09 12:55:34 -07007d62656805cca60ff9d6f5e9b8b5b8d096cf226atools: add option --cgroupmap to tcptopedittools/tcptop_example.txteditman/man8/tcptop.8edittools/tcptop.py
- libbpf-tools/vmlinux_505.h8b6a7db9c8eeb5c513a162c90a7dd8f0bd7620dd1583793216000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: update vmlinux.h with BPF helper flags generated from UAPI
Update vmlinux.h to a version generated from same v5.5 tag and default config
with cherry-picked 1aae4bdd7879 ("bpf: Switch BPF UAPI #define constants used
from BPF program side to enums") on top of it. This adds lots of BPF helper
flags often useful from BPF program side.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-09 15:33:36 -07008b6a7db9c8eeb5c513a162c90a7dd8f0bd7620ddlibbpf-tools: update vmlinux.h with BPF helper flags generated from UAPIeditlibbpf-tools/vmlinux_505.h
- src/cc/libbpf77d60b19f9d608d1039c3297f3e7fcf9548c879e1583994623000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf: sync to latest version
Sync libbpf to latest revision. It brings latest BPF headers, among other
things.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-11 23:30:23 -070077d60b19f9d608d1039c3297f3e7fcf9548c879elibbpf: sync to latest versioneditsrc/cc/libbpf
- libbpf-tools/opensnoop.bpf.clibbpf-tools/runqslower.bpf.clibbpf-tools/opensnoop.clibbpf-tools/drsnoop.bpf.clibbpf-tools/.gitignore454b138e6b75a47d4070a4f99c8f2372b383f71e1583995665000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: small clean ups across all tools
Remove BPF_F_CURRENT_CPU definitions, which are now provided by vmlinux.h
after 1aae4bdd7879 ("bpf: Switch BPF UAPI #define constants used from BPF
program side to enums") commit in kernel.
Fix potential uninitialized read warning in opensnoop.
Also add opensnoop to .gitignore.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-11 23:47:45 -0700454b138e6b75a47d4070a4f99c8f2372b383f71elibbpf-tools: small clean ups across all toolseditlibbpf-tools/runqslower.bpf.ceditlibbpf-tools/opensnoop.bpf.ceditlibbpf-tools/drsnoop.bpf.ceditlibbpf-tools/.gitignoreeditlibbpf-tools/opensnoop.c
- libbpf-tools/Makefile2b5fcc6ec332f8067dab50da833ee870fd6905791584028908000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: determine target host architecture
BPF code is compiled with -target bpf, but for PT_REGS_PARM macro (and by
induction for BPF_KPROBE/BPF_KRETPROBE macros as well), it's important to know
what's the target host original architecture was, to use correct definition of
struct pt_regs. Determine that based on output of `uname -m` (taking into
account that both x86_64 and x86 are defined as x86 internally for kernel).
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-12 09:01:48 -07002b5fcc6ec332f8067dab50da833ee870fd690579libbpf-tools: determine target host architectureeditlibbpf-tools/Makefile
- tools/tcpstates.pyd0ec8a27db740304d46d898d1a930bfcb6e096271584144164000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comBackport tcpstates to kernels < 4.15
The tracepoint inet_sock_set_state only exists in kernels 4.15.
Backported the bpf tracepoint to use kprobes on older kernels.
2020-03-13 17:02:44 -0700d0ec8a27db740304d46d898d1a930bfcb6e09627Backport tcpstates to kernels < 4.15edittools/tcpstates.py
- libbpf-tools/vmlinux_505.hlibbpf-tools/kernel.configcd43be4c6a52540a8e272ed3dcea48211c1980731584144420000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: adjust Kconfig and re-build vmlinux.h
Default v5.5 kernel config doesn't have most of BPF-related functionality
enabled, which leads to vmlinux.h not containing a lot of useful constants.
This patch contains re-generated vmlinux.h from kernel built with default
config plus minimal changes to enable most (all?) BPF-relevant parts of
kernel. Here's a list of added options:
CONFIG_BPF_EVENTS=y
CONFIG_BPFILTER_UMH=m
CONFIG_BPFILTER=y
CONFIG_BPF_JIT=y
CONFIG_BPF_KPROBE_OVERRIDE=y
CONFIG_BPF_STREAM_PARSER=y
CONFIG_BPF_SYSCALL=y
CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_CC_HAS_SANCOV_TRACE_PC=y
CONFIG_CGROUP_BPF=y
CONFIG_GCC_VERSION=70300
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SEG6_BPF=y
CONFIG_IPV6_SEG6_LWTUNNEL=y
CONFIG_LIBCRC32C=y
CONFIG_LWTUNNEL_BPF=y
CONFIG_LWTUNNEL=y
CONFIG_NET_ACT_BPF=y
CONFIG_NET_CLS_BPF=y
CONFIG_NETFILTER_ADVANCED=y
CONFIG_NETFILTER_XT_MATCH_BPF=y
CONFIG_NET_SOCK_MSG=y
CONFIG_NF_CT_PROTO_DCCP=y
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CT_PROTO_UDPLITE=y
CONFIG_SOCK_CGROUP_DATA=y
CONFIG_STREAM_PARSER=y
CONFIG_XDP_SOCKETS_DIAG=y
CONFIG_XDP_SOCKETS=y
To make this vmlinux.h generation process easier for future adjustments (e.g.,
if some of the tools would need types that default config compiles out), check
in used Kconfig along the vmlinux.h itself.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-13 17:07:00 -0700cd43be4c6a52540a8e272ed3dcea48211c198073libbpf-tools: adjust Kconfig and re-build vmlinux.heditlibbpf-tools/vmlinux_505.haddlibbpf-tools/kernel.config
- src/cc/frontends/clang/tp_frontend_action.ccsrc/cc/common.ccsrc/cc/common.h7fd2fa68b52e0f38dd4915bf786d67445941eedd1584288670000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comFactor out ebpf::parse_tracepoint function
And moving it to common.cc in order to be able to make
automated tests for it. Following patches are adding
automated test for this function and it seems too much
to link in all the clang/llvm stuff to the test binary
just for single function test.
Adding ebpf::parse_tracepoint that takes istream of the
tracepoint format data and returns tracepoint struct
as std::string.
No functional change is intended or expected.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-03-15 09:11:10 -07007fd2fa68b52e0f38dd4915bf786d67445941eeddFactor out ebpf::parse_tracepoint functioneditsrc/cc/frontends/clang/tp_frontend_action.cceditsrc/cc/common.cceditsrc/cc/common.h
- tests/cc/CMakeLists.txttests/cc/test_parse_tracepoint.ccb9099c51ca570f33a5a9baef6f4f566c126b2b161584288670000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comAdd test for ebpf::parse_tracepoint function
The test prepares tracepoint format file and run
ebpf::parse_tracepoint on it. Then it compares
expected struct output with actual function result.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-03-15 09:11:10 -0700b9099c51ca570f33a5a9baef6f4f566c126b2b16Add test for ebpf::parse_tracepoint functionaddtests/cc/test_parse_tracepoint.ccedittests/cc/CMakeLists.txt
- src/cc/common.cctests/cc/test_parse_tracepoint.ccb8423e66ce450418c6142aab61ee9330e1fcefcc1584288670000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comStrengthen tracepoint format parsing
There's issue in current RHEL real time kernel with tracepoint format,
which makes bcc-tools to return wrong data.
Two new 'common_' fields were added and it causes 2 issues for tracepoint
format parser.
First issue
- is the gap between common fields and other fields, which is not
picked up by the parser, so the resulted struct is not aligned with
the data.
Second issue
- is the fact that current parser covers common fields with:
u64 __do_not_use__
so the new common fields are not accounted for.
This issue is solved in the following patch. I kept both
issues and fixes separated to make the change readable.
There's a 'not described gap' in the sched_wakeup's format file and
probably in other formats as well:
Having:
# cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/format
name: sched_wakeup
ID: 310
format:
field:unsigned short common_type; offset:0; size:2; signed:0;
field:unsigned char common_flags; offset:2; size:1; signed:0;
field:unsigned char common_preempt_count; offset:3; size:1; signed:0;
field:int common_pid; offset:4; size:4; signed:1;
field:unsigned char common_migrate_disable; offset:8; size:1; signed:0;
field:unsigned char common_preempt_lazy_count; offset:9; size:1; signed:0;
field:char comm[16]; offset:12; size:16; signed:1;
field:pid_t pid; offset:28; size:4; signed:1;
field:int prio; offset:32; size:4; signed:1;
field:int success; offset:36; size:4; signed:1;
field:int target_cpu; offset:40; size:4; signed:1;
There's "common_preempt_lazy_count" field on offset 9 with size 1:
common_preempt_lazy_count; offset:9; size:1;
and it's followed by "comm" field on offset 12:
field:char comm[16]; offset:12; size:16; signed:1;
which makes 2 bytes gap in between, that might confuse some applications
like bpftrace or bcc-tools library.
The tracepoint parser makes struct out of the field descriptions,
but does not account for such gaps.
I posted patch to fix this [1] in RT kernel, but that might take a while,
and we could easily fix our tracepoint parser to workaround this issue.
Adding code to detect this gaps and add 1 byte __pad_X fields, where X is
the offset number.
[1] https://lore.kernel.org/linux-rt-users/20200221153541.681468-1-jolsa@kernel.org/
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-03-15 09:11:10 -0700b8423e66ce450418c6142aab61ee9330e1fcefccStrengthen tracepoint format parsingedittests/cc/test_parse_tracepoint.cceditsrc/cc/common.cc
- src/cc/common.cctests/cc/test_parse_tracepoint.cc0a9d6db96c6410d2ef741507255f5258d64060321584288670000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comAdd support for new common fields
Current parser covers common fields with:
u64 __do_not_use__
so the new common fields are not accounted for.
Keeping the 'u64 __do_not_use__' field for backward compatibility
(who knows who's actualy using it) and adding new fields, like:
char __do_not_use__X
for each byte of extra common fields, where X is the offset of the
field.
With this fix the bcc-tools correctly parses tracepoints on RT kernel
and it's usable again.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2020-03-15 09:11:10 -07000a9d6db96c6410d2ef741507255f5258d6406032Add support for new common fieldseditsrc/cc/common.ccedittests/cc/test_parse_tracepoint.cc
- src/cc/libbpf5302614d31645db8fb5466e95ba7e6500c2c46c21584505598000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf: update to latest libbpf version
Pull in latest libbpf changes. In particular, containing BPF_KRETPROBE fix.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-03-17 21:26:38 -07005302614d31645db8fb5466e95ba7e6500c2c46c2libbpf: update to latest libbpf versioneditsrc/cc/libbpf
- examples/networking/net_monitor.pyca1b0af0eff9d994a49606899c2f110a68addeca1584508954000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comadding example/networking/net_monitor.py
Aggregates incoming network traffic
outputs source ip, destination ip, the number of their network traffic, and current time
Co-authored-by: gist-banana <gist.banana@gist.ac.kr>
2020-03-17 22:22:34 -0700ca1b0af0eff9d994a49606899c2f110a68addecaadding example/networking/net_monitor.pyaddexamples/networking/net_monitor.py
- CMakeLists.txtINSTALL.md4c1136ee6c08eb9fef86ebaafe2544692472b5b71584509203000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comMake -DCMAKE_INSTALL_PREFIX=/usr as the default (#2800)
* make -DCMAKE_INSTALL_PREFIX=/usr as the default
* remove -DCMAKE_INSTALL_PEREFIX=/usr from INSTALL.md as it gets the default
2020-03-17 22:26:43 -07004c1136ee6c08eb9fef86ebaafe2544692472b5b7Make -DCMAKE_INSTALL_PREFIX=/usr as the default (#2800)editINSTALL.mdeditCMakeLists.txt
- tools/profile_example.txtman/man8/profile.8tools/profile.pyf82ea454ea55ad73ee3284a0bd6fc3b45a7d73a81584571880000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: add option --cgroupmap to profile.py
2020-03-18 15:51:20 -0700f82ea454ea55ad73ee3284a0bd6fc3b45a7d73a8tools: add option --cgroupmap to profile.pyedittools/profile_example.txtedittools/profile.pyeditman/man8/profile.8
- src/cc/bcc_syms.cce1d53a3ab329ee3504dd58db09859baea0ca724a1584572748000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comDo not prepend /proc multiple times in bcc_resolve_symname
2020-03-18 16:05:48 -0700e1d53a3ab329ee3504dd58db09859baea0ca724aDo not prepend /proc multiple times in bcc_resolve_symnameeditsrc/cc/bcc_syms.cc
- tests/cc/test_usdt_probes.cc1cd3952b7c2bc7ab0e545f42711402b9f8fe65d81584572748000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comAdd regression test for bcc resolve symbol names
2020-03-18 16:05:48 -07001cd3952b7c2bc7ab0e545f42711402b9f8fe65d8Add regression test for bcc resolve symbol namesedittests/cc/test_usdt_probes.cc
- libbpf-tools/xfsslower.hlibbpf-tools/xfsslower.bpf.clibbpf-tools/.gitignorelibbpf-tools/Makefilelibbpf-tools/xfsslower.cc2772a334bd10f6e7f66b7d79c269ab9ca5e525c1584683049000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: add CO-RE xfsslower
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
2020-03-19 22:44:09 -0700c2772a334bd10f6e7f66b7d79c269ab9ca5e525clibbpf-tools: add CO-RE xfsslowereditlibbpf-tools/.gitignoreeditlibbpf-tools/Makefileaddlibbpf-tools/xfsslower.bpf.caddlibbpf-tools/xfsslower.haddlibbpf-tools/xfsslower.c
- tools/opensnoop.py510fc7425ccd0bc53d53a56ae847d786eb15e1ce1584685416000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comopensnoop: fix --cgroupmap with kfunc
Commit c347fe6c9f75 ("Support kfunc in opensnoop.py") introduces an
alternative probe on do_sys_open() with kfuncs instead of kprobes. This
new implementation is used if the kernel supports it. But it removed the
--cgroupmap filter added in commit b2aa29fa3269 ("tools: cgroup
filtering in execsnoop/opensnoop").
This patch adds the --cgroupmap filter in the kfunc implementation.
2020-03-19 23:23:36 -0700510fc7425ccd0bc53d53a56ae847d786eb15e1ceopensnoop: fix --cgroupmap with kfuncedittools/opensnoop.py
- INSTALL.md35c9940ee7297eafa7d8bcc8d9cda29a3b17a25b1584940362000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comchore: include Amazon Linux 2 binary option in INSTALL
2020-03-22 22:12:42 -070035c9940ee7297eafa7d8bcc8d9cda29a3b17a25bchore: include Amazon Linux 2 binary option in INSTALLeditINSTALL.md
- tools/tcptop.py6b8a89673dbba9b9203a6555735e451dd94778361584978424000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools: fix alignment of ipv6_key_t in tcptop
Fixes the following error on aarch64:
bpf: Failed to load program: Permission denied
; struct sock *sk = ctx->regs[0]; int copied = ctx->regs[1];
0: (79) r8 = *(u64 *)(r1 +8)
...
; struct ipv6_key_t ipv6_key = {.pid = pid};
79: (63) *(u32 *)(r10 -48) = r7
; struct ipv6_key_t ipv6_key = {.pid = pid};
80: (7b) *(u64 *)(r10 +8) = r9
invalid stack off=8 size=8
processed 96 insns (limit 1000000) max_states_per_insn 0 total_states 7 peak_states 7 mark_read 4
2020-03-23 08:47:04 -07006b8a89673dbba9b9203a6555735e451dd9477836tools: fix alignment of ipv6_key_t in tcptopedittools/tcptop.py
- tools/cachetop.py1b0fe40663e48b315e75a9b1ed74820207f766581585422718000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comChange the default sort order to Descending
currently with ascending sort the useful information
is commonly beyond the bottom of the terminal window
and it is necessary to reverse the sort manually every execution.
Signed-off-by: Mark Kogan <mkogan@redhat.com>
2020-03-28 12:11:58 -07001b0fe40663e48b315e75a9b1ed74820207f76658Change the default sort order to Descendingedittools/cachetop.py
- tools/capable.py9adda7092054e1637a68e61e391ac755416a2fb11585422758000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comtools/capable: fix compilation error
9d7feeed87c5 ("tools: add option --unique to capable.py") introduced a
compilation error when the --unique flag is passed.
Signed-off-by: Mauricio Vásquez <mauricio@kinvolk.io>
2020-03-28 12:12:38 -07009adda7092054e1637a68e61e391ac755416a2fb1tools/capable: fix compilation erroredittools/capable.py
- libbpf-tools/filelife.bpf.clibbpf-tools/filelife.hlibbpf-tools/filelife.clibbpf-tools/.gitignorelibbpf-tools/Makefile85f5e7d5673e3273f61550d806d348626dffc1401585424916000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: add CO-RE filelife
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
2020-03-28 12:48:36 -070085f5e7d5673e3273f61550d806d348626dffc140libbpf-tools: add CO-RE filelifeaddlibbpf-tools/filelife.ceditlibbpf-tools/.gitignoreaddlibbpf-tools/filelife.bpf.ceditlibbpf-tools/Makefileaddlibbpf-tools/filelife.h
- introspection/CMakeLists.txte323254466575e03d753a33c77667011626c389f1585426415000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.commake -lrt linking optional
On Android there is no standalone rt library and relevant symbols are provided
by libc (bionic).
2020-03-28 13:13:35 -0700e323254466575e03d753a33c77667011626c389fmake -lrt linking optionaleditintrospection/CMakeLists.txt
- examples/networking/http_filter/http-parse-complete.py915d6d7617b20d4af8360c1d53efe8abd8697efa1585427578000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comcorrecting input to hex using ord funtion
2020-03-28 13:32:58 -0700915d6d7617b20d4af8360c1d53efe8abd8697efacorrecting input to hex using ord funtioneditexamples/networking/http_filter/http-parse-complete.py
- examples/tracing/mallocstacks.py472f9b3bd6bcc63e6e959148320eb76184c518701585459537000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.commallocstacks: validating before stacktrace walk
2020-03-28 22:25:37 -0700472f9b3bd6bcc63e6e959148320eb76184c51870mallocstacks: validating before stacktrace walkeditexamples/tracing/mallocstacks.py
- examples/networking/http_filter/http-parse-simple.py4f6ecea67b58699b52c315088c5829448add57c51585460142000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comhttp-parse-simple.py: fix wrong start position
Signed-off-by: Jean-Philippe Menil <jpmenil@gmail.com>
2020-03-28 22:35:42 -07004f6ecea67b58699b52c315088c5829448add57c5http-parse-simple.py: fix wrong start positioneditexamples/networking/http_filter/http-parse-simple.py
- libbpf-tools/opensnoop.bpf.clibbpf-tools/opensnoop.clibbpf-tools/opensnoop.hab54de2e4449027f2b4dccd022adc57bec4fd4eb1585525012000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comlibbpf-tools: CO-RE opensnoop minor improvements
* allow passing 0 as valid uid
* fix type for targ_uid
* improve uid validation (uid >= 4294967295 now invalid)
2020-03-29 16:36:52 -0700ab54de2e4449027f2b4dccd022adc57bec4fd4eblibbpf-tools: CO-RE opensnoop minor improvementseditlibbpf-tools/opensnoop.bpf.ceditlibbpf-tools/opensnoop.ceditlibbpf-tools/opensnoop.h
- src/cc/api/BPF.ccsrc/cc/api/BPF.hexamples/cpp/FollyRequestContextSwitch.cctests/cc/test_usdt_probes.cc689f90087e0d59caea63e10be04bcf1172a90c4f1585974837000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.com[C++] add BPF::enable_usdt_all() and disble_usdt_all() to handle all the USDT at once (#2854)
* add BPF::enable_usdt_all() to enable all the USDT
* add detach_usdt_all() to detach all the USDTs
2020-04-03 21:33:57 -0700689f90087e0d59caea63e10be04bcf1172a90c4f[C++] add BPF::enable_usdt_all() and disble_usdt_all() to handle all the USDT at once (#2854)edittests/cc/test_usdt_probes.cceditsrc/cc/api/BPF.cceditsrc/cc/api/BPF.heditexamples/cpp/FollyRequestContextSwitch.cc
- examples/tracing/nflatency.py495a4a3403371b3fb1f7049a8cefc996621e61aa1585980153000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comexamples/tracing: add nflatency - netfilter hook metrics
This adds a kprobe / kretprobe for chasing down slow netfilter hooks.
Since, often, the slowest hooks are on connection initialization and
teardown, it is bucketed by TCP flags. (rather than dive deep in to
conntrack)
Signed-off-by: Casey Callendrello <cdc@redhat.com>
2020-04-03 23:02:33 -0700495a4a3403371b3fb1f7049a8cefc996621e61aaexamples/tracing: add nflatency - netfilter hook metricsaddexamples/tracing/nflatency.py
- tests/python/CMakeLists.txttests/python/test_lpm_trie.py533391eaa94c4b3a148bf801b8aea5bb803c1e9d1586153355000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comadd test_lpm_trie.py test
test_lpm_trie.py has been in the repo for quite some time,
but is not included in the unit test.
The issue https://github.com/iovisor/bcc/issues/2860
exposed an issue involved in using together with BTF,
which requires the key type to be a structure.
Let add it as a unit test so we can be sure
lpm_trie map is supported properly by bcc.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-04-05 23:09:15 -0700533391eaa94c4b3a148bf801b8aea5bb803c1e9dadd test_lpm_trie.py testedittests/python/CMakeLists.txtedittests/python/test_lpm_trie.py
- src/cc/bpf_module.ccf35dae07bbe48f6233bf50f05ddbf835cc18c86e1586189548000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comadjust layout string in JIT with llvm11 128bit spec support
To fix the issue (https://github.com/iovisor/bcc/issues/2827)
which exposed a problem with aarch64 frontend and bpf backend
regarding __int128 type, the following llvm patch
https://reviews.llvm.org/D76587
landed to explicitly support i128 type in bpf layout spec.
Adjust the layout string in bpf_module JIT compilation
accordingly.
Signed-off-by: Yonghong Song <yhs@fb.com>
2020-04-06 09:12:28 -0700f35dae07bbe48f6233bf50f05ddbf835cc18c86eadjust layout string in JIT with llvm11 128bit spec supporteditsrc/cc/bpf_module.cc
- tests/python/CMakeLists.txtsrc/cc/bcc_syms.cctests/python/test_uprobes2.py007ee4930798f854da47f5838097193d75c67ad11586192176000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comTranslate virtual addresses to binary addresses for shared libs as well.
Quoting https://refspecs.linuxbase.org/elf/elf.pdf:
```
Symbol table entries for different object file types have slightly different
interpretations for the st_value member.
- In relocatable files, st_value holds alignment constraints for a symbol
whose section index is SHN_COMMON.
- In relocatable files, st_value holds a section offset for a defined symbol.
That is, st_value is an offset from the beginning of the section that st_shndx
identifies.
- In executable and shared object files, st_value holds a virtual address. To
make these files' symbols more useful for the dynamic linker, the section offset
(file interpretation) gives way to a virtual address (memory interpretation) for
which the section number is irrelevant.
```
This is a problem in practice as well. I run into this while tracing shared
libraries on Android with bpftrace. Some of them have text sections mmapped
at different offset than file offset which results in probes being placed
at wrong offsets.
2020-04-06 09:56:16 -0700007ee4930798f854da47f5838097193d75c67ad1Translate virtual addresses to binary addresses for shared libs as well.edittests/python/CMakeLists.txteditsrc/cc/bcc_syms.ccaddtests/python/test_uprobes2.py
- examples/tracing/io_latencies.py5057bbe6fb00a112c03ac5c5277646fd9602c1b11586192312000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comexamples/tracing: add io_latencies - IO latency distribution monitor
This adds flexible low overhead latency percentile monitoring for block
devices which can be useful in understanding and debugging IO related
issues.
Signed-off-by: Tejun Heo <tj@kernel.org>
2020-04-06 09:58:32 -07005057bbe6fb00a112c03ac5c5277646fd9602c1b1examples/tracing: add io_latencies - IO latency distribution monitoraddexamples/tracing/io_latencies.py
- tools/filelife.py15d7955e07a942340610f71e44f44046b960e3a81586194496000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comUpdate pid filter
Update pid filter; u32 pid = bpf_get_current_pid_tgid() >> 32;
2020-04-06 10:34:56 -070015d7955e07a942340610f71e44f44046b960e3a8Update pid filteredittools/filelife.py
- docs/reference_guide.md7a3854319929e7f126b893c74290076cf7a328b11586273568000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comdoc: fix wrong references to get_syscall_name
2020-04-07 08:32:48 -07007a3854319929e7f126b893c74290076cf7a328b1doc: fix wrong references to get_syscall_nameeditdocs/reference_guide.md
- examples/tracing/io_latencies.pytools/biolatpcts.py1515f28a483d62ff056602daacecd7631c98492d1587139467000https://buildbot.iovisor.org/jenkins/user/tjtjtj@kernel.orgtools: Move io_iolatencies.py example to tools/biolatpcts.py
2020-04-17 12:04:27 -04001515f28a483d62ff056602daacecd7631c98492dtools: Move io_iolatencies.py example to tools/biolatpcts.pyaddtools/biolatpcts.pydeleteexamples/tracing/io_latencies.py
- tools/biolatpcts.py66ab787b5f853d97bad8fb950b12b11b8e281b7c1587152520000https://buildbot.iovisor.org/jenkins/user/tjtjtj@kernel.orgtools/biolatpcts: Use #!/usr/bin/python instead of python3
Nothing in the script requires python3.
2020-04-17 15:42:00 -040066ab787b5f853d97bad8fb950b12b11b8e281b7ctools/biolatpcts: Use #!/usr/bin/python instead of python3edittools/biolatpcts.py
- tools/biolatpcts.py7214903a9c42c3501e50a47d3698b77547036f701587152533000https://buildbot.iovisor.org/jenkins/user/tjtjtj@kernel.orgtools/biolatpcts: --pcts handling improvements
* Multiple arguments parsing conflicts with positional argument and can become
confusing. Use a single comma separated list instead.
* Instead of converting to floats while parsing arguments, keep the strings
verbatim and use them when outputting results. This allows matching the same
target percentile string in the output and is helpful when it's consumed by
other programs.
2020-04-17 15:42:13 -04007214903a9c42c3501e50a47d3698b77547036f70tools/biolatpcts: --pcts handling improvementsedittools/biolatpcts.py
- tools/biolatpcts.pyfbf0392d72a6ced87a5e8ea8a84dfddb5a86c6bd1587152547000https://buildbot.iovisor.org/jenkins/user/tjtjtj@kernel.orgtools/biolatpcts: Accept device name/node for target device selection
MAJ:MIN is cumbersome. Update it to accept DEVNAME and /dev/DEVNAME too.
2020-04-17 15:42:27 -0400fbf0392d72a6ced87a5e8ea8a84dfddb5a86c6bdtools/biolatpcts: Accept device name/node for target device selectionedittools/biolatpcts.py
- man/man8/biolatpcts.8tools/biolatpcts_example.txt1e9c56f40a44faf72569ddc2e37ca5d554aee93b1587152557000https://buildbot.iovisor.org/jenkins/user/tjtjtj@kernel.orgtools/biolatpcts: Add the example file and man page
2020-04-17 15:42:37 -04001e9c56f40a44faf72569ddc2e37ca5d554aee93btools/biolatpcts: Add the example file and man pageaddman/man8/biolatpcts.8addtools/biolatpcts_example.txt
- examples/tracing/biolatpcts.pyexamples/tracing/biolatpcts_example.txt10519c74c72b58109a2c14eba59d3cfe985ddc0f1587154392000https://buildbot.iovisor.org/jenkins/user/tjtjtj@kernel.orgexamples: Add biolatpcts.py example
This is simplified version of tools/biolatpcts.py and demonstrates how to
obtain and calculate latency percentiles.
2020-04-17 16:13:12 -040010519c74c72b58109a2c14eba59d3cfe985ddc0fexamples: Add biolatpcts.py exampleaddexamples/tracing/biolatpcts.pyaddexamples/tracing/biolatpcts_example.txt
- tests/cc/test_usdt_probes.ccsrc/cc/api/BPF.hf8f230c8162e59202987fb46f2d3d867a5cbef1d1587255987000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comadd attribute readers to class USDT (C++ API)
2020-04-18 17:26:27 -0700f8f230c8162e59202987fb46f2d3d867a5cbef1dadd attribute readers to class USDT (C++ API)editsrc/cc/api/BPF.hedittests/cc/test_usdt_probes.cc
- CMakeLists.txt1599c2ef8206988d5df7eeadc3c5138c006ac2451587256414000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.combuild: fix clang 10 build
some distros already packaging clang 10 (checked fedora and arch) no longer
ship all the individual libclang*.so component libraries.
Instead, clang from 9.0 onwards provides a new lib, libclang-cpp.so, which
includes everything we need.
Tell cmake to use it if the individual libraries are no longer found.
(Build-wise, if both are present it is more efficient to use the individual
components so keep these first)
2020-04-18 17:33:34 -07001599c2ef8206988d5df7eeadc3c5138c006ac245build: fix clang 10 buildeditCMakeLists.txt
- libbpf-tools/README.mdc1d3a65f0d6dd29aad71ffc87f21345473a2bca31587259187000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comAdded kernel recompile guidance for libbpf CO-RE (#2876)
Added kernel recompile guidance for libbpf CO-RE
2020-04-18 18:19:47 -0700c1d3a65f0d6dd29aad71ffc87f21345473a2bca3Added kernel recompile guidance for libbpf CO-RE (#2876)editlibbpf-tools/README.md
- src/cc/bcc_version.h.insrc/cc/CMakeLists.txtexamples/cpp/CMakeLists.txtexamples/cpp/HelloWorld.cc6d61622f6300fa140647de82122e66b6288fe2ed1587262787000https://buildbot.iovisor.org/jenkins/user/noreplynoreplynoreply@github.comAdd `bcc_version.h` to access LIBBCC_VERSION from C/C++ (#2856)
add bcc/bcc_version.h to install
2020-04-18 19:19:47 -07006d61622f6300fa140647de82122e66b6288fe2edAdd `bcc_version.h` to access LIBBCC_VERSION from C/C++ (#2856)addsrc/cc/bcc_version.h.ineditexamples/cpp/HelloWorld.cceditsrc/cc/CMakeLists.txteditexamples/cpp/CMakeLists.txt
- INSTALL.mdd3359b294636579649f200deabe71fd98d4edd351587395451000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comImprove ubuntu installation description
2020-04-20 08:10:51 -0700d3359b294636579649f200deabe71fd98d4edd35Improve ubuntu installation descriptioneditINSTALL.md
- src/cc/frontends/b/codegen_llvm.hsrc/cc/frontends/b/codegen_llvm.cc45e63f2b316cdce2d8cc925f6f14a8726ade9ff61587416401000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comfix llvm 11 compilation issues
The llvm CreateCall used in bcc is deprecated in llvm 11:
https://reviews.llvm.org/D76269
The llvm CreateMemCpy is changed in llvm 11 as well:
https://reviews.llvm.org/D71473
This caused bcc compilation error.
/home/yhs/work/bcc/src/cc/frontends/b/codegen_llvm.cc: In member function
‘ebpf::StatusTuple ebpf::cc::CodegenLLVM::emit_log(ebpf::cc::Method CallExprNode*)’:
/home/yhs/work/bcc/src/cc/frontends/b/codegen_llvm.cc:691:39: error: no matching function for call to
‘llvm::IRBuilder<>::CreateCall(llvm::Value*&, std::vector<llvm::Value*, std::allocator<llvm::Value*> >&)’
expr_ = B.CreateCall(printk_fn, args);
^
...
/home/yhs/work/bcc/src/cc/frontends/b/codegen_llvm.cc: In member function
‘virtual ebpf::StatusTuple ebpf::cc::CodegenLLVM::visit_string_exp_node(ebpf::cc::StringExprNode*)’:
/home/yhs/work/bcc/src/cc/frontends/b/codegen_llvm.cc:440:55: error: no matching function for call to
‘llvm::IRBuilder<>::CreateMemCpy(llvm:Value*&, int, llvm::Value*&, int, std::__cxx11::basic_string<char>::size_type)’
B.CreateMemCpy(ptr, 1, global, 1, n->val_.size() + 1);
^
...
This patch fixed the compilation issue.
2020-04-20 14:00:01 -070045e63f2b316cdce2d8cc925f6f14a8726ade9ff6fix llvm 11 compilation issueseditsrc/cc/frontends/b/codegen_llvm.cceditsrc/cc/frontends/b/codegen_llvm.h
- src/cc/libbpfsrc/cc/libbpf.cintrospection/bps.csrc/cc/compat/linux/virtual_bpf.hsrc/cc/export/helpers.hdocs/kernel-versions.mddf3e7d673da4bd4acab333f28851eccf00ca9f871587431304000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comsync to latest libbpf
sync to libbpf v0.0.8. Add newer helpers to
helpers.h, libbpf.c error reporting and docs.
2020-04-20 18:08:24 -0700df3e7d673da4bd4acab333f28851eccf00ca9f87sync to latest libbpfeditintrospection/bps.ceditsrc/cc/export/helpers.heditsrc/cc/libbpfeditsrc/cc/libbpf.ceditdocs/kernel-versions.mdeditsrc/cc/compat/linux/virtual_bpf.h
- debian/changelogceb458d6a07a42d8d6d3c16a3b8e387b5131d6101587436551000https://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songys114321@gmail.comprepare for release v0.14.0
added changelog for release v0.14.0
2020-04-20 19:35:51 -0700ceb458d6a07a42d8d6d3c16a3b8e387b5131d610prepare for release v0.14.0editdebian/changelog
githttps://buildbot.iovisor.org/jenkins/user/noreplynoreplyhttps://buildbot.iovisor.org/jenkins/user/yonghong-songyonghong-songhttps://buildbot.iovisor.org/jenkins/user/tjtjhttps://buildbot.iovisor.org/jenkins/user/andriinandriinhttps://buildbot.iovisor.org/jenkins/user/edwardwuedwardwu471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc25/471/471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc26/471/471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc27/471/471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc28/471/471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=ubuntu1604/471/471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=ubuntu1710/471/471https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=ubuntu1804/471/