mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: tglx@linutronix.de
Cc: dave.hansen@linux.intel.com,
	"Paul E. McKenney" <paulmck@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Stephen Röttger" <sroettger@google.com>,
	peterz@infradead.org, boqun.feng@gmail.com, hpa@zytor.com,
	aruna.ramakrishna@oracle.com, elver@google.com,
	"Dave Hansen" <dave.hansen@intel.com>,
	"Dmitry Vyukov" <dvyukov@google.com>,
	"Ingo Molnar" <mingo@kernel.org>,
	x86@kernel.org, mingo@redhat.com, bp@alien8.de
Subject: Re: [PATCH v7 3/4] rseq: Make rseq work with protection keys
Date: Mon, 22 Sep 2025 09:06:21 -0400	[thread overview]
Message-ID: <00b90f80-5ad7-4d5e-aef7-a81d88aa76d3@efficios.com> (raw)
In-Reply-To: <CACT4Y+YQdjRyrQ_=sR4chrh1J5yRykXf-ck2ygNB9rzpAiyF4Q@mail.gmail.com>

On 2025-09-19 09:07, Dmitry Vyukov wrote:
> On Thu, 21 Aug 2025 at 17:12, Dmitry Vyukov <dvyukov@google.com> wrote:
>>
>> On Mon, 21 Jul 2025 at 10:41, Dave Hansen <dave.hansen@intel.com> wrote:
>>>
>>> On 7/21/25 06:25, Mathieu Desnoyers wrote:
>>>> This series looks OK from my perspective. I think the last piece that
>>>> was missing was to get a review from Dave Hansen.
>>>>
>>>> Dave ?
>>>
>>> It looks fine to me. I think the best thing is if you folks send it in
>>> as an rseq fix. I'm OK with the x86 bits. For the series:
>>>
>>> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
>>
>> Ingo,
>>
>> Now both Mathieu and Dave reviewed this series.
>>
>> Can you please take it to your tree? Or suggest who can take it?
>>
>> Thanks
> 
> Ingo, Borislav (not sure who else maintaining tip tree),
> 
> Please merge this change into the tip tree.

Hi Thomas,

This series from Dmitry is at v7:

https://lore.kernel.org/lkml/cover.1747817128.git.dvyukov@google.com/

The initial version from February 2025 can be found here:

https://lore.kernel.org/lkml/ffd123bb0c73df5cdd3a5807b360bd390983150b.1739790300.git.dvyukov@google.com/

What are the next steps to get it upstream ? We have not heard back
from the tip tree maintainers since June 2025 after repeated pings
from Dmitry.

Note: it will likely conflict with your rseq rework.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

  reply	other threads:[~2025-09-22 13:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21  8:47 [PATCH v7 0/4] " Dmitry Vyukov
2025-05-21  8:47 ` [PATCH v7 1/4] pkeys: add API to switch to permissive/zero pkey register Dmitry Vyukov
2025-05-21  8:47 ` [PATCH v7 2/4] x86/signal: Use write_permissive_pkey_val() helper Dmitry Vyukov
2025-05-21  8:47 ` [PATCH v7 3/4] rseq: Make rseq work with protection keys Dmitry Vyukov
2025-05-21  8:59   ` Dmitry Vyukov
2025-06-24  9:17     ` Dmitry Vyukov
2025-07-18  9:01       ` Dmitry Vyukov
2025-07-21 13:25         ` Mathieu Desnoyers
2025-07-21 17:41           ` Dave Hansen
2025-08-21 15:12             ` Dmitry Vyukov
2025-09-19 13:07               ` Dmitry Vyukov
2025-09-22 13:06                 ` Mathieu Desnoyers [this message]
2025-10-20 13:46   ` Kevin Brodsky
2025-11-26  0:45     ` Thomas Gleixner
2025-11-26  9:32       ` Florian Weimer
2025-11-26 17:56         ` Thomas Gleixner
2025-11-26 19:06           ` Florian Weimer
2025-11-26 20:52             ` Thomas Gleixner
2025-11-26 22:06               ` Florian Weimer
2025-11-27 14:38                 ` Thomas Gleixner
2025-12-02 19:19           ` Kevin Brodsky
2025-05-21  8:47 ` [PATCH v7 4/4] selftests/rseq: Add test for rseq+pkeys Dmitry Vyukov

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=00b90f80-5ad7-4d5e-aef7-a81d88aa76d3@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=aruna.ramakrishna@oracle.com \
    --cc=boqun.feng@gmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sroettger@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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: 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

all inboxes | Powered by JetHome®