From: Hugh Dickins <hughd@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonas Jensen <jonas.jensen@gmail.com>,
Ming Lei <tom.leiming@gmail.com>,
Kevin Hilman <khilman@linaro.org>, Felipe Balbi <balbi@ti.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Lock Directory failure
Date: Tue, 19 Aug 2014 09:34:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1408190926090.1991@eggly.anvils> (raw)
In-Reply-To: <20140820012345.7c358fd7@canb.auug.org.au>
On Wed, 20 Aug 2014, Stephen Rothwell wrote:
> On Mon, 18 Aug 2014 13:58:26 -0700 (PDT) Hugh Dickins <hughd@google.com> wrote:
> >
> > [PATCH next] vfs: initialize m_list to fix crash in mnt_set_mountpoint
> >
> > Fix mnt_set_mountpoint() crash: new_mountpoint() must initialize m_list.
> >
> > Reported-by: Felipe Balbi <balbi@ti.com>
> > Signed-off-by: Hugh Dickins <hughd@google.com>
>
> I assume that this is a fix for commit 89f7ca1af15b ("vfs: Keep a list
> of mounts on a mount point") that is currently i the vfs tree. I will
> apply this patch as a fix up for the vfs tree in linux-next today.
Yes, that's it: thanks a lot, Stephen, that will help everybody.
I should acknowledge that Thierry Reding posted the same fix (a few
lines away) before mine, but I only came across his later in the day.
Hugh
prev parent reply other threads:[~2014-08-19 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140818163209.GJ9662@saruman.home>
2014-08-18 20:58 ` Lock Directory failure Hugh Dickins
2014-08-19 15:23 ` Stephen Rothwell
2014-08-19 16:34 ` Hugh Dickins [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=alpine.LSU.2.11.1408190926090.1991@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbi@ti.com \
--cc=ebiederm@xmission.com \
--cc=jonas.jensen@gmail.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@gmail.com \
--cc=tom.leiming@gmail.com \
--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).