From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, suleiman@google.com,
ngupta@vflare.org, minchan@kernel.org,
keescook+coverity-bot@chromium.org, keescook@chromium.org,
senozhatsky@chromium.org, akpm@linux-foundation.org
Subject: [obsolete] zram-introduce-recompress-sysfs-knob-fix-2.patch removed from -mm tree
Date: Tue, 15 Nov 2022 15:07:41 -0800 [thread overview]
Message-ID: <20221115230741.E006FC433B5@smtp.kernel.org> (raw)
The quilt patch titled
Subject: zram: explicitly limit prio_max for static analyzers
has been removed from the -mm tree. Its filename was
zram-introduce-recompress-sysfs-knob-fix-2.patch
This patch was dropped because it is obsolete
------------------------------------------------------
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: zram: explicitly limit prio_max for static analyzers
Date: Mon, 14 Nov 2022 11:14:20 +0900
coverity (got confused by the code, so this simply is supposed to help
coverity figure out that we never do an out of bounds access in comps[]
array: https://lore.kernel.org/lkml/202211100847.388C61B3@keescook/
Link: https://lkml.kernel.org/r/20221114021420.4060601-1-senozhatsky@chromium.org
Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Nitin Gupta <ngupta@vflare.org>
Cc: Suleiman Souhlal <suleiman@google.com>
Cc: Kees Cook <keescook@chromium.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/block/zram/zram_drv.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/block/zram/zram_drv.c~zram-introduce-recompress-sysfs-knob-fix-2
+++ a/drivers/block/zram/zram_drv.c
@@ -1689,6 +1689,7 @@ static int zram_recompress(struct zram *
* Iterate the secondary comp algorithms list (in order of priority)
* and try to recompress the page.
*/
+ prio_max = min(prio_max, ZRAM_MAX_COMPS);
for (; prio < prio_max; prio++) {
if (!zram->comps[prio])
continue;
_
Patches currently in -mm which might be from senozhatsky@chromium.org are
zram-preparation-for-multi-zcomp-support.patch
zram-add-recompression-algorithm-sysfs-knob.patch
zram-factor-out-wb-and-non-wb-zram-read-functions.patch
zram-introduce-recompress-sysfs-knob.patch
zram-introduce-recompress-sysfs-knob-fix.patch
zram-add-recompress-flag-to-read_block_state.patch
zram-clarify-writeback_store-comment.patch
zram-use-is_err_value-to-check-for-zs_malloc-errors.patch
zram-remove-redundant-checks-from-zram_recompress.patch
zram-add-algo-parameter-support-to-zram_recompress.patch
documentation-add-zram-recompression-documentation.patch
zram-add-incompressible-writeback.patch
zram-add-incompressible-flag-to-read_block_state.patch
reply other threads:[~2022-11-15 23:07 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=20221115230741.E006FC433B5@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=keescook+coverity-bot@chromium.org \
--cc=keescook@chromium.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 \
--cc=suleiman@google.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 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.