public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>, reinoudkoornstra@gmail.com
Cc: wagi@monom.org, viro@zeniv.linux.org.uk, xfs@oss.sgi.com
Subject: Re: crash in xfs in current
Date: Mon, 6 Jun 2016 23:27:17 -0700	[thread overview]
Message-ID: <20160607062717.GA30022@infradead.org> (raw)
In-Reply-To: <79c8e051-24a9-2e2b-553a-bcab17d03e83@sandeen.net>

On Mon, Jun 06, 2016 at 11:39:59PM -0500, Eric Sandeen wrote:
> xfs_dir2_leaf_lookup_int() only hits that ASSERT if it was given
> a name to rename, and failed to find the original.  i.e. that should
> not happen.
> 
>         /*
>          * Loop over all the entries with the right hash value
>          * looking to match the name.
>          */
> 
> <do that loop>
> <fail to find the hash value for the name>
> <then:>
> 
>         ASSERT(args->op_flags & XFS_DA_OP_OKNOENT);
>         /*
>          * Here, we can only be doing a lookup (not a rename or remove).
>          * If a case-insensitive match was found earlier, re-read the
>          * appropriate data block if required and return it.
>          */
> 
> A rename should never fail to find the original name.

FYI, this looks very much the same like the Bug Daniel reported, which
I tried to help debugging in person over the weekend.  His backtrace
points to cancelling a dirty transaction after xfs_dir_replace failed,
which most likely comes from the failing lookup, except that he probably
doen't have XFS_DEBUG enabled.

Given that 4.7-rc1 comes with the new shared locks for lookups, and
there are very little other changes I wonder if there is any relation
It would be good if Reinoud and/or Daniel can confirm that Linux 4.6
is ok.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-06-07  6:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  1:43 crash in xfs in current Reinoud Koornstra
2016-06-07  4:39 ` Eric Sandeen
2016-06-07  6:27   ` Christoph Hellwig [this message]
2016-06-07  7:51     ` Daniel Wagner
2016-06-07  8:09       ` Reinoud Koornstra
2016-06-07 10:52         ` Daniel Wagner
2016-06-07 11:07           ` Reinoud Koornstra
2016-06-07 13:44           ` Christoph Hellwig
2016-06-07 23:40             ` Reinoud Koornstra
2016-06-08  4:16               ` Reinoud Koornstra
2016-06-08  4:40                 ` Reinoud Koornstra
2016-06-08  5:40                   ` Christoph Hellwig
2016-06-09  2:22                   ` Dave Chinner
2016-06-09  2:53                     ` Reinoud Koornstra
2016-06-09  2:56                       ` Eric Sandeen
2016-06-09  3:42                         ` Reinoud Koornstra
2016-06-15  5:40                           ` Reinoud Koornstra
2016-06-22  1:42                             ` Dave Chinner
2016-06-30  6:04                               ` Daniel Wagner
2016-06-08 12:08             ` Daniel Wagner
2016-06-07  9:33     ` Reinoud Koornstra

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=20160607062717.GA30022@infradead.org \
    --to=hch@infradead.org \
    --cc=reinoudkoornstra@gmail.com \
    --cc=sandeen@sandeen.net \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wagi@monom.org \
    --cc=xfs@oss.sgi.com \
    /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