From: Damien Le Moal <dlemoal@kernel.org>
To: Dave Chinner <david@fromorbit.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
dm-devel@lists.linux.dev,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [WARN 6.16-rc3] warning in bdev_count_inflight()
Date: Wed, 25 Jun 2025 23:49:53 +0900 [thread overview]
Message-ID: <d6078d51-169b-4152-8589-40251411a45f@kernel.org> (raw)
In-Reply-To: <36b2bb05-d26f-484b-acae-fdad7645f1cd@kernel.org>
On 6/25/25 23:48, Damien Le Moal wrote:
> On 6/25/25 18:00, Dave Chinner wrote:
>> On Wed, Jun 25, 2025 at 06:26:14PM +1000, Dave Chinner wrote:
>>> Hi Jens,
>>>
>>> I had this warning fire on 6.16-rc3 whilst running fstests. I don't
>>> know what test caused it - I run 64 tests in parallel over a couple
>>> of hundred loop devices, so there's lots of stuff going on all the
>>> time.
>>>
>>> This warning fired when xfs_repair was running on some kind of DM
>>> device:
>
> You are not alone seeing this one. Shin'ichiro saw it with blktests runs and
> other peoples have mentioned seeing it with various hardware as well. We have no
> reliable reproducer yet, and because it randomly shows up. So it is hard to
> debug. This is since 6.16-rc1 I think.
Ignore... I was not aware of the fix candidate :)
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-06-25 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 8:26 [WARN 6.16-rc3] warning in bdev_count_inflight() Dave Chinner
2025-06-25 9:00 ` Dave Chinner
2025-06-25 14:48 ` Damien Le Moal
2025-06-25 14:49 ` Damien Le Moal [this message]
2025-06-25 11:28 ` Christoph Hellwig
2025-06-25 12:12 ` Dave Chinner
2025-06-25 12:13 ` 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=d6078d51-169b-4152-8589-40251411a45f@kernel.org \
--to=dlemoal@kernel.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=snitzer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.