From: Jens Axboe <jaxboe@fusionio.com>
To: Vasiliy Kulikov <segooon@gmail.com>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
Mike Miller <mike.miller@hp.com>,
"Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
"iss_storagedev@hp.com" <iss_storagedev@hp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: cciss: fix information leak to userland
Date: Thu, 28 Oct 2010 06:32:10 -0600 [thread overview]
Message-ID: <4CC96D4A.7060000@fusionio.com> (raw)
In-Reply-To: <1288194048-9233-1-git-send-email-segooon@gmail.com>
On 2010-10-27 09:40, Vasiliy Kulikov wrote:
> Structure IOCTL_Command_struct is copied to userland with
> some padding fields at the end of the struct unitialized.
> It leads to leaking of contents of kernel stack memory.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2010-10-28 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 15:40 [PATCH] block: cciss: fix information leak to userland Vasiliy Kulikov
2010-10-28 12:32 ` Jens Axboe [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=4CC96D4A.7060000@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=akpm@linux-foundation.org \
--cc=iss_storagedev@hp.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=segooon@gmail.com \
/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