Hi Yi Is it possible to use the latest mdadm https://github.com/md-raid-utilities/mdadm for testing? This problem should already be fixed. Best Regards Xiao On Thu, Jul 17, 2025 at 3:21 PM Yi Zhang <yi.zhang@xxxxxxxxxx> wrote: > > Hi > I reproduced this failure on the latest linux-block/for-next, please > help check it and let me know if you need any infor/test, thanks. > > Environment: > mdadm-4.3-7.fc43.x86_64 > linux-block/for-next: 522390782310 (HEAD -> for-next, origin/for-next) > Merge branch 'for-6.17/io_uring' into for-next > > Reproducer steps > # ./check md/001 > md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap > size) [failed] > runtime 3.511s ... 5.924s > --- tests/md/001.out 2025-07-15 06:27:41.496610277 -0400 > +++ /root/blktests/results/nodev/md/001.out.bad 2025-07-17 > 03:10:50.718820367 -0400 > @@ -1,3 +1,9 @@ > Running md/001 > ++ mdadm --quiet --create /dev/md/blktests_md --level=1 > --bitmap=internal --bitmap-chunk=1024K --assume-clean --run > --raid-devices=2 /dev/nvme0n1 missing > +*** buffer overflow detected ***: terminated > +tests/md/001: line 69: 1835 Aborted (core > dumped) mdadm --quiet --create /dev/md/blktests_md --level=1 > --bitmap=internal --bitmap-chunk=1024K --assume-clean --run > --raid-devices=2 /dev/"${ns}" missing > ++ mdadm --quiet --stop /dev/md/blktests_md > +mdadm: error opening /dev/md/blktests_md: No such file or directory > ++ set +x > ... > (Run 'diff -u tests/md/001.out > /root/blktests/results/nodev/md/001.out.bad' to see the entire diff) > > -- > Best Regards, > Yi Zhang > >
