From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Vasily Averin <vasily.averin@linux.dev>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH] zram: unsafe zram_get_element call in zram_read_page()
Date: Tue, 7 Nov 2023 19:40:41 +0900 [thread overview]
Message-ID: <20231107104041.GC11577@google.com> (raw)
In-Reply-To: <20231107073911.GB11577@google.com>
On (23/11/07 16:39), Sergey Senozhatsky wrote:
> On (23/11/06 22:54), Vasily Averin wrote:
> > @@ -1362,14 +1362,14 @@ static int zram_read_page(struct zram *zram, struct page *page, u32 index,
> > ret = zram_read_from_zspool(zram, page, index);
> > zram_slot_unlock(zram, index);
> > } else {
> > + unsigned long entry = zram_get_element(zram, index);
> > /*
> > * The slot should be unlocked before reading from the backing
> > * device.
> > */
> > zram_slot_unlock(zram, index);
> >
> > - ret = read_from_bdev(zram, page, zram_get_element(zram, index),
> > - parent);
> > + ret = read_from_bdev(zram, page, entry, parent);
>
> Hmmm,
> We may want to do more here. Basically, we probably need to re-confirm
> after read_from_bdev() that the entry at index still has ZRAM_WB set
> and, if so, that it points to the same blk_idx. IOW, check that it has
> not been free-ed and re-used under us.
>
> Minchan, what do you think? Is that scenario possible?
Basically
---
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index f5e3756fc21a..2d69f6efcee3 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -1364,14 +1364,21 @@ static int zram_read_page(struct zram *zram, struct page *page, u32 index,
ret = zram_read_from_zspool(zram, page, index);
zram_slot_unlock(zram, index);
} else {
+ unsigned long idx = zram_get_element(zram, index);
/*
* The slot should be unlocked before reading from the backing
* device.
*/
zram_slot_unlock(zram, index);
- ret = read_from_bdev(zram, page, zram_get_element(zram, index),
- parent);
+ ret = read_from_bdev(zram, page, idx, parent);
+ if (ret == 0) {
+ zram_slot_lock(zram, index);
+ if (!zram_test_flag(zram, index, ZRAM_WB) ||
+ idx != zram_get_element(zram, index))
+ ret = -EINVAL;
+ zram_slot_unlock(zram, index);
+ }
}
/* Should NEVER happen. Return bio error if it does. */
next prev parent reply other threads:[~2023-11-07 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 19:54 [PATCH] zram: unsafe zram_get_element call in zram_read_page() Vasily Averin
2023-11-07 7:39 ` Sergey Senozhatsky
2023-11-07 10:40 ` Sergey Senozhatsky [this message]
2023-11-07 18:19 ` Vasily Averin
2023-11-08 1:42 ` Sergey Senozhatsky
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=20231107104041.GC11577@google.com \
--to=senozhatsky@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=vasily.averin@linux.dev \
/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.