From: "lilingfeng (A)" <lilingfeng3@huawei.com>
To: <linux-kernel@vger.kernel.org>, Joe Thornber <ejt@redhat.com>
Cc: <snitzer@redhat.com>, <yi.zhang@huawei.com>,
<yangerkun@huawei.com>, <chengzhihao1@huawei.com>,
<zhangxiaoxu5@huawei.com>
Subject: Question about how to trigger BUG_ON() in sm_disk_new_block()
Date: Fri, 13 Jan 2023 16:07:31 +0800 [thread overview]
Message-ID: <3475f910-68fd-76da-c7f9-4fcc32d878e7@huawei.com> (raw)
Hello,
I notice the patch 4feaef830de7ffdd8352e1fe14ad3bf13c9688f8 (dm space
map common: fix to ensure new block isn't already in use) can explain
the BUG_ON() in sm_disk_new_block().
However, I'm still confused since I can't find the code path in which
'begin' field was not being updated (as you say "increment of a data
block reference count due to breaking sharing of a neighbour block in
the same btree leaf").
What I found are as below:
break_sharing
alloc_data_block
dm_pool_alloc_data_block
dm_sm_new_block
sm_disk_new_block
sm_ll_find_free_block
smd->begin = *b + 1
May I bother you to list the path?
Thanks
reply other threads:[~2023-01-13 8:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3475f910-68fd-76da-c7f9-4fcc32d878e7@huawei.com \
--to=lilingfeng3@huawei.com \
--cc=chengzhihao1@huawei.com \
--cc=ejt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=zhangxiaoxu5@huawei.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
all inboxes | Powered by JetHome®