BPF List
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Selftest failures related to kern_sync_rcu()
Date: Thu, 08 Apr 2021 21:34:47 +0200	[thread overview]
Message-ID: <87blaozi20.fsf@toke.dk> (raw)

Hi Andrii

I'm getting some selftest failures that all seem to have something to do
with kern_sync_rcu() not being enough to trigger the kernel events that
the selftest expects:

$ ./test_progs | grep FAIL
test_lookup_update:FAIL:map1_leak inner_map1 leaked!
#15/1 lookup_update:FAIL
#15 btf_map_in_map:FAIL
test_exit_creds:FAIL:null_ptr_count unexpected null_ptr_count: actual 0 == expected 0
#123/2 exit_creds:FAIL
#123 task_local_storage:FAIL
test_exit_creds:FAIL:null_ptr_count unexpected null_ptr_count: actual 0 == expected 0
#123/2 exit_creds:FAIL
#123 task_local_storage:FAIL

They are all fixed by adding a sleep(1) after the call(s) to
kern_sync_rcu(), so I'm guessing it's some kind of
timing/synchronisation problem. Is there a particular kernel config
that's needed for the membarrier syscall trick to work? I've tried with
various settings of PREEMPT and that doesn't really seem to make any
difference...

-Toke


             reply	other threads:[~2021-04-08 19:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 19:34 Toke Høiland-Jørgensen [this message]
2021-04-13  3:38 ` Selftest failures related to kern_sync_rcu() Andrii Nakryiko
2021-04-13  8:50   ` Toke Høiland-Jørgensen
2021-04-13 21:43     ` Andrii Nakryiko
2021-04-14 15:54       ` Alexei Starovoitov
2021-04-14 17:52         ` Paul E. McKenney
2021-04-14 17:59           ` Alexei Starovoitov
2021-04-14 18:19             ` Paul E. McKenney
2021-04-14 18:39               ` Toke Høiland-Jørgensen
2021-04-14 18:41                 ` Paul E. McKenney
2021-04-14 19:18                   ` Toke Høiland-Jørgensen
2021-04-14 21:25                     ` Paul E. McKenney
2021-04-14 22:13                       ` Andrii Nakryiko
2021-04-14 22:27                         ` Paul E. McKenney
2021-04-14 22:47                         ` Toke Høiland-Jørgensen
2021-04-14 18:27             ` Toke Høiland-Jørgensen

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=87blaozi20.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.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