From: Thomas Backlund <tmb@mageia.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jordi Pujol <jordipujolp@gmail.com>,
stable@vger.kernel.org, Jiang Liu <jiang.liu@huawei.com>,
linux-kernel@vger.kernel.org
Subject: Re: ZRAM 3.10.6 Buffer I/O error
Date: Tue, 13 Aug 2013 08:01:11 +0300 [thread overview]
Message-ID: <5209BD97.6000605@mageia.org> (raw)
In-Reply-To: <20130813043358.GD3101@bbox>
Minchan Kim skrev 13.8.2013 07:33:
> Hello Greg,
>
> On Mon, Aug 12, 2013 at 08:58:02PM -0700, Greg Kroah-Hartman wrote:
>> On Tue, Aug 13, 2013 at 10:39:00AM +0900, Minchan Kim wrote:
>>> Hello,
>>>
>>> On Mon, Aug 12, 2013 at 07:39:46PM +0300, Thomas Backlund wrote:
>>>> 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:
>>>
>>> Very true. Let's Cc Greg, explicitely.
>>
>> -ENOCONTEXT
>
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/staging/zram?id=75c7caf5a052ffd8db3312fa7864ee2d142890c4
>
> It seems you already merge "zram:allow request end to conincide with disksize" to stable.
> So there is no concern any more.
Nope...
thats master branch wich tracks upstream tree...
it's not in the 3.10 stable as of 3.10.6 (or current stable queue)
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/drivers/staging/zram?h=linux-3.10.y
--
Thomas
next prev parent reply other threads:[~2013-08-13 5:06 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
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 [this message]
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=5209BD97.6000605@mageia.org \
--to=tmb@mageia.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiang.liu@huawei.com \
--cc=jordipujolp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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