From: Emmanuel Florac <eflorac@intellique.com>
To: list@jonas-server.de
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org, linux-xfs-owner@vger.kernel.org
Subject: Re: XFS Calltraces by using XFS with Ceph
Date: Thu, 15 Jun 2017 19:20:09 +0200 [thread overview]
Message-ID: <20170615192009.18ddd3bc@harpe.intellique.com> (raw)
In-Reply-To: <34ddf391569ed02b85a59eff856088ab@jonas-server.de>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Le Thu, 15 Jun 2017 07:55:12 +0200
list@jonas-server.de écrivait:
> > Looking at the new Elixir[1], it looks like we're trying to deref
> > ((*bpp)->b_addr)->magic, so that might explain the crash you see.
> >
> > --D
> >
> > [1]
> > http://elixir.free-electrons.com/linux/v4.4.72/source/fs/xfs/libxfs/xfs_da_btree.c#L270
> >
> >>
Indeed that matches exactly the crash Darrick mentioned. Looks like you
need either a special hand-patched kernel... or wait for an official
fix for this one :/
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-06-15 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 8:22 XFS Calltraces by using XFS with Ceph list
2017-06-14 12:08 ` Brian Foster
2017-06-14 13:22 ` list
2017-06-14 14:07 ` Brian Foster
2017-06-14 15:55 ` Darrick J. Wong
2017-06-15 5:55 ` list
2017-06-15 17:20 ` Emmanuel Florac [this message]
2017-06-16 5:37 ` list
2017-06-16 13:15 ` Emmanuel Florac
2017-06-16 17:46 ` Darrick J. Wong
2017-06-19 10:17 ` list
2017-07-10 6:34 ` list
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=20170615192009.18ddd3bc@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs-owner@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=list@jonas-server.de \
/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).