public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Zorro Lang <zlang@redhat.com>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
	"Darrick J. Wong" <djwong@kernel.org>,
	Carlos Maiolino <carlos@maiolino.me>
Subject: Re: [Bug report][fstests generic/047] Internal error !(flags & XFS_DABUF_MAP_HOLE_OK) at line 2572 of file fs/xfs/libxfs/xfs_da_btree.c. Caller xfs_dabuf_map.constprop.0+0x26c/0x368 [xfs]
Date: Tue, 7 Nov 2023 19:13:39 +1100	[thread overview]
Message-ID: <ZUnxswEfoeZQhw5P@dread.disaster.area> (raw)
In-Reply-To: <20231107080522.5lowalssbmi6lus3@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Tue, Nov 07, 2023 at 04:05:22PM +0800, Zorro Lang wrote:
> On Tue, Nov 07, 2023 at 07:33:50AM +1100, Dave Chinner wrote:
> > On Tue, Nov 07, 2023 at 03:26:27AM +0800, Zorro Lang wrote:
> > > Thanks for your reply :) I tried to do a kernel bisect long time, but
> > > find nothing ... Then suddently, I found it's failed from a xfsprogs
> > > change [1].
> > > 
> > > Although that's not the root cause of this bug (on s390x), it just
> > > enabled "nrext64" by default, which I never tested on s390x before.
> > > For now, we know this's an issue about this feature, and only on
> > > s390x for now.
> > 
> > That's not good. Can you please determine if this is a zero-day bug
> > with the nrext64 feature? I think it was merged in 5.19, so if you
> > could try to reproduce it on a 5.18 and 5.19 kernels first, that
> > would be handy.
> 
> Unfortunately, it's a bug be there nearly from beginning. The linux v5.19
> can trigger this bug (with latest xfsprogs for-next branch):

Ok. Can you grab the pahole output for the xfs_dinode and
xfs_log_dinode for s390 from both 5.18 and 5.19 kernel builds?
(i.e. 'pahole fs/xfs/xfs_inode.o |less' and search for the two
structures).

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2023-11-07  8:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29  4:11 [Bug report][fstests generic/047] Internal error !(flags & XFS_DABUF_MAP_HOLE_OK) at line 2572 of file fs/xfs/libxfs/xfs_da_btree.c. Caller xfs_dabuf_map.constprop.0+0x26c/0x368 [xfs] Zorro Lang
2023-11-06  6:13 ` Dave Chinner
2023-11-06 19:26   ` Zorro Lang
2023-11-06 20:33     ` Dave Chinner
2023-11-06 22:20       ` Darrick J. Wong
2023-11-07  8:05       ` Zorro Lang
2023-11-07  8:13         ` Dave Chinner [this message]
2023-11-07 15:13           ` Zorro Lang
2023-11-08  6:38             ` Dave Chinner
     [not found]               ` <CAN=2_H+CdEK_rEUmYbmkCjSRqhX2cwi5yRHQcKAmKDPF16vqOw@mail.gmail.com>
2023-11-09  6:14                 ` Dave Chinner
2023-11-09 14:09                   ` Zorro Lang
2023-11-09 23:13                     ` Dave Chinner
2023-11-10  1:36                       ` Zorro Lang
2023-11-10  2:03                         ` Dave Chinner
2023-11-10  4:32                           ` Darrick J. Wong
2023-11-10  7:34                           ` Christoph Hellwig
2023-11-10 13:56                           ` Zorro Lang
2023-11-14 11:17                           ` edward6
2023-11-07  8:29       ` Christoph Hellwig

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=ZUnxswEfoeZQhw5P@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=carlos@maiolino.me \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@redhat.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