public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Ingo Molnar <mingo@elte.hu>, Vegard Nossum <vegardno@ifi.uio.no>
Cc: Dave Airlie <airlied@redhat.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: fix leak of uninitialized data to userspace
Date: Fri, 10 Oct 2008 05:13:06 -0700 (PDT)	[thread overview]
Message-ID: <356742.30067.qm@web38201.mail.mud.yahoo.com> (raw)

> From: Ingo Molnar <mingo@elte.hu>

>
> i've stuck it into the tip/out-of-tree quick-fixes branch.

I've just got to say that testing Ingo's stuff is always an absolute pleasure. Ingo has pulled in test patches into his git tree which makes testing potential fixes many times easier for me (I've had yahoo mail mangle patches which would force me to rebuild the patch by hand rather than just apply it). The sheer speed of turn around is scarily impressive too. If you ever want to know how to get people to test your stuff Ingo's lead is a good one to follow.

> Sitsofe, could you please check very latest tip/master with 
> CONFIG_KMEMCHECK=y, does it find any other uninitialized memory access?

Give me a few minutes and I'll try and get back to you...



      

             reply	other threads:[~2008-10-10 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 12:13 Sitsofe Wheeler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-10 10:02 [PATCH] drm: fix leak of uninitialized data to userspace Vegard Nossum
2008-10-10 10:17 ` Ingo Molnar
2008-11-04 21:38   ` Greg KH
2008-11-04 22:17     ` Ingo Molnar
2008-11-04 22:23       ` Greg KH
2008-11-04 22:42         ` Vegard Nossum
2008-11-04 22:50         ` Dave Airlie

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=356742.30067.qm@web38201.mail.mud.yahoo.com \
    --to=sitsofe@yahoo.com \
    --cc=airlied@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegardno@ifi.uio.no \
    /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