From: Thomas Backlund <tmb@mageia.org>
To: Jordi Pujol <jordipujolp@gmail.com>, stable@vger.kernel.org
Cc: Jiang Liu <jiang.liu@huawei.com>, linux-kernel@vger.kernel.org
Subject: Re: ZRAM 3.10.6 Buffer I/O error
Date: Mon, 12 Aug 2013 19:39:46 +0300 [thread overview]
Message-ID: <52090FD2.9030702@mageia.org> (raw)
In-Reply-To: <1998314.O9XRMyhM6u@pcjordi>
12.08.2013 17:27, Jordi Pujol skrev:
> Hello,
>
> zram shows an error when mounting a swap partition,
> current version Linux kernel 3.10.6,
> previous versions worked, I suppose that latest zram patches have some
> problem,
>
> machine is an AMD64 dual core, 4GB RAM
>
> + modprobe -qb zram num_devices=2
> + echo 104857600 > /sys/block/zram0/disksize
>
> # mkswap /dev/zram0
> Setting up swapspace version 1, size = 102396 KiB
> no label, UUID=6c249930-2ba0-46cf-a8c6-766481942b7d
>
> # pager /var/log/dmesg
> (no more errors shown)
>
> # swapon /dev/zram0
>
> # pager /var/log/dmesg
> ...
> [ 309.300479] Buffer I/O error on device zram0, logical block 25599
> [ 309.300491] Buffer I/O error on device zram0, logical block 25599
> [ 309.300514] Buffer I/O error on device zram0, logical block 25599
> [ 345.205887] Adding 102396k swap on /dev/zram0. Priority:-2 extents:1
> across:102396k SSFS
>
> full log files and the kernel source are stored in the address:
>
> http://livenet.selfip.com/ftp/debian/zram_3.10.6_IO_error/
>
I think this one should fix it and belongs in 3.10 stable too:
From 75c7caf5a052ffd8db3312fa7864ee2d142890c4 Mon Sep 17 00:00:00 2001
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date: Sat, 22 Jun 2013 14:21:00 +0000
Subject: zram: allow request end to coincide with disksize
Pass valid_io_request() checks if request end coincides with disksize
(end equals bound), only fail if we attempt to read beyond the bound.
mkfs.ext2 produces numerous errors:
[ 2164.632747] quiet_error: 1 callbacks suppressed
[ 2164.633260] Buffer I/O error on device zram0, logical block 153599
[ 2164.633265] lost page write due to I/O error on zram0
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
diff --git a/drivers/staging/zram/zram_drv.c
b/drivers/staging/zram/zram_drv.c
index 7538774..82c7202 100644
--- a/drivers/staging/zram/zram_drv.c
+++ b/drivers/staging/zram/zram_drv.c
@@ -180,7 +180,7 @@ static inline int valid_io_request(struct zram
*zram, struct bio *bio)
end = start + (bio->bi_size >> SECTOR_SHIFT);
bound = zram->disksize >> SECTOR_SHIFT;
/* out of range range */
- if (unlikely(start >= bound || end >= bound || start > end))
+ if (unlikely(start >= bound || end > bound || start > end))
return 0;
/* I/O request is valid */
--
cgit v0.9.2
next prev parent reply other threads:[~2013-08-12 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 14:27 ZRAM 3.10.6 Buffer I/O error Jordi Pujol
2013-08-12 16:39 ` Thomas Backlund [this message]
2013-08-13 1:39 ` Minchan Kim
2013-08-13 3:58 ` Greg Kroah-Hartman
2013-08-13 4:33 ` Minchan Kim
2013-08-13 5:01 ` Thomas Backlund
2013-08-13 5:18 ` Minchan Kim
2013-08-13 5:47 ` Greg Kroah-Hartman
2013-08-13 6:03 ` Minchan Kim
2013-08-13 5:13 ` Jordi Pujol
2013-08-13 5:47 ` Greg KH
2013-08-13 11:07 ` Luis Henriques
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=52090FD2.9030702@mageia.org \
--to=tmb@mageia.org \
--cc=jiang.liu@huawei.com \
--cc=jordipujolp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox