All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Brandon Taylor <bt610490@yahoo.com>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
	live-patching@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Joshua Peisach <jpeisach@ubuntu.com>,
	Florian Weimer <fw@deneb.enyo.de>,
	Breno Leitao <leitao@debian.org>,
	Anthony Iliopoulos <ailiop@suse.com>,
	Michal Hocko <mhocko@suse.com>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH v3] killswitch: add per-function short-circuit mitigation primitive
Date: Mon, 18 May 2026 07:23:11 +0200	[thread overview]
Message-ID: <2026051854-emphases-cascade-29ee@gregkh> (raw)
In-Reply-To: <e4527b42-f2e6-447a-861d-580a521bde19@yahoo.com>

On Sun, May 17, 2026 at 02:19:35PM -0500, Brandon Taylor wrote:
> Have we learned NOTHING from just over 9 and a half years ago?!
> 
> I do not pretend to be a prophet of Linus, but I cannot for the life of me
> help but get flashbacks from kernel version 4.8 when Linus himself did not
> explain, but EXPLODED, in saying "there is NO F*CKING EXCUSE to knowingly
> kill the kernel."

That's not what this patchset does, sorry.

best of luck!

greg k-h

  reply	other threads:[~2026-05-18  5:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 19:57 [PATCH v2] killswitch: add per-function short-circuit mitigation primitive Sasha Levin
2026-05-09 12:02 ` Florian Weimer
2026-05-09 12:34   ` Sasha Levin
2026-05-11 10:33     ` Anthony Iliopoulos
2026-05-11 11:15       ` Sasha Levin
2026-05-11 17:23         ` Anthony Iliopoulos
2026-05-11 20:12           ` Sasha Levin
2026-05-11 13:14 ` Breno Leitao
2026-05-11 13:41   ` Sasha Levin
2026-05-11 14:59     ` Breno Leitao
2026-05-17 13:48 ` [PATCH v3] " Sasha Levin
2026-05-17 14:17   ` sashiko-bot
2026-05-17 19:19   ` Brandon Taylor
2026-05-18  5:23     ` Greg Kroah-Hartman [this message]
2026-05-18  6:37   ` Song Liu
2026-05-18 13:33     ` Sasha Levin
2026-05-18 23:59       ` Song Liu
2026-05-19  0:22         ` Sasha Levin
2026-05-19 12:13         ` Daniel Borkmann
2026-05-19 19:57           ` Sasha Levin
2026-05-19 22:00             ` Song Liu
2026-05-21 14:38               ` Sasha Levin
2026-05-21 18:02                 ` Song Liu
2026-05-21  9:11             ` Daniel Borkmann
2026-05-21 15:31               ` Sasha Levin
2026-05-21 18:16                 ` Song Liu
2026-05-23 13:41                   ` Sasha Levin
2026-05-26 13:10                     ` Daniel Borkmann
2026-05-26 14:29                       ` Sasha Levin
2026-06-04 21:18       ` Justin Suess
2026-05-18 23:52   ` Song Liu

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=2026051854-emphases-cascade-29ee@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ailiop@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=bt610490@yahoo.com \
    --cc=corbet@lwn.net \
    --cc=fw@deneb.enyo.de \
    --cc=jolsa@kernel.org \
    --cc=jpeisach@ubuntu.com \
    --cc=leitao@debian.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhocko@suse.com \
    --cc=sashal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.