Live Patching
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	corbet@lwn.net, skhan@linuxfoundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, gregkh@linuxfoundation.org,
	akinobu.mita@gmail.com, live-patching@vger.kernel.org
Subject: Re: [PATCH] killswitch: add per-function short-circuit mitigation primitive
Date: Thu, 14 May 2026 16:35:15 +0200	[thread overview]
Message-ID: <agXdowd63K8j43xi@krava> (raw)
In-Reply-To: <agIbaeBQAr-RkqYc@laps>

On Mon, May 11, 2026 at 02:09:45PM -0400, Sasha Levin wrote:

SNIP

> > > Even if I'm okay with rebooting that often (and I really really would prefer
> > > not to), this doesn't solve the issues of a larger fleet of servers that can't
> > > just reboot that often.
> > > 
> > > What am I missing?
> > 
> > For one, you are missing more maintainers of code modification infrastructures.
> 
> Happy to add more, but I don't want to be too spammy. I'll add in the
> livepatching ML and the fault injection maintainer (I couldn't find a list).
> Please add any other folks/lists who you think might want to contribute to this
> discussion.

hi,
could you please add bpf (bpf@vger.kernel.org) to the loop?

thanks,
jirka

      reply	other threads:[~2026-05-14 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <agG_PZ3qcl6TwLnL@gmail.com>
     [not found] ` <agHUp8ulaWJ75WU5@tiehlicka>
     [not found]   ` <agHcFCRVSn5ra5Kc@laps>
     [not found]     ` <agHeZPA3eHhJHIsQ@tiehlicka>
     [not found]       ` <agHgDgwu8H9Opzpl@laps>
     [not found]         ` <agHm9Vj7bPPCRS1g@tiehlicka>
     [not found]           ` <agH7_QBPLWKTZucB@laps>
     [not found]             ` <agH_bGUTvWm2h5g4@tiehlicka>
     [not found]               ` <agIHsN9tiIHnVTeV@laps>
     [not found]                 ` <agINlnNN4ubZgyiN@tiehlicka>
2026-05-11 18:09                   ` [PATCH] killswitch: add per-function short-circuit mitigation primitive Sasha Levin
2026-05-14 14:35                     ` Jiri Olsa [this message]

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=agXdowd63K8j43xi@krava \
    --to=olsajiri@gmail.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --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=mhocko@suse.com \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.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