From: Minchan Kim <minchan@kernel.org>
To: Michael wang <wangyun@linux.vnet.ibm.com>
Cc: Mitch Harder <mitch.harder@sabayonlinux.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiang Liu <jiang.liu@huawei.com>, Nitin Gupta <ngupta@vflare.org>,
Jerome Marchand <jmarchand@redhat.com>,
devel@driverdev.osuosl.org
Subject: Re: BUG: scheduling while atomic 3.10.7 in ZRAM Swap
Date: Mon, 19 Aug 2013 13:44:44 +0900 [thread overview]
Message-ID: <20130819044444.GD26832@bbox> (raw)
In-Reply-To: <52119B4E.4060409@linux.vnet.ibm.com>
Hello,
On Mon, Aug 19, 2013 at 12:13:02PM +0800, Michael wang wrote:
> Hi, Mitch
>
> On 08/17/2013 10:01 PM, Mitch Harder wrote:
> > I'm encountering a BUG while using a ZRAM Swap device.
> >
> > The call trace seems to involve the changes recently added to 3.10.6
> > by the patch:
> > zram: use zram->lock to protect zram_free_page() in swap free notify path
> >
> > The hardware is a x86 single CPU AMD Athlon XP system with 1GB RAM.
> >
> > I'm implementing a 352MB ZRAM swap device, and also have 1GB swap
> > space on the hard disk.
>
> IMHO, it was caused by that swap_entry_free() was invoked with page
> spin-locked, thus zram_slot_free_notify() should not use rw-lock which
> may goto sleep.
>
> CC folks related.
Thanks for Ccing me, Michael,
Mitch, It's known problem and it should be fixed by [1] in recent linux-next.
[1] a0c516cbfc, zram: don't grab mutex in zram_slot_free_noity
Thanks for the report!
>
> Regards,
> Michael Wang
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2013-08-19 4:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 14:01 BUG: scheduling while atomic 3.10.7 in ZRAM Swap Mitch Harder
2013-08-19 4:13 ` Michael wang
2013-08-19 4:44 ` Minchan Kim [this message]
2013-08-20 14:51 ` Mitch Harder
2013-09-11 23:08 ` Mitch Harder
2013-09-12 16:42 ` Greg Kroah-Hartman
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=20130819044444.GD26832@bbox \
--to=minchan@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiang.liu@huawei.com \
--cc=jmarchand@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.org \
--cc=ngupta@vflare.org \
--cc=wangyun@linux.vnet.ibm.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