[bug report] kmemleak observed from blktests on latest linux-block/for-next

[Yi Zhang]

Hi Ming

The kmemleak also can be reproduced on 5.19.0-rc2, pls try to enable
nvme_core multipath and retest.

# cat /sys/module/nvme_core/parameters/multipath
Y

[ 7924.010585] run blktests nvme/013 at 2022-06-13 08:22:46
[ 8184.561412] kmemleak: 6 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
[ 8325.411833] run blktests nvme/014 at 2022-06-13 08:29:27
[ 8346.540549] run blktests nvme/015 at 2022-06-13 08:29:48
[ 8370.369628] run blktests nvme/016 at 2022-06-13 08:30:12
[ 8415.649177] run blktests nvme/017 at 2022-06-13 08:30:57
[ 8752.325270] run blktests nvme/018 at 2022-06-13 08:36:34
[ 8755.591067] run blktests nvme/019 at 2022-06-13 08:36:37
[ 8758.549365] run blktests nvme/020 at 2022-06-13 08:36:40
[ 8761.768996] run blktests nvme/021 at 2022-06-13 08:36:43
[ 8765.001197] run blktests nvme/022 at 2022-06-13 08:36:47
[ 8768.416640] run blktests nvme/023 at 2022-06-13 08:36:50
[ 8771.390804] run blktests nvme/024 at 2022-06-13 08:36:53
[ 8774.600581] run blktests nvme/025 at 2022-06-13 08:36:56
[ 8777.796734] run blktests nvme/026 at 2022-06-13 08:36:59
[ 8780.996435] run blktests nvme/027 at 2022-06-13 08:37:03
[ 8784.198718] run blktests nvme/028 at 2022-06-13 08:37:06
[ 8787.433885] run blktests nvme/029 at 2022-06-13 08:37:09
[ 8791.489253] run blktests nvme/030 at 2022-06-13 08:37:13
[ 8794.647937] run blktests nvme/031 at 2022-06-13 08:37:16
[ 8830.344625] run blktests nvme/032 at 2022-06-13 08:37:52
[ 8836.335828] run blktests nvme/032 at 2022-06-13 08:37:58
[ 8838.544409] kmemleak: 1 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
[ 8843.460926] run blktests nvme/032 at 2022-06-13 08:38:05
[ 8854.927287] run blktests nvme/038 at 2022-06-13 08:38:17
[ 8856.009771] run blktests nvme/039 at 2022-06-13 08:38:18
[ 8857.073699] run blktests nvme/039 at 2022-06-13 08:38:19
[ 8858.186741] run blktests nvme/039 at 2022-06-13 08:38:20
[ 8859.671329] run blktests scsi/004 at 2022-06-13 08:38:21
[ 8861.887756] run blktests scsi/005 at 2022-06-13 08:38:23
[ 8868.325999] run blktests scsi/007 at 2022-06-13 08:38:30
[ 8879.486812] run blktests zbd/002 at 2022-06-13 08:38:41
[ 8880.266536] run blktests zbd/003 at 2022-06-13 08:38:42
[ 8881.237849] run blktests zbd/004 at 2022-06-13 08:38:43
[ 8883.809750] run blktests zbd/005 at 2022-06-13 08:38:45
[ 8885.738364] run blktests zbd/006 at 2022-06-13 08:38:47
[ 8887.247449] run blktests zbd/008 at 2022-06-13 08:38:49
[ 9480.025760] kmemleak: 22 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
[10337.012629] run blktests nvme/039 at 2022-06-13 09:02:59
[10337.808560] run blktests nvme/039 at 2022-06-13 09:02:59
[10338.729114] run blktests nvme/039 at 2022-06-13 09:03:00

On Mon, Jun 13, 2022 at 11:29 AM Ming Lei <ming.lei at redhat.com> wrote:
>
> On Sun, Jun 12, 2022 at 03:23:36PM +0800, Yi Zhang wrote:
> > Hello
> > I found below kmemleak with the latest linux-block/for-next[1], pls
> > help check it, thanks.
> >
> > [1]
> > 75d6654eb3ab (origin/for-next) Merge branch 'for-5.19/block' into for-next
>
> Hi Yi,
>
> for-5.19/block should be stale, and seems not see such issue when running blktests
> on v5.19-rc2.
>
>
> Thanks,
> Ming
>


-- 
Best Regards,
  Yi Zhang