Re: [PATCH 16/33] riscv/shstk: If needed allocate a new shadow stack on clone

2024-10-07 Thread Zong Li
On Tue, Oct 8, 2024 at 1:31 PM Deepak Gupta wrote: > > On Tue, Oct 08, 2024 at 01:16:17PM +0800, Zong Li wrote: > >On Tue, Oct 8, 2024 at 7:30 AM Deepak Gupta wrote: > >> > >> On Mon, Oct 07, 2024 at 04:17:47PM +0800, Zong Li wrote: > >> >On Wed, Oct 2, 2024 at 12:20 AM Deepak Gupta wrote: > >>

Re: [PATCH 16/33] riscv/shstk: If needed allocate a new shadow stack on clone

2024-10-07 Thread Deepak Gupta
On Tue, Oct 08, 2024 at 01:16:17PM +0800, Zong Li wrote: On Tue, Oct 8, 2024 at 7:30 AM Deepak Gupta wrote: On Mon, Oct 07, 2024 at 04:17:47PM +0800, Zong Li wrote: >On Wed, Oct 2, 2024 at 12:20 AM Deepak Gupta wrote: >> >> Userspace specifies CLONE_VM to share address space and spawn new thr

Re: [PATCH 16/33] riscv/shstk: If needed allocate a new shadow stack on clone

2024-10-07 Thread Zong Li
On Tue, Oct 8, 2024 at 7:30 AM Deepak Gupta wrote: > > On Mon, Oct 07, 2024 at 04:17:47PM +0800, Zong Li wrote: > >On Wed, Oct 2, 2024 at 12:20 AM Deepak Gupta wrote: > >> > >> Userspace specifies CLONE_VM to share address space and spawn new thread. > >> `clone` allow userspace to specify a new

Re: [PATCH 16/33] riscv/shstk: If needed allocate a new shadow stack on clone

2024-10-07 Thread Deepak Gupta
On Mon, Oct 07, 2024 at 04:17:47PM +0800, Zong Li wrote: On Wed, Oct 2, 2024 at 12:20 AM Deepak Gupta wrote: Userspace specifies CLONE_VM to share address space and spawn new thread. `clone` allow userspace to specify a new stack for new thread. However there is no way to specify new shadow st

Re: [PATCH v2 1/6] Add AutoFDO support for Clang build

2024-10-07 Thread Rong Xu
On Mon, Oct 7, 2024 at 11:33 AM Miguel Ojeda wrote: > > On Mon, Oct 7, 2024 at 8:04 PM Rong Xu wrote: > > > > I removed the "code-block" directives from the rst files, > > and used "::" suggested by Jonathan. The rst files themselves are now > > I think it was Mike. Sorry for mixing up the names

Re: [PATCH v2 1/6] Add AutoFDO support for Clang build

2024-10-07 Thread Miguel Ojeda
On Mon, Oct 7, 2024 at 8:04 PM Rong Xu wrote: > > I removed the "code-block" directives from the rst files, > and used "::" suggested by Jonathan. The rst files themselves are now I think it was Mike. > (1) The text that was previously in code-block no longer indents. It aligns > with the

Re: [PATCH v2 1/6] Add AutoFDO support for Clang build

2024-10-07 Thread Rong Xu
I removed the "code-block" directives from the rst files, and used "::" suggested by Jonathan. The rst files themselves are now easier to read in vi. However, the rendered HTML output has some differences: (1) The text that was previously in code-block no longer indents. It aligns with the p

Re: [PATCH v3] kernel-docs: Add new section for Rust learning materials

2024-10-07 Thread Jonathan Corbet
Carlos Bilbao writes: > Include a new section in the Index of Further Kernel Documentation with > resources to learn Rust. Reference it in the Rust index. The resources > are a product of a survey among assistants to the conference Kangrejos'24. > > Signed-off-by: Carlos Bilbao > Reviewed-by: Di

Re: [PATCH v2] Documentation/process: maintainer-soc: clarify submitting patches

2024-10-07 Thread Jonathan Corbet
Krzysztof Kozlowski writes: > Patches for SoCs are expected to be picked up by SoC submaintainers. > The main SoC maintainers should be addressed only in few cases. > > Rewrite the section about maintainer handling to document above > expectation. > > Signed-off-by: Krzysztof Kozlowski > Cc: Lin

Re: [PATCH doc] docs: gcov: fix link to LCOV website

2024-10-07 Thread Jonathan Corbet
"Matthieu Baerts (NGI0)" writes: > The previous website hosted on SourceForge is no longer available since > January 2024 according to archive.org [1]. > > It looks like the website has been officially moved to GitHub in June > 2022 [2]. Best to redirect readers to the new location then. > > Link

Re: [PATCH] docs: backporting: fix a typo

2024-10-07 Thread Jonathan Corbet
Andrew Kreimer writes: > Fix a typo in documentation. > > Signed-off-by: Andrew Kreimer > --- > Documentation/process/backporting.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/process/backporting.rst > b/Documentation/process/backporting.rst > index

Re: [PATCH RFC net] docs: netdev: document guidance on cleanup patches

2024-10-07 Thread Jakub Kicinski
On Mon, 7 Oct 2024 17:15:01 +0100 Simon Horman wrote: > > > We could merge or otherwise rearrange that section with the one proposed > > > by > > > this patch. But I didn't feel it was necessary last week. > > > > Somewhat, we don't push back on correct use of device-managed APIs. > > But conve

Re: [PATCH RFC net] docs: netdev: document guidance on cleanup patches

2024-10-07 Thread Simon Horman
On Mon, Oct 07, 2024 at 09:08:28AM -0700, Jakub Kicinski wrote: > On Mon, 7 Oct 2024 16:55:21 +0100 Simon Horman wrote: > > > > +Netdev discourages patches which perform simple clean-ups, which are > > > > not in > > > > +the context of other work. For example addressing ``checkpatch.pl`` > > > >

Re: [PATCH RFC net] docs: netdev: document guidance on cleanup patches

2024-10-07 Thread Jakub Kicinski
On Mon, 7 Oct 2024 16:55:21 +0100 Simon Horman wrote: > > > +Netdev discourages patches which perform simple clean-ups, which are not > > > in > > > +the context of other work. For example addressing ``checkpatch.pl`` > > > +warnings, or :ref:`local variable ordering` issues. This is because > >

Re: [PATCH RFC net] docs: netdev: document guidance on cleanup patches

2024-10-07 Thread Simon Horman
On Mon, Oct 07, 2024 at 08:24:30AM -0700, Jakub Kicinski wrote: > On Fri, 04 Oct 2024 10:49:53 +0100 Simon Horman wrote: > > The purpose of this section is to document what is the current practice > > regarding clean-up patches which address checkpatch warnings and similar > > problems. I feel ther

Re: [PATCH RFC net] docs: netdev: document guidance on cleanup patches

2024-10-07 Thread Jakub Kicinski
On Fri, 04 Oct 2024 10:49:53 +0100 Simon Horman wrote: > The purpose of this section is to document what is the current practice > regarding clean-up patches which address checkpatch warnings and similar > problems. I feel there is a value in having this documented so others > can easily refer to i

Re: [RFC PATCH v2 4/4] sched+mm: Use hazard pointers to track lazy active mm existence

2024-10-07 Thread Mathieu Desnoyers
kernel config and materials to reproduce are available at: https://download.01.org/0day-ci/archive/20241007/202410072229.18756716-oliver.s...@intel.com -- Mathieu Desnoyers EfficiOS Inc. https://www.efficios.com

Re: [RFC PATCH v2 4/4] sched+mm: Use hazard pointers to track lazy active mm existence

2024-10-07 Thread kernel test robot
x86/entry/entry_32.S:944) The kernel config and materials to reproduce are available at: https://download.01.org/0day-ci/archive/20241007/202410072229.18756716-oliver.s...@intel.com -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

Re: [PATCH 16/33] riscv/shstk: If needed allocate a new shadow stack on clone

2024-10-07 Thread Zong Li
On Wed, Oct 2, 2024 at 12:20 AM Deepak Gupta wrote: > > Userspace specifies CLONE_VM to share address space and spawn new thread. > `clone` allow userspace to specify a new stack for new thread. However > there is no way to specify new shadow stack base address without changing > API. This patch a