From: Miroslav Benes <mbenes@suse.cz>
To: Donald Buczek <buczek@molgen.mpg.de>
Cc: Solar Designer <solar@openwall.com>,
oss-security@lists.openwall.com,
Vegard Nossum <vegard.nossum@oracle.com>,
Jiri Kosina <jkosina@suse.cz>,
ksummit@lists.linux.dev
Subject: Re: Re: [MAINTAINERS SUMMIT] Handling of embargoed security issues -- security@korg vs. linux-distros@
Date: Tue, 29 Aug 2023 10:46:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.2308291043590.21665@pobox.suse.cz> (raw)
In-Reply-To: <12aa367f-9934-7450-1016-fe303c72cc5a@molgen.mpg.de>
[ apologies for a slight off topic ]
Hi,
On Fri, 25 Aug 2023, Donald Buczek wrote:
> We go a long way to avoid rebooting. This might be as easy as disabling
> unused dynamic modules by just removing the .ko files from userspace,
> but sometimes we even convert an upstream fix into a loadable module
> which uses ftrace to replace or wrap the buggy functions in the running
> systems. A "reboot party" would only be a measure of last resort.
the kernel live patching infrastructure might help you with this. See
Documentation/livepatch/ and samples/livepatch/ in the kernel tree.
Regards,
Miroslav
prev parent reply other threads:[~2023-08-29 8:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 9:28 Jiri Kosina
2023-08-15 10:17 ` Vegard Nossum
2023-08-15 10:34 ` Jiri Kosina
2023-08-15 11:23 ` Greg KH
2023-08-15 12:42 ` Steven Rostedt
2023-08-15 13:17 ` Daniel Borkmann
2023-08-15 14:19 ` Laurent Pinchart
2023-08-15 22:04 ` Jiri Kosina
2023-08-15 14:20 ` Catalin Marinas
2023-08-15 14:41 ` Greg KH
2023-08-15 15:04 ` Steven Rostedt
2023-08-15 15:51 ` Greg KH
2023-08-15 15:08 ` Greg KH
2023-08-15 18:46 ` Konrad Rzeszutek Wilk
2023-08-15 19:41 ` Greg KH
2023-08-15 22:13 ` Jiri Kosina
2023-08-15 22:31 ` Steven Rostedt
2023-08-16 14:55 ` Greg KH
2024-02-16 17:14 ` Michal Suchánek
2024-02-16 17:34 ` Greg KH
2024-02-16 18:13 ` Michal Suchánek
2024-02-16 18:16 ` Jiri Kosina
2023-08-15 22:17 ` Jiri Kosina
2023-08-16 14:57 ` Greg KH
2023-08-16 17:22 ` Jiri Kosina
2023-08-16 18:38 ` Vegard Nossum
2023-08-16 15:26 ` Solar Designer
2023-08-25 11:17 ` Donald Buczek
2023-08-29 8:46 ` Miroslav Benes [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=alpine.LSU.2.21.2308291043590.21665@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=buczek@molgen.mpg.de \
--cc=jkosina@suse.cz \
--cc=ksummit@lists.linux.dev \
--cc=oss-security@lists.openwall.com \
--cc=solar@openwall.com \
--cc=vegard.nossum@oracle.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