From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Vasiliy Kulikov <segooon@gmail.com>,
Iliyan Malchev <ibm@android.com>,
Brian Swetland <swetland@google.com>, San Mehat <san@android.com>,
kernel-janitors@vger.kernel.org, Tejun Heo <tj@kernel.org>,
devel@driverdev.osuosl.org, Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/8] staging: dream: fix information leak to userland
Date: Thu, 28 Oct 2010 14:08:02 -0700 [thread overview]
Message-ID: <20101028210802.GA23773@kroah.com> (raw)
In-Reply-To: <20101028205831.GD19421@elf.ucw.cz>
On Thu, Oct 28, 2010 at 10:58:31PM +0200, Pavel Machek wrote:
> Hi!
>
> > > Structure msm_audio_stats is copied to userland with some fields unitialized.
> > > It leads to leaking of contents of kernel stack memory.
> > > Also struct msm_audio_config has field "unused" of type array of 3 elements,
> > > not 4. Instead of this, initialize field "type".
> > >
> > > Signed-off-by: Vasiliy Kulikov <segooon@gmail.com>
> > > ---
> > > drivers/staging/dream/qdsp5/audio_aac.c | 3 ++-
> >
> > {sigh}
> >
> > I'd really like to just drop this whole driver as I feel it's _way_
> > behind whatever anyone is really using "in the wild".
> >
> > Actually, I doubt that anyone even uses this thing, do they?
>
> Not sure, you should definitely talk to codeaurora folks.
>
> > Any objection to me just dropping the drivers/staging/dream/ tree?
> > People should be working on the chipset-specific driver tree here
> > instead, right?
>
> codeaurora people should know...
Which specific ones? No one seems to be contributing to the
drivers/staging/dream/ anymore, and there are a number of out-of-tree
dream trees floating around now.
> > Pavel, it looks like you're not doing any dream work anymore, any
> > problems with me dropping it?
>
> Too busy to do any real work on Dream, sorry :-(.
Ok, I think I'll just drop it unless someone screams.
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-28 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 20:01 [PATCH 1/8] staging: dream: fix information leak to userland Vasiliy Kulikov
2010-10-28 20:45 ` Greg KH
2010-10-28 20:58 ` Pavel Machek
2010-10-28 21:08 ` Greg KH [this message]
2010-10-29 1:32 ` Bryan Huntsman
2010-10-29 1:38 ` Greg KH
2010-10-29 18:27 ` Bryan Huntsman
2010-10-29 19:40 ` Greg KH
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=20101028210802.GA23773@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=ibm@android.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=san@android.com \
--cc=segooon@gmail.com \
--cc=swetland@google.com \
--cc=tj@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