From: Oliver Sang <oliver.sang@intel.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org, lkp@lists.01.org
Subject: Re: [btrfs] 62bd8124e2: WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs]
Date: Fri, 10 Jun 2022 09:26:59 +0800 [thread overview]
Message-ID: <20220610012659.GA6844@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20220609094652.GB3668047@falcondesktop>
hi, Filipe Manana,
On Thu, Jun 09, 2022 at 10:46:52AM +0100, Filipe Manana wrote:
>
> I am unable to reproduce that on a 12 cores box.
> I also don't see anything wrong that could lead to that by manual inspection.
>
> How easy is it for you to trigger it?
we reproduced this upon 62bd8124e2 4 times out of 6 runs.
but since the other 2 runs crash early due to other issues (below (1)), we
cannot say they are clean.
at the same time, the 6 runs for parent are clean.
7e2bb5b3f3bca223 62bd8124e2f17910fcd89568e50
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 67% 4:6 dmesg.RIP:btrfs_release_global_block_rsv[btrfs]
:6 67% 4:6 dmesg.WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs]
:6 33% 2:6 dmesg.kernel_BUG_at_fs/xfs/xfs_message.c <----- (1)
>
> Can you also run it with CONFIG_BTRFS_ASSERT=y set in the kernel config?
got it, we will enable this config and rerun tests, for both this commit and
parent.
next prev parent reply other threads:[~2022-06-10 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bf924988687205627604f36cbd8ff13936e938ab.1654009356.git.fdmanana@suse.com>
2022-06-08 15:23 ` kernel test robot
2022-06-09 9:46 ` Filipe Manana
2022-06-10 1:26 ` Oliver Sang [this message]
2022-06-12 14:36 ` Oliver Sang
2022-06-13 10:50 ` Filipe Manana
2022-06-16 2:42 ` Oliver Sang
2022-06-17 10:32 ` Filipe Manana
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=20220610012659.GA6844@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.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
all inboxes | Powered by JetHome®