dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36522] Caught 16-bit read from uninitialized memory in drm_fb_helper_setcmap
Date: Fri, 05 Aug 2016 07:54:10 +0000	[thread overview]
Message-ID: <bug-36522-2300-6B1XX3P57p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-36522-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=36522

--- Comment #16 from Christian Casteyde <casteyde.christian@free.fr> ---
No, I still have this:
[ 1215.037018] WARNING: kmemcheck: Caught 16-bit read from uninitialized memory
(ffff8801c307d020)
[ 1215.037029] 2e032b012206070e0307373e033534262327353721171507111e031514062322
[ 1215.037038]  u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u
[ 1215.037039]  ^
[ 1215.037046] RIP: 0010:[<ffffffff81442b8b>]  [<ffffffff81442b8b>]
drm_fb_helper_setcmap+0x15b/0x420
[ 1215.037047] RSP: 0018:ffff8801b9fc7a30  EFLAGS: 00010286
[ 1215.037048] RAX: 0000000000000010 RBX: 0000000000000010 RCX:
0000000000000000
[ 1215.037049] RDX: 00000000000000ff RSI: 0000000000ffff00 RDI:
ffff8801c3064390
[ 1215.037050] RBP: ffff8801b9fc7ad8 R08: ffff8801c307c840 R09:
ffff8801c307d200
[ 1215.037051] R10: ffff8801c307d022 R11: 000000000000ffff R12:
ffff8801c307d220
[ 1215.037051] R13: ffff8801c307d420 R14: ffff8801c307c800 R15:
ffff8801c3064000
[ 1215.037053] FS:  00007f35566fd8c0(0000) GS:ffff8801c7400000(0000)
knlGS:0000000000000000
[ 1215.037054] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1215.037055] CR2: ffff8801c29306c0 CR3: 00000000a8911000 CR4:
00000000000406f0
[ 1215.037058]  [<ffffffff813d5009>] fb_set_cmap+0x49/0x130
[ 1215.037060]  [<ffffffff813d2769>] fb_set_var+0x279/0x460
[ 1215.037063]  [<ffffffff813cba4b>] fbcon_blank+0x33b/0x380
[ 1215.037066]  [<ffffffff8142d966>] do_unblank_screen+0xc6/0x190
[ 1215.037069]  [<ffffffff81424263>] vt_ioctl+0x533/0x1430
[ 1215.037071]  [<ffffffff8141950c>] tty_ioctl+0x38c/0xe90
[ 1215.037073]  [<ffffffff811aed7e>] do_vfs_ioctl+0x8e/0x670
[ 1215.037075]  [<ffffffff811af39c>] SyS_ioctl+0x3c/0x70
[ 1215.037078]  [<ffffffff8193fee5>] entry_SYSCALL_64_fastpath+0x18/0xa8
[ 1215.037080]  [<ffffffffffffffff>] 0xffffffffffffffff

-- 
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

  parent reply	other threads:[~2016-08-05  7:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36522-2300@https.bugzilla.kernel.org/>
2012-05-14 14:25 ` [Bug 36522] Caught 16-bit read from uninitialized memory in drm_fb_helper_setcmap bugzilla-daemon
2012-08-05 21:28 ` bugzilla-daemon
2012-10-21 21:49 ` bugzilla-daemon
2013-01-03 12:55 ` bugzilla-daemon
2013-08-31 17:11 ` bugzilla-daemon
2013-12-23 13:40 ` bugzilla-daemon
2016-07-10 11:23 ` bugzilla-daemon
2016-08-04 15:03 ` bugzilla-daemon
2016-08-04 15:04 ` bugzilla-daemon
2016-08-05  7:54 ` bugzilla-daemon [this message]
2016-08-06  2:33 ` bugzilla-daemon
2016-08-06  5:58 ` bugzilla-daemon
2022-02-17 18:19 ` bugzilla-daemon
2022-02-17 18:19 ` 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-36522-2300-6B1XX3P57p@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;
as well as URLs for NNTP newsgroup(s).