public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcaov@gmail.com>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: linux-riscv@lists.infradead.org, Guo Ren <guoren@kernel.org>,
	bpf@vger.kernel.org, Hou Tao <houtao@huaweicloud.com>,
	yonghong.song@linux.dev,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Puranjay Mohan <puranjay12@gmail.com>
Subject: Re: RISC-V uprobe bug (Was: Re: WARNING: CPU: 3 PID: 261 at kernel/bpf/memalloc.c:342)
Date: Sun, 27 Aug 2023 10:35:06 +0200	[thread overview]
Message-ID: <ZOsKukBz8i+h4Y8j@nam-dell> (raw)
In-Reply-To: <87cyz8sy4y.fsf@all.your.base.are.belong.to.us>

On Sun, Aug 27, 2023 at 10:11:25AM +0200, Björn Töpel wrote:
> The default implementation of is_trap_insn() which RISC-V is using calls
> is_swbp_insn(), which is doing what your patch does. Your patch does not
> address the issue.

is_swbp_insn() does this:

        #ifdef CONFIG_RISCV_ISA_C
                return (*insn & 0xffff) == UPROBE_SWBP_INSN;
        #else
                return *insn == UPROBE_SWBP_INSN;
        #endif

...so it doesn't even check for 32-bit ebreak if C extension is on. My patch
is not the same.

But okay, if it doesn't solve the problem, then I must be wrong somewhere.
 
> We're taking an ebreak trap from kernel space. In this case we should
> never look for a userland (uprobe) handler at all, only the kprobe
> handlers should be considered.
> 
> In this case, the TIF_UPROBE is incorrectly set, and incorrectly (not)
> handled in the "common entry" exit path, which takes us to the infinite
> loop.

This change makes a lot of sense, no reason to check for uprobes if exception
comes from the kernel.

Best regards,
Nam

  reply	other threads:[~2023-08-27  8:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 10:32 WARNING: CPU: 3 PID: 261 at kernel/bpf/memalloc.c:342 Björn Töpel
2023-08-25 15:28 ` Yonghong Song
2023-08-25 18:53   ` Alexei Starovoitov
2023-08-25 19:49     ` Alexei Starovoitov
2023-08-25 21:31       ` Andrii Nakryiko
2023-08-26 22:49         ` Kumar Kartikeya Dwivedi
2023-08-26  3:48   ` Hou Tao
2023-08-26  9:23     ` Björn Töpel
2023-08-26 10:27       ` Hou Tao
2023-08-26 10:49         ` Björn Töpel
2023-08-27  8:37           ` Björn Töpel
2023-08-27 14:53             ` Yonghong Song
2023-08-28 13:57               ` Hou Tao
2023-08-29  0:54                 ` Yonghong Song
2023-08-29  7:26                 ` Björn Töpel
2023-08-29 11:46                   ` Björn Töpel
2023-08-30 12:15                     ` Hou Tao
2023-08-29 12:54                   ` Björn Töpel
2023-08-29 15:26                 ` Alexei Starovoitov
2023-08-30 12:08                   ` Hou Tao
2023-08-30 21:05                     ` Alexei Starovoitov
2023-08-26 13:44 ` RISC-V uprobe bug (Was: Re: WARNING: CPU: 3 PID: 261 at kernel/bpf/memalloc.c:342) Björn Töpel
2023-08-26 18:12   ` Nam Cao
2023-08-26 18:31     ` Nam Cao
2023-08-27  8:11     ` Björn Töpel
2023-08-27  8:35       ` Nam Cao [this message]
2023-08-27  9:04         ` Björn Töpel
2023-08-27  9:39           ` Nam Cao
2023-08-27 19:20             ` Björn Töpel
2023-08-27 19:41               ` Nam Cao
2023-08-27 20:15               ` Nam Cao

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=ZOsKukBz8i+h4Y8j@nam-dell \
    --to=namcaov@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=guoren@kernel.org \
    --cc=houtao@huaweicloud.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=puranjay12@gmail.com \
    --cc=yonghong.song@linux.dev \
    /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