From: Greg KH <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Alexander Usyskin <alexander.usyskin@intel.com>
Subject: Re: [char-misc-next 3/3 V2] mei: report consistently copy_from/to_user failures
Date: Mon, 17 Mar 2014 15:53:10 -0700 [thread overview]
Message-ID: <20140317225310.GA28519@kroah.com> (raw)
In-Reply-To: <1394623153-27046-1-git-send-email-tomas.winkler@intel.com>
On Wed, Mar 12, 2014 at 01:19:13PM +0200, Tomas Winkler wrote:
> From: Alexander Usyskin <alexander.usyskin@intel.com>
>
> Consistently display error on possible copy_from/to_user failures
> use dev_dbg so it cannot be abused to flood the kernel log
>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> Reviewed-on: https://git-isdc.jer.intel.com/gerrit/1158
That's a non-public URL, so it doesn't make sense to be put into a
kernel changelog :(
next prev parent reply other threads:[~2014-03-17 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 11:19 [char-misc-next 3/3 V2] mei: report consistently copy_from/to_user failures Tomas Winkler
2014-03-17 22:53 ` Greg KH [this message]
2014-03-18 6:06 ` Winkler, Tomas
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=20140317225310.GA28519@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.