public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] zoran: do not use kmalloc for memory mapped to userspace
Date: Thu, 21 Jan 2016 11:22:46 +0100	[thread overview]
Message-ID: <20160121102246.GE29520@dhcp22.suse.cz> (raw)
In-Reply-To: <1453364958-29983-1-git-send-email-mhocko@kernel.org>

On Thu 21-01-16 09:29:18, Michal Hocko wrote:
> Hi,
> I am sending this offlist for the review because this has security

Ups, forgot to update this. This went offlist before but Hans has noted
that it can go public because the number of users of this old HW is so
limitted that any potential security concerns are basically moot.
-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2016-01-21 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  8:29 [PATCH] [media] zoran: do not use kmalloc for memory mapped to userspace Michal Hocko
2016-01-21 10:22 ` Michal Hocko [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=20160121102246.GE29520@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.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