From: Minchan Kim <minchan@kernel.org>
To: kerolasa@gmail.com
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org,
util-linux <util-linux@vger.kernel.org>
Subject: Re: zram hot_add device busy
Date: Mon, 26 Jun 2017 11:23:01 +0900 [thread overview]
Message-ID: <20170626022301.GA18490@bbox> (raw)
In-Reply-To: <CAG27Bk06F72rk7i-dL=DhDmhX3BhCZFct+AAVBis7NMqTEF98w@mail.gmail.com>
Hello,
On Sat, Jun 24, 2017 at 11:08:01AM +0100, Sami Kerola wrote:
> Hello,
>
> While going through if there are new util-linux bugs reported I came a
> cross this https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1645846
>
> Simple way to reproduce the issue is:
> d=$(cat /sys/class/zram-control/hot_add) && zramctl --size 256M /dev/zram$d
To know the problem comes from any side, could you test it without zramctl
command?
IOW,
d=$(cat /sys/class/zram-control/hot_add) && echo $((256<<20)) /dev/zram$d
If it still has a problem, please show your test code which helps
understanding of fundamental problem a lot. ;-)
>
> I am not entirely sure, but drivers/block/zram/zram_drv.c function
> zram_add() should block until the device is usable. Looking the code
> that it might be the device_add_disk() from block/genhd.c that should
> do the blocking. But perhaps it's best if I leave such detail to
> people who know the code a bit better.
I might miss something but I believe device is usable state after zram_add done.
Just in case, please test return value after some operation.
if [ $? -ne 0 ];
then
echo "fail to some op"
blah blah
fi
Thanks.
>
> One thing annoys me. I expected 'zramctl --find --size 256M' to suffer
> from same issue but it does not. I can only reproduce the issue when
> triggering hot_add separately, and as quick as possibly using the
> path. Notice that sometimes it takes second try before the hot_add and
> use triggers the issue. That is almost certainly down to speed the
> system in hand, e.g., quicker the computer less likely to trigger.
>
> --
> Sami Kerola
> http://www.iki.fi/kerolasa/
next prev parent reply other threads:[~2017-06-26 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 10:08 zram hot_add device busy Sami Kerola
2017-06-26 2:23 ` Minchan Kim [this message]
2017-06-26 2:39 ` Sergey Senozhatsky
2017-06-26 2:58 ` 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=20170626022301.GA18490@bbox \
--to=minchan@kernel.org \
--cc=kerolasa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=util-linux@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