[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.2104080957580.18270@cbobk.fhfr.pm>
Date: Thu, 8 Apr 2021 10:01:23 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
cc: Thomas Gleixner <tglx@...utronix.de>,
Luis Chamberlain <mcgrof@...nel.org>,
Minchan Kim <minchan@...nel.org>, keescook@...omium.org,
dhowells@...hat.com, hch@...radead.org, mbenes@...e.com,
ngupta@...are.org, sergey.senozhatsky.work@...il.com,
axboe@...nel.dk, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, Jiri Kosina <jikos@...os.cz>
Subject: Re: [PATCH 1/2] zram: fix crashes due to use of cpu hotplug
multistate
On Thu, 8 Apr 2021, Greg KH wrote:
> Removing a module from a system has always been "let's try it and see!"
> type of operation for a very long time.
Which part of it?
If there is a driver/subsystem code that can't handle the reverse
operation to modprobe, it clearly can't handle error handling during
modprobe (which, one would hope, is supported), and should be fixed.
If there is a particular issue in kernel dynamic linker that causes crash
on module removal, we'd better off fixing it. Is there one such that makes
you claim module removal unsupported?
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists