From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Miroslav Benes <mbenes@suse.cz>,
Greg KH <gregkh@linuxfoundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
mbenes@suse.com, Minchan Kim <minchan@kernel.org>,
keescook@chromium.org, dhowells@redhat.com, hch@infradead.org,
ngupta@vflare.org, sergey.senozhatsky.work@gmail.com,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
Jessica Yu <jeyu@kernel.org>
Subject: Re: [PATCH 1/2] zram: fix crashes due to use of cpu hotplug multistate
Date: Wed, 7 Apr 2021 16:09:44 +0200 [thread overview]
Message-ID: <YG29KAuOHbJd3Bll@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210406155423.t7dagp24bupudv3p@treble>
On Tue, Apr 06, 2021 at 10:54:23AM -0500, Josh Poimboeuf wrote:
> Same for Red Hat. Unloading livepatch modules seems to work fine, but
> isn't officially supported.
>
> That said, if rmmod is just considered a development aid, and we're
> going to be ignoring bugs, we should make it official with a new
> TAINT_RMMOD.
Another option would be to have live-patch modules leak a module
reference by default, except when some debug sysctl is set or something.
Then only those LP modules loaded while the sysctl is set to 'YOLO' can
be unloaded.
next prev parent reply other threads:[~2021-04-07 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210312183238.GW4332@42.do-not-panic.com>
[not found] ` <YEvA1dzDsFOuKdZ/@google.com>
[not found] ` <20210319190924.GK4332@42.do-not-panic.com>
[not found] ` <YFjHvUolScp3btJ9@google.com>
[not found] ` <20210322204156.GM4332@42.do-not-panic.com>
[not found] ` <YFkWMZ0m9nKCT69T@google.com>
[not found] ` <20210401235925.GR4332@42.do-not-panic.com>
[not found] ` <YGbNpLKXfWpy0ZZa@kroah.com>
[not found] ` <20210402183016.GU4332@42.do-not-panic.com>
[not found] ` <YGgHg7XCHD3rATIK@kroah.com>
[not found] ` <20210406003152.GZ4332@42.do-not-panic.com>
2021-04-06 12:00 ` [PATCH 1/2] zram: fix crashes due to use of cpu hotplug multistate Miroslav Benes
2021-04-06 15:54 ` Josh Poimboeuf
2021-04-07 14:09 ` Peter Zijlstra [this message]
2021-04-07 15:30 ` Josh Poimboeuf
2021-04-07 16:48 ` Peter Zijlstra
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=YG29KAuOHbJd3Bll@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=axboe@kernel.dk \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jeyu@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.com \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.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;
as well as URLs for NNTP newsgroup(s).