From: akpm@linux-foundation.org
To: axboe@kernel.dk, minchan@kernel.org, mm-commits@vger.kernel.org,
sergey.senozhatsky.work@gmail.com, taejoon.song@lge.com
Subject: + zram-try-to-avoid-worst-case-scenario-on-same-element-pages-update.patch added to -mm tree
Date: Fri, 10 Jan 2020 12:54:08 -0800 [thread overview]
Message-ID: <20200110205408.VVJaJ7sjb%akpm@linux-foundation.org> (raw)
The patch titled
Subject: zram: try to avoid worst-case scenario on same element pages
has been added to the -mm tree. Its filename is
zram-try-to-avoid-worst-case-scenario-on-same-element-pages-update.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/zram-try-to-avoid-worst-case-scenario-on-same-element-pages-update.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/zram-try-to-avoid-worst-case-scenario-on-same-element-pages-update.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Taejoon Song <taejoon.song@lge.com>
Subject: zram: try to avoid worst-case scenario on same element pages
fix off-by-one
Link: http://lkml.kernel.org/r/1578642001-11765-1-git-send-email-taejoon.song@lge.com
Signed-off-by: Taejoon Song <taejoon.song@lge.com>
Acked-by: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/block/zram/zram_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/block/zram/zram_drv.c~zram-try-to-avoid-worst-case-scenario-on-same-element-pages-update
+++ a/drivers/block/zram/zram_drv.c
@@ -217,7 +217,7 @@ static bool page_same_filled(void *ptr,
if (val != page[last_pos])
return false;
- for (pos = 1; pos < last_pos - 1; pos++) {
+ for (pos = 1; pos < last_pos; pos++) {
if (val != page[pos])
return false;
}
_
Patches currently in -mm which might be from taejoon.song@lge.com are
zram-try-to-avoid-worst-case-scenario-on-same-element-pages.patch
zram-try-to-avoid-worst-case-scenario-on-same-element-pages-update.patch
reply other threads:[~2020-01-10 20:54 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=20200110205408.VVJaJ7sjb%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=taejoon.song@lge.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).