event->sector (the location) and event->nr_sector (the amount of sectors written) are switched up in the code (where one wants the location of a block I/O access, the nr_sector field is used and vice versa), resulting in nonsensical I/O events.
This issue is unrelated to the issue preventing lo2s from correctly capturing the activity of NVMe devices specifically(#290), which is not caused by lo2s incorrectly handling block I/O events, but most likely by NVMe devices (partially) bypassing the block layer.
event->sector(the location) andevent->nr_sector(the amount of sectors written) are switched up in the code (where one wants the location of a block I/O access, thenr_sectorfield is used and vice versa), resulting in nonsensical I/O events.This issue is unrelated to the issue preventing lo2s from correctly capturing the activity of NVMe devices specifically(#290), which is not caused by lo2s incorrectly handling block I/O events, but most likely by NVMe devices (partially) bypassing the block layer.