From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Nick Piggin <npiggin@kernel.dk>
Subject: Re: [PATCH] Unlock vfsmount_lock in do_mount
Date: Thu, 24 Feb 2011 13:11:06 +0900 [thread overview]
Message-ID: <6152.1298520666@jrobl> (raw)
In-Reply-To: <20110224011057.GP22723@ZenIV.linux.org.uk>
Al Viro:
> On Wed, Feb 23, 2011 at 04:59:49PM +0900, J. R. Okajima wrote:
> > By the commit
> > b3e19d9 2011-01-07 fs: scale mntget/mntput
> > vfsmount_lock was introduced around testing mnt_count.
> > Fix the mis-typed 'unlock'
>
> Gyah... Nice catch. Applied, will push tonight.
Thanks.
But I made a mistake in the subject.
It should be "do_umount" instead of "do_mount". Please fix it when you
push. Otherwise I will post the fixed one.
J. R. Okajima
prev parent reply other threads:[~2011-02-24 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 7:59 [PATCH] Unlock vfsmount_lock in do_mount J. R. Okajima
2011-02-24 1:10 ` Al Viro
2011-02-24 4:11 ` J. R. Okajima [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=6152.1298520666@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).