[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230620180839.oodfav5cz234pph7@moria.home.lan>
Date: Tue, 20 Jun 2023 14:08:39 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Andy Lutomirski <luto@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel@...r.kernel.org,
"linux-bcachefs@...r.kernel.org" <linux-bcachefs@...r.kernel.org>,
Kent Overstreet <kent.overstreet@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Uladzislau Rezki <urezki@...il.com>,
"hch@...radead.org" <hch@...radead.org>, linux-mm@...ck.org,
Kees Cook <keescook@...omium.org>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH 07/32] mm: Bring back vmalloc_exec
On Tue, Jun 20, 2023 at 10:42:02AM -0700, Andy Lutomirski wrote:
> Code is either correct, and comes with an explanation as to how it is
> correct, or it doesn't go in. Saying that something is like BPF is
> not an explanation as to how it's correct. Saying that someone has
> not come up with the chain of events that causes a mere violation of
> architecture rules to actual incorrect execution is not an explanation
> as to how something is correct.
No, I'm saying your concerns are baseless and too vague to address.
> text_poke() by itself is *not* the proper API, as discussed. It
> doesn't serialize adequately, even on x86. We have text_poke_sync()
> for that.
Andy, I replied explaining the difference between text_poke() and
text_poke_sync(). It's clear you have no idea what you're talking about,
so I'm not going to be wasting my time on further communications with
you.
Powered by blists - more mailing lists