From: "nobuta.keiya@fujitsu.com" <nobuta.keiya@fujitsu.com> To: "'Madhavan T. Venkataraman'" <madvenka@linux.microsoft.com>, "mark.rutland@arm.com" <mark.rutland@arm.com>, "broonie@kernel.org" <broonie@kernel.org>, "jpoimboe@redhat.com" <jpoimboe@redhat.com>, "ardb@kernel.org" <ardb@kernel.org>, "sjitindarsingh@gmail.com" <sjitindarsingh@gmail.com>, "catalin.marinas@arm.com" <catalin.marinas@arm.com>, "will@kernel.org" <will@kernel.org>, "jmorris@namei.org" <jmorris@namei.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "live-patching@vger.kernel.org" <live-patching@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: RE: [PATCH v13 11/11] arm64: Select HAVE_RELIABLE_STACKTRACE Date: Wed, 26 Jan 2022 10:20:16 +0000 [thread overview] Message-ID: <TY2PR01MB5257BE671A481D81F1A40E0185209@TY2PR01MB5257.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <825b8b72-c746-ba24-7142-3fff481e82d6@linux.microsoft.com> > I have not seen any activity on that in a long time. IIRC, Julien quit RedHat. > I don't know if anyone else has taken over this work in RedHat. > > Sorry, I don't have any more information. > > Madhavan Thanks for your information. By the way, I'm considering test code for arch_stack_walk_reliable(). Specifically, I apply Suraj's patch to enable livepatch, and added a function that sleeps between SYM_CODE_START and SYM_CODE_END, then livepatch checks if the task has an unreliable stack. For now my internal test code working correctly, but my Kconfig excludes STACK_VALIDATION dependency. It seems that objtool will not be enabled yet, so I would like to test it easier. If you are already testing with this patch, could you tell me how to do it? Thanks, Keiya > > On 1/24/22 23:21, nobuta.keiya@fujitsu.com wrote: > > Hi Madhavan, > > > >> Select HAVE_RELIABLE_STACKTRACE in arm64/Kconfig to allow > >> arch_stack_walk_reliable() to be used. > >> > >> Note that this is conditional upon STACK_VALIDATION which will be > >> added when frame pointer validation is implemented (say via objtool). > > > > I know that Julien Thierry published objtool support for arm64 [1], > > but I'm not sure if it has been updated. Could you tell me other threads if you know? > > > > [1] > > https://lore.kernel.org/linux-arm-kernel/20210303170932.1838634-1-jthi > > erry@redhat.com/ > > > > > > Thanks, > > Keiya > > > >> > >> Signed-off-by: Madhavan T. Venkataraman > >> <madvenka@linux.microsoft.com> > >> --- > >> arch/arm64/Kconfig | 1 + > >> 1 file changed, 1 insertion(+) > >> > >> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index > >> f6e333b59314..bc7b3514b563 100644 > >> --- a/arch/arm64/Kconfig > >> +++ b/arch/arm64/Kconfig > >> @@ -223,6 +223,7 @@ config ARM64 > >> select THREAD_INFO_IN_TASK > >> select HAVE_ARCH_USERFAULTFD_MINOR if USERFAULTFD > >> select TRACE_IRQFLAGS_SUPPORT > >> + select HAVE_RELIABLE_STACKTRACE if FRAME_POINTER && > >> +STACK_VALIDATION > >> help > >> ARM 64-bit (AArch64) Linux support. > >> > >> -- > >> 2.25.1 > > > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "nobuta.keiya@fujitsu.com" <nobuta.keiya@fujitsu.com> To: "'Madhavan T. Venkataraman'" <madvenka@linux.microsoft.com>, "mark.rutland@arm.com" <mark.rutland@arm.com>, "broonie@kernel.org" <broonie@kernel.org>, "jpoimboe@redhat.com" <jpoimboe@redhat.com>, "ardb@kernel.org" <ardb@kernel.org>, "sjitindarsingh@gmail.com" <sjitindarsingh@gmail.com>, "catalin.marinas@arm.com" <catalin.marinas@arm.com>, "will@kernel.org" <will@kernel.org>, "jmorris@namei.org" <jmorris@namei.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "live-patching@vger.kernel.org" <live-patching@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: RE: [PATCH v13 11/11] arm64: Select HAVE_RELIABLE_STACKTRACE Date: Wed, 26 Jan 2022 10:20:16 +0000 [thread overview] Message-ID: <TY2PR01MB5257BE671A481D81F1A40E0185209@TY2PR01MB5257.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <825b8b72-c746-ba24-7142-3fff481e82d6@linux.microsoft.com> > I have not seen any activity on that in a long time. IIRC, Julien quit RedHat. > I don't know if anyone else has taken over this work in RedHat. > > Sorry, I don't have any more information. > > Madhavan Thanks for your information. By the way, I'm considering test code for arch_stack_walk_reliable(). Specifically, I apply Suraj's patch to enable livepatch, and added a function that sleeps between SYM_CODE_START and SYM_CODE_END, then livepatch checks if the task has an unreliable stack. For now my internal test code working correctly, but my Kconfig excludes STACK_VALIDATION dependency. It seems that objtool will not be enabled yet, so I would like to test it easier. If you are already testing with this patch, could you tell me how to do it? Thanks, Keiya > > On 1/24/22 23:21, nobuta.keiya@fujitsu.com wrote: > > Hi Madhavan, > > > >> Select HAVE_RELIABLE_STACKTRACE in arm64/Kconfig to allow > >> arch_stack_walk_reliable() to be used. > >> > >> Note that this is conditional upon STACK_VALIDATION which will be > >> added when frame pointer validation is implemented (say via objtool). > > > > I know that Julien Thierry published objtool support for arm64 [1], > > but I'm not sure if it has been updated. Could you tell me other threads if you know? > > > > [1] > > https://lore.kernel.org/linux-arm-kernel/20210303170932.1838634-1-jthi > > erry@redhat.com/ > > > > > > Thanks, > > Keiya > > > >> > >> Signed-off-by: Madhavan T. Venkataraman > >> <madvenka@linux.microsoft.com> > >> --- > >> arch/arm64/Kconfig | 1 + > >> 1 file changed, 1 insertion(+) > >> > >> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index > >> f6e333b59314..bc7b3514b563 100644 > >> --- a/arch/arm64/Kconfig > >> +++ b/arch/arm64/Kconfig > >> @@ -223,6 +223,7 @@ config ARM64 > >> select THREAD_INFO_IN_TASK > >> select HAVE_ARCH_USERFAULTFD_MINOR if USERFAULTFD > >> select TRACE_IRQFLAGS_SUPPORT > >> + select HAVE_RELIABLE_STACKTRACE if FRAME_POINTER && > >> +STACK_VALIDATION > >> help > >> ARM 64-bit (AArch64) Linux support. > >> > >> -- > >> 2.25.1 > > > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-26 10:20 UTC|newest] Thread overview: 150+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <95691cae4f4504f33d0fc9075541b1e7deefe96f> 2022-01-17 14:55 ` [PATCH v13 00/11] arm64: Reorganize the unwinder and implement stack trace reliability checks madvenka 2022-01-17 14:55 ` madvenka 2022-01-17 14:55 ` [PATCH v13 01/11] arm64: Remove NULL task check from unwind_frame() madvenka 2022-01-17 14:55 ` madvenka 2022-01-17 14:55 ` [PATCH v13 02/11] arm64: Rename unwinder functions madvenka 2022-01-17 14:55 ` madvenka 2022-01-17 14:56 ` [PATCH v13 03/11] arm64: Rename stackframe to unwind_state madvenka 2022-01-17 14:56 ` madvenka 2022-01-17 14:56 ` [PATCH v13 04/11] arm64: Split unwind_init() madvenka 2022-01-17 14:56 ` madvenka 2022-02-02 18:44 ` Mark Brown 2022-02-02 18:44 ` Mark Brown 2022-02-03 0:26 ` Madhavan T. Venkataraman 2022-02-03 0:26 ` Madhavan T. Venkataraman 2022-02-03 0:39 ` Madhavan T. Venkataraman 2022-02-03 0:39 ` Madhavan T. Venkataraman 2022-02-03 11:29 ` Mark Brown 2022-02-03 11:29 ` Mark Brown 2022-02-15 13:07 ` Mark Rutland 2022-02-15 13:07 ` Mark Rutland 2022-02-15 18:04 ` Madhavan T. Venkataraman 2022-02-15 18:04 ` Madhavan T. Venkataraman 2022-01-17 14:56 ` [PATCH v13 05/11] arm64: Copy the task argument to unwind_state madvenka 2022-01-17 14:56 ` madvenka 2022-02-02 18:45 ` Mark Brown 2022-02-02 18:45 ` Mark Brown 2022-02-15 13:22 ` Mark Rutland 2022-02-15 13:22 ` Mark Rutland 2022-02-22 16:53 ` Madhavan T. Venkataraman 2022-02-22 16:53 ` Madhavan T. Venkataraman 2022-01-17 14:56 ` [PATCH v13 06/11] arm64: Use stack_trace_consume_fn and rename args to unwind() madvenka 2022-01-17 14:56 ` madvenka 2022-02-02 18:46 ` Mark Brown 2022-02-02 18:46 ` Mark Brown 2022-02-03 0:34 ` Madhavan T. Venkataraman 2022-02-03 0:34 ` Madhavan T. Venkataraman 2022-02-03 11:30 ` Mark Brown 2022-02-03 11:30 ` Mark Brown 2022-02-03 14:45 ` Madhavan T. Venkataraman 2022-02-03 14:45 ` Madhavan T. Venkataraman 2022-02-15 13:39 ` Mark Rutland 2022-02-15 13:39 ` Mark Rutland 2022-02-15 18:12 ` Madhavan T. Venkataraman 2022-02-15 18:12 ` Madhavan T. Venkataraman 2022-03-07 16:51 ` Madhavan T. Venkataraman 2022-03-07 16:51 ` Madhavan T. Venkataraman 2022-03-07 17:01 ` Mark Brown 2022-03-07 17:01 ` Mark Brown 2022-03-08 22:00 ` Madhavan T. Venkataraman 2022-03-08 22:00 ` Madhavan T. Venkataraman 2022-03-09 11:47 ` Mark Brown 2022-03-09 11:47 ` Mark Brown 2022-03-09 15:34 ` Madhavan T. Venkataraman 2022-03-09 15:34 ` Madhavan T. Venkataraman 2022-03-10 8:33 ` Miroslav Benes 2022-03-10 8:33 ` Miroslav Benes 2022-03-10 12:36 ` Madhavan T. Venkataraman 2022-03-10 12:36 ` Madhavan T. Venkataraman 2022-03-16 3:43 ` Josh Poimboeuf 2022-03-16 3:43 ` Josh Poimboeuf 2022-04-08 14:44 ` Mark Rutland 2022-04-08 14:44 ` Mark Rutland 2022-04-08 17:58 ` Mark Rutland 2022-04-08 17:58 ` Mark Rutland 2022-04-10 17:42 ` Madhavan T. Venkataraman 2022-04-10 17:42 ` Madhavan T. Venkataraman 2022-04-10 17:33 ` Madhavan T. Venkataraman 2022-04-10 17:33 ` Madhavan T. Venkataraman 2022-04-10 17:45 ` Madhavan T. Venkataraman 2022-04-10 17:45 ` Madhavan T. Venkataraman 2022-01-17 14:56 ` [PATCH v13 07/11] arm64: Make the unwind loop in unwind() similar to other architectures madvenka 2022-01-17 14:56 ` madvenka 2022-01-17 14:56 ` [PATCH v13 08/11] arm64: Introduce stack trace reliability checks in the unwinder madvenka 2022-01-17 14:56 ` madvenka 2022-01-17 14:56 ` [PATCH v13 09/11] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka 2022-01-17 14:56 ` madvenka 2022-01-17 14:56 ` [PATCH v13 10/11] arm64: Introduce arch_stack_walk_reliable() madvenka 2022-01-17 14:56 ` madvenka 2022-01-17 14:56 ` [PATCH v13 11/11] arm64: Select HAVE_RELIABLE_STACKTRACE madvenka 2022-01-17 14:56 ` madvenka 2022-01-25 5:21 ` nobuta.keiya 2022-01-25 5:21 ` nobuta.keiya 2022-01-25 13:43 ` Madhavan T. Venkataraman 2022-01-25 13:43 ` Madhavan T. Venkataraman 2022-01-26 10:20 ` nobuta.keiya [this message] 2022-01-26 10:20 ` nobuta.keiya 2022-01-26 17:14 ` Madhavan T. Venkataraman 2022-01-26 17:14 ` Madhavan T. Venkataraman 2022-01-27 1:13 ` nobuta.keiya 2022-01-27 1:13 ` nobuta.keiya 2022-01-26 17:16 ` Mark Brown 2022-01-26 17:16 ` Mark Brown 2022-04-07 20:25 ` [RFC PATCH v1 0/9] arm64: livepatch: Use DWARF Call Frame Information for frame pointer validation madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 1/9] objtool: Parse DWARF Call Frame Information in object files madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 2/9] objtool: Generate DWARF rules and place them in a special section madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 3/9] dwarf: Build the kernel with DWARF information madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 4/9] dwarf: Implement DWARF rule processing in the kernel madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 5/9] dwarf: Implement DWARF support for modules madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 6/9] arm64: unwinder: Add a reliability check in the unwinder based on DWARF CFI madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 7/9] arm64: dwarf: Implement unwind hints madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 8/9] dwarf: Miscellaneous changes required for enabling livepatch madvenka 2022-04-07 20:25 ` madvenka 2022-04-07 20:25 ` [RFC PATCH v1 9/9] dwarf: Enable livepatch for ARM64 madvenka 2022-04-07 20:25 ` madvenka 2022-04-08 0:21 ` [RFC PATCH v1 0/9] arm64: livepatch: Use DWARF Call Frame Information for frame pointer validation Josh Poimboeuf 2022-04-08 0:21 ` Josh Poimboeuf 2022-04-08 11:41 ` Peter Zijlstra 2022-04-08 11:41 ` Peter Zijlstra 2022-04-11 17:26 ` Madhavan T. Venkataraman 2022-04-11 17:26 ` Madhavan T. Venkataraman 2022-04-11 17:18 ` Madhavan T. Venkataraman 2022-04-11 17:18 ` Madhavan T. Venkataraman 2022-04-12 8:32 ` Chen Zhongjin 2022-04-12 8:32 ` Chen Zhongjin 2022-04-16 0:56 ` Josh Poimboeuf 2022-04-16 0:56 ` Josh Poimboeuf 2022-04-18 12:28 ` Chen Zhongjin 2022-04-18 12:28 ` Chen Zhongjin 2022-04-18 16:11 ` Josh Poimboeuf 2022-04-18 16:11 ` Josh Poimboeuf 2022-04-18 18:38 ` Madhavan T. Venkataraman 2022-04-18 18:38 ` Madhavan T. Venkataraman [not found] ` <844b3ede-eddb-cbe6-80e0-3529e2da2eb6@huawei.com> 2022-04-12 17:27 ` Madhavan T. Venkataraman 2022-04-12 17:27 ` Madhavan T. Venkataraman 2022-04-16 1:07 ` Josh Poimboeuf 2022-04-16 1:07 ` Josh Poimboeuf 2022-04-14 14:11 ` Madhavan T. Venkataraman 2022-04-14 14:11 ` Madhavan T. Venkataraman 2022-04-08 10:55 ` Peter Zijlstra 2022-04-08 10:55 ` Peter Zijlstra 2022-04-08 11:54 ` Peter Zijlstra 2022-04-08 11:54 ` Peter Zijlstra 2022-04-08 14:34 ` Josh Poimboeuf 2022-04-08 14:34 ` Josh Poimboeuf 2022-04-10 17:47 ` Madhavan T. Venkataraman 2022-04-10 17:47 ` Madhavan T. Venkataraman 2022-04-11 16:34 ` Josh Poimboeuf 2022-04-11 16:34 ` Josh Poimboeuf 2022-04-08 12:06 ` Peter Zijlstra 2022-04-08 12:06 ` Peter Zijlstra 2022-04-11 17:35 ` Madhavan T. Venkataraman 2022-04-11 17:35 ` Madhavan T. Venkataraman
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=TY2PR01MB5257BE671A481D81F1A40E0185209@TY2PR01MB5257.jpnprd01.prod.outlook.com \ --to=nobuta.keiya@fujitsu.com \ --cc=ardb@kernel.org \ --cc=broonie@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=jmorris@namei.org \ --cc=jpoimboe@redhat.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=live-patching@vger.kernel.org \ --cc=madvenka@linux.microsoft.com \ --cc=mark.rutland@arm.com \ --cc=sjitindarsingh@gmail.com \ --cc=will@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.