From: syzbot <syzbot+3a992c9e4fd9f0e6fd0e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] BUG: RESTRACK detected leak of resources
Date: Mon, 04 Oct 2021 03:45:26 -0700 [thread overview]
Message-ID: <0000000000005a800a05cd849c36@google.com> (raw)
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@syzkaller.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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2021-10-04 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:45 syzbot [this message]
2021-10-04 12:42 ` [syzbot] BUG: RESTRACK detected leak of resources Dmitry Vyukov
2021-10-04 13:15 ` Jason Gunthorpe
2021-10-04 13:22 ` Dmitry Vyukov
2021-10-04 16:02 ` Haakon Bugge
2021-10-05 13:11 ` Zhu Yanjun
2021-10-05 23:01 ` Bob Pearson
2021-10-06 10:10 ` Leon Romanovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000005a800a05cd849c36@google.com \
--to=syzbot+3a992c9e4fd9f0e6fd0e@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.