Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Hugh Dickins <hughd@google.com>
Cc: Felipe Balbi <balbi@ti.com>,
	"Eric W. Biederman" <ebiederman@twitter.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: Wed, 20 Aug 2014 01:23:45 +1000	[thread overview]
Message-ID: <20140820012345.7c358fd7@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LSU.2.11.1408181350260.1127@eggly.anvils>

[-- Attachment #1: Type: text/plain, Size: 596 bytes --]

Hi Hugh,

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-19 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 16:32 Lock Directory failure Felipe Balbi
2014-08-18 20:58 ` Hugh Dickins
2014-08-19 15:23   ` Stephen Rothwell [this message]
2014-08-19 16:34     ` Hugh Dickins

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=20140820012345.7c358fd7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=balbi@ti.com \
    --cc=ebiederman@twitter.com \
    --cc=hughd@google.com \
    --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=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