From: Brian Norris <computersforpeace@gmail.com>
To: akpm@linux-foundation.org
Cc: artem.bityutskiy@linux.intel.com, linux-mtd@lists.infradead.org,
lizefan@huawei.com, dwmw2@infradead.org, stable@vger.kernel.org
Subject: Re: [patch 3/4] jffs2: avoid soft-lockup in jffs2_reserve_space_gc()
Date: Tue, 25 Feb 2014 18:17:09 -0800 [thread overview]
Message-ID: <20140226021709.GD4194@ld-irv-0074> (raw)
In-Reply-To: <20140212204456.E010B5A40F6@corp2gmr1-2.hot.corp.google.com>
+ linux-mtd
Hi Li,
On Wed, Feb 12, 2014 at 12:44:56PM -0800, Andrew Morton wrote:
> From: Li Zefan <lizefan@huawei.com>
> Subject: jffs2: avoid soft-lockup in jffs2_reserve_space_gc()
>
> We triggered soft-lockup under stress test on 2.6.34 kernel.
>
> BUG: soft lockup - CPU#1 stuck for 60009ms! [lockf2.test:14488]
> ...
> [<bf09a4d4>] (jffs2_do_reserve_space+0x420/0x440 [jffs2])
> [<bf09a528>] (jffs2_reserve_space_gc+0x34/0x78 [jffs2])
> [<bf0a1350>] (jffs2_garbage_collect_dnode.isra.3+0x264/0x478 [jffs2])
> [<bf0a2078>] (jffs2_garbage_collect_pass+0x9c0/0xe4c [jffs2])
> [<bf09a670>] (jffs2_reserve_space+0x104/0x2a8 [jffs2])
> [<bf09dc48>] (jffs2_write_inode_range+0x5c/0x4d4 [jffs2])
> [<bf097d8c>] (jffs2_write_end+0x198/0x2c0 [jffs2])
> [<c00e00a4>] (generic_file_buffered_write+0x158/0x200)
> [<c00e14f4>] (__generic_file_aio_write+0x3a4/0x414)
> [<c00e15c0>] (generic_file_aio_write+0x5c/0xbc)
> [<c012334c>] (do_sync_write+0x98/0xd4)
> [<c0123a84>] (vfs_write+0xa8/0x150)
> [<c0123d74>] (sys_write+0x3c/0xc0)]
>
> Fix this by adding a cond_resched() in the while loop.
This patch looks good.
> [akpm@linux-foundation.org: don't initialize `ret']
> Signed-off-by: Li Zefan <lizefan@huawei.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Brian Norris <computersforpeace@gmail.com>
> Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> fs/jffs2/nodemgmt.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff -puN fs/jffs2/nodemgmt.c~jffs2-avoid-soft-lockup-in-jffs2_reserve_space_gc fs/jffs2/nodemgmt.c
> --- a/fs/jffs2/nodemgmt.c~jffs2-avoid-soft-lockup-in-jffs2_reserve_space_gc
> +++ a/fs/jffs2/nodemgmt.c
> @@ -211,20 +211,25 @@ out:
> int jffs2_reserve_space_gc(struct jffs2_sb_info *c, uint32_t minsize,
> uint32_t *len, uint32_t sumsize)
> {
> - int ret = -EAGAIN;
> + int ret;
> minsize = PAD(minsize);
>
> jffs2_dbg(1, "%s(): Requested 0x%x bytes\n", __func__, minsize);
>
> - spin_lock(&c->erase_completion_lock);
> - while(ret == -EAGAIN) {
> + while (true) {
> + spin_lock(&c->erase_completion_lock);
> ret = jffs2_do_reserve_space(c, minsize, len, sumsize);
> if (ret) {
> jffs2_dbg(1, "%s(): looping, ret is %d\n",
> __func__, ret);
> }
> + spin_unlock(&c->erase_completion_lock);
> +
> + if (ret == -EAGAIN)
> + cond_resched();
Just curious: would this be a place to use cond_resched_lock(), and keep
the lock outside the loop?
> + else
> + break;
> }
> - spin_unlock(&c->erase_completion_lock);
> if (!ret)
> ret = jffs2_prealloc_raw_node_refs(c, c->nextblock, 1);
>
Anyway, pushed to l2-mtd.git.
Thanks,
Brian
next parent reply other threads:[~2014-02-26 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140212204456.E010B5A40F6@corp2gmr1-2.hot.corp.google.com>
2014-02-26 2:17 ` Brian Norris [this message]
2014-02-26 12:04 ` [patch 3/4] jffs2: avoid soft-lockup in jffs2_reserve_space_gc() Li Zefan
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=20140226021709.GD4194@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lizefan@huawei.com \
--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