linux-kernel - Re: [PATCH v26 00/28] riscv control-flow integrity for usermode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKC1njQ-hS+kUJ0C_v0oqZW1EZw2zAXMp-SnnA-ZXh_H-SoVdQ@mail.gmail.com>
Date: Thu, 8 Jan 2026 07:10:32 -0800
From: Deepak Gupta <debug@...osinc.com>
To: Paul Walmsley <pjw@...nel.org>
Cc: x86@...nel.org, Paul Walmsley <paul.walmsley@...ive.com>, 
	Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>, 
	Conor Dooley <conor@...nel.org>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>, 
	Christian Brauner <brauner@...nel.org>, Peter Zijlstra <peterz@...radead.org>, 
	Oleg Nesterov <oleg@...hat.com>, Eric Biederman <ebiederm@...ssion.com>, Kees Cook <kees@...nel.org>, 
	Jonathan Corbet <corbet@....net>, Shuah Khan <shuah@...nel.org>, Jann Horn <jannh@...gle.com>, 
	Conor Dooley <conor+dt@...nel.org>, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>, 
	Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, 
	Trevor Gross <tmgross@...ch.edu>, Benno Lossin <lossin@...nel.org>, linux-kernel@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, linux-mm@...ck.org, 
	linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org, 
	linux-arch@...r.kernel.org, linux-doc@...r.kernel.org, 
	linux-kselftest@...r.kernel.org, alistair.francis@....com, 
	richard.henderson@...aro.org, jim.shu@...ive.com, 
	Andy Chiu <andybnac@...il.com>, kito.cheng@...ive.com, charlie@...osinc.com, 
	atishp@...osinc.com, evan@...osinc.com, cleger@...osinc.com, 
	alexghiti@...osinc.com, samitolvanen@...gle.com, broonie@...nel.org, 
	rick.p.edgecombe@...el.com, rust-for-linux@...r.kernel.org, 
	Zong Li <zong.li@...ive.com>, Andreas Korb <andreas.korb@...ec.fraunhofer.de>, 
	Valentin Haudiquet <valentin.haudiquet@...onical.com>, Charles Mirabile <cmirabil@...hat.com>, 
	Jesse Huang <jesse.huang@...ive.com>
Subject: Re: [PATCH v26 00/28] riscv control-flow integrity for usermode

Hi Paul,

I have a bugfix for a bug reported by Jesse Huang (thanks Jesse) in riscv
implementation of `map_shadow_stack`.

Should I send a new series or only the bugfix-patch for implementation
of `map_shadow_stack`

Let me know. Thanks.

-Deepak

-Deepak



On Fri, Dec 12, 2025 at 10:33 AM Deepak Gupta <debug@...osinc.com> wrote:
>
> On Fri, Dec 12, 2025 at 01:30:29AM -0700, Paul Walmsley wrote:
> >On Thu, 11 Dec 2025, Deepak Gupta via B4 Relay wrote:
> >
> >> v26: CONFIG_RISCV_USER_CFI depends on CONFIG_MMU (dependency of shadow stack
> >> on MMU). Used b4 to pick tags, apparantly it messed up some tag picks. Fixing it
> >
> >Deepak: I'm now (at least) the third person to tell you to stop resending
> >this entire series over and over again.
>
> To be very honest I also feel very bad doing and DOSing the lists. Sorry to you
> and everyone else.
>
> But I have been sitting on this patch series for last 3-4 merge windows with
> patches being exactly same/similar. So I have been a little more than desperate
> to get it in.
>
> I really haven't had any meaningful feedback on patch series except stalling
> just before each merge window for reasons which really shouldn't stall its
> merge. Sure that's the nature of open source development and it's maintainer's
> call at the end of the day. And I am new to this. I'll improve.
>
> >
> >First, a modified version of the CFI v23 series was ALREADY SITTING IN
> >LINUX-NEXT.  So there's no reason you should be resending the entire
> >series, UNLESS your intention for me is to drop the entire existing series
> >and wait for another merge window.
> >
> >Second: when someone asks you questions about an individual patch, and you
> >want to answer those questions, it's NOT GOOD for you to resend the entire
> >28 series as the response!  You are DDOSing a bunch of lists and E-mail
> >inboxes.  Just answer the question in a single E-mail.  If you want to
> >update a single patch, just send that one patch.
>
> Noted. I wasn't sure about it. I'll explicitly ask next time if you want me to
> send another one.
>
> >
> >If you don't start paying attention to these rules then people are going
> >to start ignoring you -- at best! -- and it's going to give the entire
> >community a bad reputation.
>
> Even before this, this patch series has been ignored largely. I don't know
> how to get attention. All I wanted was either feedback or get it in. And as I
> said I've been desparate to get it in. Also as I said, I'll improve.
>
> >
> >Please acknowledge that you understand this,
>
> ACKed.
>
> >
> >
> >- Paul