From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 121831] Several kmemcheck: Caught 64-bit read from uninitialized memory in radeo
Date: Mon, 11 Jul 2016 09:39:27 +0000 [thread overview]
Message-ID: <bug-121831-2300-QXTN4Z2u8G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-121831-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=121831
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
Shouldn't drivers/dma-buf/fence.c:fence_init() fully initialize the struct
fence passed in? If not, using kzalloc instead of kmalloc in radeon_fence_emit
should probably fix this.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-11 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 11:35 [Bug 121831] New: Several kmemcheck: Caught 64-bit read from uninitialized memory in radeo bugzilla-daemon
2016-07-11 9:39 ` bugzilla-daemon [this message]
2022-02-17 18:10 ` [Bug 121831] " bugzilla-daemon
2022-02-17 18:11 ` bugzilla-daemon
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-121831-2300-QXTN4Z2u8G@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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