From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: linux-security-module@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Arnaud Lacombe <lacombar@gmail.com>,
James Morris <jmorris@namei.org>,
David Safford <safford@watson.ibm.com>
Subject: [PATCH v1 0/4] lib: hex2bin error checking
Date: Tue, 20 Sep 2011 15:52:49 -0400 [thread overview]
Message-ID: <1316548373-8782-1-git-send-email-zohar@linux.vnet.ibm.com> (raw)
hex2bin converts a hexadecimal string to its binary representation.
This version simply adds error checking to the existing hex2bin().
On success, hex2bin returns 0, on failure -1.
Changelog v1
- refreshed the trusted, encrypted, 'target' patches
- removed unpack_hex_byte()
- changed return code from boolean to int
Mimi Zohar (4):
lib: add error checking to hex2bin
trusted-keys: check hex2bin result
encrypted-keys: check hex2bin result
target: check hex2bin result
drivers/target/target_core_fabric_lib.c | 11 +++++++++--
include/linux/kernel.h | 2 +-
lib/hexdump.c | 15 +++++++++++----
security/keys/encrypted-keys/encrypted.c | 14 +++++++++++---
security/keys/trusted.c | 19 +++++++++++++++----
5 files changed, 47 insertions(+), 14 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-09-20 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 19:52 Mimi Zohar [this message]
2011-09-20 19:52 ` [PATCH v1 1/4] lib: add error checking to hex2bin Mimi Zohar
2011-09-20 19:52 ` [PATCH v1 2/4] trusted-keys: check hex2bin result Mimi Zohar
2011-09-20 19:52 ` [PATCH v1 3/4] encrypted-keys: " Mimi Zohar
2011-09-20 19:52 ` [PATCH v1 4/4] target: " Mimi Zohar
2011-09-20 23:55 ` Andy Shevchenko
2011-09-21 3:41 ` Mimi Zohar
2011-09-21 15:04 ` Mimi Zohar
2011-09-21 12:35 ` [PATCH v1 4/4] target: check hex2bin result (updated) Mimi Zohar
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=1316548373-8782-1-git-send-email-zohar@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=jmorris@namei.org \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=safford@watson.ibm.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;
as well as URLs for NNTP newsgroup(s).