From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24659] New: kernel 5.2 bpf -- user and kernel-space map reads not synchronized?
Date: Mon, 10 Jun 2019 17:09:00 -0000 [thread overview]
Message-ID: <bug-24659-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24659
Bug ID: 24659
Summary: kernel 5.2 bpf -- user and kernel-space map reads not
synchronized?
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: me at serhei dot io
Target Milestone: ---
It appears that the recent kernels (seen on 5.2 rawhide) introduce some timing
issue between kernel- and user-space map operations.
global value//=2
global status//=2
probe begin {
println("BEGIN")
value = 2
status = 2
}
probe kernel.function("vfs_read") {
status = 0
if (value == 2) next
status = 1
}
probe kernel.function("vfs_read") {
printf("vfs_read\n")
printf("value %d\n", value)
printf("status %d\n", status)
if (status != 2) exit()
}
probe end {
printf("end\n")
printf("value %d\n", value)
printf("status %d\n", status)
if (status)
println("END FAIL")
else
println("END PASS")
}
In this example, probe end runs too soon after the map update in vfs_read and
receives an updated value. Changing the second probe vfs_read to probe
timer.s(2) would make the testcase pass.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-06-10 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 17:09 me at serhei dot io [this message]
2019-06-10 17:10 ` [Bug bpf/24659] " me at serhei dot io
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-24659-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).