GitHub pull request #2986 of commit 917dd1d3968d8720831867dfb779a2a084c3f838, no merge conflicts.sha1origin/pr/2986/mergeghprbActualCommit917dd1d3968d8720831867dfb779a2a084c3f838ghprbActualCommitAuthorYonghong SongghprbActualCommitAuthorEmailyhs@fb.comghprbAuthorRepoGitUrlhttps://github.com/iovisor/bcc.gitghprbTriggerAuthorghprbTriggerAuthorEmailghprbTriggerAuthorLoginghprbTriggerAuthorLoginMentionghprbPullId2986ghprbTargetBranchmasterghprbSourceBranchyhs_devGIT_BRANCHyhs_devghprbPullAuthorEmailghprbPullAuthorLoginyonghong-songghprbPullAuthorLoginMention@yonghong-songghprbPullDescriptionGitHub pull request #2986 of commit 917dd1d3968d8720831867dfb779a2a084c3f838, no merge conflicts.ghprbPullTitlebpf: use bpf_probe_read in implicitly generated kernel mem readghprbPullLinkhttps://github.com/iovisor/bcc/pull/2986ghprbPullLongDescriptionCurrently, bcc rewriter uses bpf_probe_read_kernel() for implicitly specified\r\nkernel memory read. This is not totally correct. Some user memory in kernel\r\ndata structure may be accessed. bpf_probe_read_kernel() may fail with\r\nlater kernels. Let us revert back to old bpf_probe_read().ghprbCommentBodynullghprbGhRepositoryiovisor/bccghprbCredentialsId6d3daf13-69b8-48b1-9c8f-ec5353264113false<a title="bpf: use bpf_probe_read in implicitly generated kernel mem read" href="https://github.com/iovisor/bcc/pull/2986">PR #2986</a>: bpf: use bpf_probe_read in ...#56812098687460664bcc-pr #568568false5684552SUCCESS1592800314843https://buildbot.iovisor.org/jenkins/job/bcc-pr/568/git568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=fc25/568/568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=fc26/568/568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=fc27/568/568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=fc28/568/568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=ubuntu1604/568/568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=ubuntu1710/568/568https://buildbot.iovisor.org/jenkins/job/bcc-pr/label=ubuntu1804/568/