* Question about how to trigger BUG_ON() in sm_disk_new_block()
@ 2023-01-13 8:07 lilingfeng (A)
0 siblings, 0 replies; only message in thread
From: lilingfeng (A) @ 2023-01-13 8:07 UTC (permalink / raw)
To: linux-kernel, Joe Thornber
Cc: snitzer, yi.zhang, yangerkun, chengzhihao1, zhangxiaoxu5
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-01-13 8:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-13 8:07 Question about how to trigger BUG_ON() in sm_disk_new_block() lilingfeng (A)
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®