From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 205595] Memory leak in scsi_init_io
Date: Mon, 30 Dec 2019 05:00:49 +0000 [thread overview]
Message-ID: <bug-205595-11613-MvXvZEDzd2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205595-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205595
--- Comment #1 from Bart Van Assche (bvanassche@acm.org) ---
On 2019-11-20 06:27, bugzilla-daemon@bugzilla.kernel.org wrote:
> Syzkaller hit 'memory leak in scsi_init_io' bug.
> BUG: memory leak
> unreferenced object 0xffff888029b78500 (size 256):
Was the "unreferenced object" text perhaps generated by kmemleak?
What software genereated the "BUG: memory leak" output? A quick search
through the kernel tree did not reveal any code that produces that text.
I'm wondering how to reproduce this issue and the leak reports. Is
running the provided syzkaller reproducer sufficient?
Thanks,
Bart.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-12-30 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 14:27 [Bug 205595] New: Memory leak in scsi_init_io bugzilla-daemon
2019-12-30 5:00 ` Bart Van Assche
2019-12-30 5:00 ` bugzilla-daemon [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=bug-205595-11613-MvXvZEDzd2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox