From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: linux-xfs@vger.kernel.org, riteshh@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org
Subject: Re: [next-20220215] WARNING at fs/iomap/buffered-io.c:75 with xfstests
Date: Wed, 16 Feb 2022 18:39:19 +1100 [thread overview]
Message-ID: <20220216183919.13b32e1e@canb.auug.org.au> (raw)
In-Reply-To: <5AD0BD6A-2C31-450A-924E-A581CD454073@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Hi Sachin,
On Wed, 16 Feb 2022 12:55:02 +0530 Sachin Sant <sachinp@linux.ibm.com> wrote:
>
> While running xfstests on IBM Power10 logical partition (LPAR) booted
> with 5.17.0-rc4-next-20220215 following warning was seen:
>
> The warning is seen when test tries to unmount the file system. This problem is seen
> while running generic/475 sub test. Have attached captured messages during the test
> run of generic/475.
>
> xfstest is a recent add to upstream regression bucket. I don’t have any previous data
> to attempt a git bisect.
If you have time, could you test v5.17-rc4-2-gd567f5db412e (the commit
in Linus' tree that next-20220215 is based on) and if that OK, then a
bisect from that to 5.17.0-rc4-next-20220215 may be helpful.
Thanks for the report.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-16 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 7:25 [next-20220215] WARNING at fs/iomap/buffered-io.c:75 with xfstests Sachin Sant
2022-02-16 7:39 ` Stephen Rothwell [this message]
2022-02-16 9:47 ` Sachin Sant
2022-02-16 11:39 ` Stephen Rothwell
2022-02-16 17:35 ` Darrick J. Wong
2022-02-16 17:46 ` Matthew Wilcox
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=20220216183919.13b32e1e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=riteshh@linux.ibm.com \
--cc=sachinp@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).