From: Andrew Morton <akpm@linux-foundation.org>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v3 0/3] x86/mm: LAM fixups and cleanups
Date: Tue, 2 Jul 2024 10:36:28 -0700 [thread overview]
Message-ID: <20240702103628.61879ef17b9b01305515c634@linux-foundation.org> (raw)
In-Reply-To: <20240702132139.3332013-1-yosryahmed@google.com>
On Tue, 2 Jul 2024 13:21:36 +0000 Yosry Ahmed <yosryahmed@google.com> wrote:
> This series has fixups and cleanups for LAM. Most importantly, patch 1
> fixes a sycnhronization issue that may cause crashes of userspace
> applications. This is a resend of v3, rebased on top of v6.10-rc6.
"Crashes of userspace applications" is bad. Yet the patchset has been
floating about for four months.
It's unclear (to me) how serious this is. Can you please explain how
common this is, what the userspace application needs to do to trigger
this, etc?
next prev parent reply other threads:[~2024-07-02 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 13:21 Yosry Ahmed
2024-07-02 13:21 ` [RESEND PATCH v3 1/3] x86/mm: Use IPIs to synchronize LAM enablement Yosry Ahmed
2024-07-02 18:58 ` Borislav Petkov
2024-07-02 19:00 ` Yosry Ahmed
2024-07-02 13:21 ` [RESEND PATCH v3 2/3] x86/mm: Fix LAM inconsistency during context switch Yosry Ahmed
2024-07-02 13:21 ` [RESEND PATCH v3 3/3] x86/mm: Cleanup prctl_enable_tagged_addr() nr_bits error checking Yosry Ahmed
2024-07-02 17:36 ` Andrew Morton [this message]
2024-07-02 17:39 ` [RESEND PATCH v3 0/3] x86/mm: LAM fixups and cleanups Yosry Ahmed
2024-07-02 18:35 ` Andrew Morton
2024-07-02 18:38 ` Dave Hansen
2024-07-02 18:55 ` Yosry Ahmed
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=20240702103628.61879ef17b9b01305515c634@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yosryahmed@google.com \
/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