Hi
I tried to reproduce the problem by adding mdelay() in
tasklet_action_common() after t->func() but failed.
Since cc->io_queue is created without WQ_UNBOUND, the work queued to it
will be executed by the CPU which queued the work, which means
bio_endio() will not be called until tasklet_acti
ted without WQ_UNBOUND [2].
Revert commit 5735a2671ffb ("dm-crypt, dm-verity: disable tasklets") to
bring tasklet back.
[1] https://lore.kernel.org/all/d390d7ee-f142-44d3-822a-87949e146...@suse.de/T/
[2] https://lore.kernel.org/all/4d331659-badd-749d-fba1-271543631...@huawei.com/
Sign
send the revert patch to 6.6
mainly for comments.
Of course, I think the other branches need it too.
Thanks
在 2024/4/11 17:52, Greg KH 写道:
On Thu, Apr 11, 2024 at 05:15:39PM +0800, Li Lingfeng wrote:
This reverts commit 5735a2671ffb70ea29ca83969fe01316ee2ed6fc
you mind explaining it to me?
Thanks
在 2024/4/11 20:37, Mikulas Patocka 写道:
Hi
I NACK this.
On Thu, 11 Apr 2024, Li Lingfeng wrote:
This reverts commit 5735a2671ffb70ea29ca83969fe01316ee2ed6fc which is
commit 0a9bab391e336489169b95cb0d4553d921302189 upstream.
Tasklet is thought to cause me
dm
device. However, IO can't be done since map is still NULL and it will be
submitted again by kworker.
Leave IO in the deferred list when the map is NULL to prevent IO from
being repeatedly resubmitted until the map is ready.
Signed-off-by: Li Lingfeng
---
drivers/md/dm.c | 6 ++
1 file ch
"
dmsetup suspend mydevice
dmsetup reload mydevice --table "0 2097152 linear /dev/sdb 0"
dmsetup resume mydevice &
dmsetup remove mydevice
Introduce ima_lock to prevent concurrent calls to dm_ima_measure_*
functions to fix it.
Fixes: 91ccbbac1747 ("dm ima: measure data o
prevent concurrent
usage and release.
Fixes: 91ccbbac1747 ("dm ima: measure data on table load")
Signed-off-by: Li Lingfeng
---
drivers/md/dm-ima.c | 45 +
drivers/md/dm-ima.h | 2 ++
2 files changed, 47 insertions(+)
diff --git a/d
在 2025/7/18 2:45, Mikulas Patocka 写道:
On Thu, 17 Jul 2025, Hou Tao wrote:
Hi,
On 7/17/2025 10:07 PM, Li Lingfeng wrote:
There is a window between freeing md->ima.active_table.hash and setting
md->ima.active_table.hash to NULL in dm_ima_measure_on_device_resume
Hi all,
Recently, when creating dm-mpath devices based on iSCSI devices, we
encountered a 'tried to init an initialized object' error triggered
by one DM_DEV_CREATE and two DM_TABLE_LOAD operations.
// DM_DEV_CREATE
dev_create
dm_create
alloc_dev
blk_alloc_disk // alloc gendisk for md->dis