From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, ngupta@vflare.org,
minchan@kernel.org, senozhatsky@chromium.org,
akpm@linux-foundation.org
Subject: [folded-merged] zram-do-not-lookup-algorithm-in-backends-table-v2.patch removed from -mm tree
Date: Sun, 03 Jul 2022 17:04:22 -0700 [thread overview]
Message-ID: <20220704000423.781ACC341C6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: zram: do not lookup algorithm in backends table
has been removed from the -mm tree. Its filename was
zram-do-not-lookup-algorithm-in-backends-table-v2.patch
This patch was dropped because it was folded into zram-do-not-lookup-algorithm-in-backends-table.patch
------------------------------------------------------
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: zram: do not lookup algorithm in backends table
Date: Fri, 24 Jun 2022 15:06:06 +0900
add comment
Link: https://lkml.kernel.org/r/20220624060606.1014474-1-senozhatsky@chromium.org
Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Nitin Gupta <ngupta@vflare.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/block/zram/zcomp.c | 5 +++++
1 file changed, 5 insertions(+)
--- a/drivers/block/zram/zcomp.c~zram-do-not-lookup-algorithm-in-backends-table-v2
+++ a/drivers/block/zram/zcomp.c
@@ -211,6 +211,11 @@ struct zcomp *zcomp_create(const char *c
struct zcomp *comp;
int error;
+ /*
+ * Crypto API will execute /sbin/modprobe if the compression module
+ * is not loaded yet. We must do it here, otherwise we are about to
+ * call /sbin/modprobe under CPU hot-plug lock.
+ */
if (!zcomp_available_algorithm(compress))
return ERR_PTR(-EINVAL);
_
Patches currently in -mm which might be from senozhatsky@chromium.org are
zram-do-not-lookup-algorithm-in-backends-table.patch
reply other threads:[~2022-07-04 0:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220704000423.781ACC341C6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.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.