From: David Disseldorp <ddiss@suse.de>
To: target-devel@vger.kernel.org
Subject: Re: Memory leak in pSCSI backend?
Date: Tue, 30 Oct 2018 17:58:46 +0000 [thread overview]
Message-ID: <20181030185846.2b5ea2ef@suse.de> (raw)
In-Reply-To: <CAJboL95nkVbNDTCPTGJBzusaFA8ZLZT87oCU1otFO=TT=REbCQ@mail.gmail.com>
Hi Ben,
Thanks for the report.
On Tue, 30 Oct 2018 09:03:38 +1100, Ben Klein wrote:
> Please let me know if there's any other information I can provide.
Any chance you'd be able to rerun your reproducer with kmemleak logging
enabled? Details can be found at:
https://www.kernel.org/doc/Documentation/dev-tools/kmemleak.rst
Cheers, David
prev parent reply other threads:[~2018-10-30 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 22:03 Memory leak in pSCSI backend? Ben Klein
2018-10-30 17:58 ` David Disseldorp [this message]
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=20181030185846.2b5ea2ef@suse.de \
--to=ddiss@suse.de \
--cc=target-devel@vger.kernel.org \
/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.