linux-kernel - [syzbot] BUG: RESTRACK detected leak of resources

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <0000000000005a800a05cd849c36@google.com>
Date:   Mon, 04 Oct 2021 03:45:26 -0700
From:   syzbot <syzbot+3a992c9e4fd9f0e6fd0e@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] BUG: RESTRACK detected leak of resources

Hello,

syzbot found the following issue on:

HEAD commit:    c7b4d0e56a1d Add linux-next specific files for 20210930
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=104be6cb300000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c9a1f6685aeb48bd
dashboard link: https://syzkaller.appspot.com/bug?extid=3a992c9e4fd9f0e6fd0e
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3a992c9e4fd9f0e6fd0e@...kaller.appspotmail.com

rdma_rxe: rxe-pd pool destroyed with unfree'd elem
rdma_rxe: rxe-mr pool destroyed with unfree'd elem
restrack: ------------[ cut here ]------------
infiniband syz0: BUG: RESTRACK detected leak of resources
restrack: Kernel PD object allocated by rds_rdma is not freed
restrack: ------------[ cut here ]------------


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.