From: Mark Brown <broonie@kernel.org>
To: Pedro Falcato <pfalcato@suse.de>
Cc: Aishwarya <aishwarya.tcv@arm.com>,
pulehui@huaweicloud.com, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, jannh@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, mhiramat@kernel.org, oleg@redhat.com,
peterz@infradead.org, pulehui@huawei.com, stable@vger.kernel.org,
vbabka@suse.cz, Ryan.Roberts@arm.com, Dev.Jain@arm.com
Subject: Re: [PATCH v1 4/4] selftests/mm: Add test about uprobe pte be orphan during vma merge
Date: Tue, 10 Jun 2025 12:34:57 +0100 [thread overview]
Message-ID: <97432af8-da8f-4cc6-96f0-ccc8297b7029@sirena.org.uk> (raw)
In-Reply-To: <f5tx6ko7xu2ulvfwu6srlaly6omqcciez2qh6jmcd6fob3szgm@cedwkuqgw34b>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Tue, Jun 10, 2025 at 12:27:28PM +0100, Pedro Falcato wrote:
> On Tue, Jun 10, 2025 at 11:37:29AM +0100, Aishwarya wrote:
> > 7155 12:46:54.650730 # # # handle_uprobe_upon_merged_vma: Test terminated by assertion
> > 7156 12:46:54.661750 # # # FAIL merge.handle_uprobe_upon_merged_vma
> > 7157 12:46:54.662030 # # not ok 8 merge.handle_uprobe_upon_merged_vma
> So, basically we're not finding the uprobe (I guess CONFIG_UPROBES isn't set in
> defconfig, and it's not in the mm/config either), and the test just fails instead
> of skipping.
Indeed:
$ grep UPROBES arch/arm64/configs/defconfig tools/testing/selftests/mm/config
$
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-06-10 11:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 15:56 [PATCH v1 0/4] Fix uprobe pte be overwritten when expanding vma Pu Lehui
2025-05-29 15:56 ` [PATCH v1 1/4] mm: " Pu Lehui
2025-05-30 9:28 ` Lorenzo Stoakes
2025-05-30 18:51 ` David Hildenbrand
2025-06-02 11:55 ` Lorenzo Stoakes
2025-06-02 12:26 ` David Hildenbrand
2025-06-02 13:26 ` Lorenzo Stoakes
2025-06-02 16:28 ` David Hildenbrand
2025-06-02 17:01 ` Lorenzo Stoakes
2025-06-03 12:16 ` David Hildenbrand
2025-06-04 1:51 ` Andrew Morton
2025-05-29 15:56 ` [PATCH v1 2/4] mm: Expose abnormal new_pte during move_ptes Pu Lehui
2025-05-29 19:19 ` Andrew Morton
2025-05-30 1:24 ` Pu Lehui
2025-05-30 3:47 ` Andrew Morton
2025-05-30 10:21 ` Lorenzo Stoakes
2025-05-30 16:44 ` Oleg Nesterov
2025-05-29 15:56 ` [PATCH v1 3/4] selftests/mm: Extract read_sysfs and write_sysfs into vm_util Pu Lehui
2025-05-30 11:48 ` Lorenzo Stoakes
2025-06-03 7:17 ` Pu Lehui
2025-06-04 2:36 ` Andrew Morton
2025-06-04 8:21 ` Pu Lehui
2025-05-29 15:56 ` [PATCH v1 4/4] selftests/mm: Add test about uprobe pte be orphan during vma merge Pu Lehui
2025-05-30 11:32 ` Lorenzo Stoakes
2025-06-03 7:08 ` Pu Lehui
2025-06-03 9:56 ` Lorenzo Stoakes
2025-06-10 10:37 ` Aishwarya
2025-06-10 11:27 ` Pedro Falcato
2025-06-10 11:34 ` Mark Brown [this message]
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=97432af8-da8f-4cc6-96f0-ccc8297b7029@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Dev.Jain@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=Ryan.Roberts@arm.com \
--cc=aishwarya.tcv@arm.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=pfalcato@suse.de \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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