BPF List
 help / color / mirror / Atom feed
From: Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>
To: "'Yonghong Song'" <yhs@fb.com>,
	"'Toke Høiland-Jørgensen'" <toke@redhat.com>,
	bpf@vger.kernel.org
Cc: <ast@kernel.org>, <andrii@kernel.org>, <daniel@iogearbox.net>,
	<joannelkoong@gmail.com>, <brouer@redhat.com>
Subject: Re: [PATCH] bpf: fix rq lock recursion issue
Date: Mon, 13 Jun 2022 10:47:07 -0700	[thread overview]
Message-ID: <005f01d87f4d$9a075210$ce15f630$@quicinc.com> (raw)
In-Reply-To: <fc16df47-df2b-ffa2-4e66-5a3dc92cb4db@fb.com>


On 6/13/22 9:35 AM, Yonghong Song wrote:
>
>
> On 6/13/22 2:22 AM, Toke Høiland-Jørgensen wrote:
>> !-------------------------------------------------------------------|
>>    This Message Is From an External Sender
>>    This message came from outside your organization.
>> |-------------------------------------------------------------------!
>>
>> Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com> writes:
>>
>>> Below recursion is observed in a rare scenario where __schedule()
>>> takes rq lock, at around same time task's affinity is being changed,
>>> bpf function for tracing sched_switch calls migrate_enabled(),
>>> checks for affinity change (cpus_ptr != cpus_mask) lands into
>>> __set_cpus_allowed_ptr which tries acquire rq lock and causing the
>>> recursion bug.
>>
>> So this only affects tracing programs that attach to tasks that can have
>> their affinity changed? Or do we need to review migrate_enable() vs
>> preempt_enable() for networking hooks as well?
>
> I think that changing from migrate_disable() to preempt_disable()
> won't work from RT kernel. In fact, the original preempt_disable() to
> migrate_disable() is triggered by RT kernel discussion.
>
> As you mentioned, this is a very special case. Not sure whether we have
> a good way to fix it or not. Is it possible we can check whether rq lock
> is held or not under condition cpus_ptr != cpus_mask? If it is,
> migrate_disable() (or a variant of it) should return an error code
> to indicate it won't work?

That essentially becomes using preempt_enable/disable().
If we need migrate_enable/disable() for RT kernels, we can
add specific check for RT Kernels like below which should fix
issue for non-RT Kernels? 

diff --git a/include/linux/bpf.h b/include/linux/bpf.h
index 2b914a56a2c5..ec1a287dbf5e 100644
--- a/include/linux/bpf.h
+++ b/include/linux/bpf.h
@@ -1414,7 +1414,11 @@ bpf_prog_run_array(const struct bpf_prog_array 
*array,
         if (unlikely(!array))
                 return ret;

+#ifdef CONFIG_PREEMPT_RT
         migrate_disable();
+#else
+       preempt_disable();
+#endif
         old_run_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
         item = &array->items[0];
         while ((prog = READ_ONCE(item->prog))) {
@@ -1423,7 +1427,11 @@ bpf_prog_run_array(const struct bpf_prog_array 
*array,
                 item++;
         }
         bpf_reset_run_ctx(old_run_ctx);
+#ifdef CONFIG_PREEMPT_RT
         migrate_enable();
+#else
+       preempt_enable();
+#endif
         return ret;
  }

>
>>
>> -Toke
>>


  reply	other threads:[~2022-06-13 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  2:52 [PATCH] bpf: fix rq lock recursion issue Satya Durga Srinivasu Prabhala
2022-06-13  9:22 ` Toke Høiland-Jørgensen
2022-06-13 16:17   ` Satya Durga Srinivasu Prabhala
2022-06-13 16:35   ` Yonghong Song
2022-06-13 17:47     ` Satya Durga Srinivasu Prabhala [this message]
2022-06-13 21:01       ` Alexei Starovoitov
2022-06-13 21:35         ` Satya Durga Srinivasu Prabhala
2022-06-13 21:49           ` Alexei Starovoitov
2022-06-14  1:10             ` Satya Durga Srinivasu Prabhala
2022-06-14  6:09               ` Yonghong Song
2022-06-24  6:56                 ` Satya Durga Srinivasu Prabhala
2022-06-24 16:46                   ` Alexei Starovoitov

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='005f01d87f4d$9a075210$ce15f630$@quicinc.com' \
    --to=quic_satyap@quicinc.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=joannelkoong@gmail.com \
    --cc=toke@redhat.com \
    --cc=yhs@fb.com \
    /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