From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao2.yu@samsung.com>
Cc: "'Yang Shi'" <yang.shi@linaro.org>,
cm224.lee@samsung.com, tglx@linutronix.de, rostedt@goodmis.org,
bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-rt-users@vger.kernel.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] f2fs: mutex can't be used by down_write_nest_lock()
Date: Wed, 2 Mar 2016 10:22:46 -0800 [thread overview]
Message-ID: <20160302182246.GC9395@jaegeuk.gateway> (raw)
In-Reply-To: <00d101d17398$dbbaca10$93305e30$@samsung.com>
On Tue, Mar 01, 2016 at 04:59:39PM +0800, Chao Yu wrote:
> Hi Yang,
>
> > -----Original Message-----
> > From: Yang Shi [mailto:yang.shi@linaro.org]
> > Sent: Saturday, February 27, 2016 8:25 AM
> > To: jaegeuk@kernel.org; cm224.lee@samsung.com; chao2.yu@samsung.com; tglx@linutronix.de;
> > rostedt@goodmis.org; bigeasy@linutronix.de
> > Cc: linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net;
> > linux-fsdevel@vger.kernel.org; linux-rt-users@vger.kernel.org;
> > linaro-kernel@lists.linaro.org; yang.shi@linaro.org
> > Subject: [PATCH] f2fs: mutex can't be used by down_write_nest_lock()
> >
> > fsf2_lock_all() calls down_write_nest_lock() to acquire a rw_sem and check
Fixed, and merged. :)
>
> Nitpick, f2fs_lock_all().
>
> Anyway, this patch looks good to me.
>
> Reviewed-by: Chao Yu <chao2.yu@samsung.com>
prev parent reply other threads:[~2016-03-02 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 0:25 [PATCH] f2fs: mutex can't be used by down_write_nest_lock() Yang Shi
2016-03-01 8:59 ` Chao Yu
2016-03-02 18:22 ` Jaegeuk Kim [this message]
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=20160302182246.GC9395@jaegeuk.gateway \
--to=jaegeuk@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=chao2.yu@samsung.com \
--cc=cm224.lee@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=yang.shi@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.