From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: weird splats in xfs/561 on 6.10-rc1?
Date: Thu, 30 May 2024 23:18:22 -0700 [thread overview]
Message-ID: <20240531061822.GG53013@frogsfrogsfrogs> (raw)
In-Reply-To: <ZllikUoZiO3jVqru@infradead.org>
On Thu, May 30, 2024 at 10:39:29PM -0700, Christoph Hellwig wrote:
> On Thu, May 30, 2024 at 03:59:12PM -0700, Darrick J. Wong wrote:
> > >From what I can tell, this wasn't happening with my 6.9 djwong-dev
> > branch, so I suspect it's something that came in from when I rebased
> > against 6.10-rc1. It seems to happen all over the place (and not just
> > with realtime files) if I leave Zhang Yi's iomap patches applied. If I
> > revert them, the screaming seems to go down to just this one test.
>
> When testing Linus' tree I haven't seen this yet, but I also haven't
> done a lot of testing yet. I mostly triggered odd MM warnings that
> Johannes fixes, but I haven't seen something like this yet.
>
> > The file itself is ~1482KB, or enough for the file to have 0x169 actual
> > blocks of written data to it, so the delalloc reservation is beyond the
> > eof block. Any thoughts?
>
> I'll see if I can reproduce it with your tree. I have a pretty full
> plate given that yesterday was a public holiday here which doesn't
> really help my catch up rate..
Yeah. You might want to revert all of Zhang Yi's patches first, though
maybe his new series actually fixes all the problems.
(Hm, no, it's still missing that cow-over-hole thing Dave was musing
about.)
--D
next prev parent reply other threads:[~2024-05-31 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 22:59 weird splats in xfs/561 on 6.10-rc1? Darrick J. Wong
2024-05-31 5:39 ` Christoph Hellwig
2024-05-31 6:18 ` Darrick J. Wong [this message]
2024-05-31 6:22 ` Christoph Hellwig
2024-05-31 13:58 ` Darrick J. Wong
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=20240531061822.GG53013@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
/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