From: Jon Derrick <jonathan.derrick@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jon Derrick <jonathan.derrick@intel.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
Scott Bauer <scott.bauer@intel.com>,
Rafael Antognolli <rafael.antognolli@intel.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCHv4 0/4] OPAL patches
Date: Wed, 15 Feb 2017 14:45:53 -0700 [thread overview]
Message-ID: <1487195159-12599-1-git-send-email-jonathan.derrick@intel.com> (raw)
Just a couple of fixes for sed-opal to prevent faulty firmware from
allowing us to go off in the weeds, and a helper to remove some
duplicate code.
v3->v4:
uses IS_ERR since tok is embedded in the response buffer and cannot be NULL
v2->v3:
corrected the bad calculation on the response parser check and changed
it to only check the subpacket length
v1->v2:
left tok->len as a size_t
got everyone important on the same email thread
Jon Derrick (4):
block/sed: Use ssize_t on atom parsers to return errors
block/sed: Add helper to qualify response tokens
block/sed: Check received header lengths
MAINTAINERS: Remove powerpc's opal match
MAINTAINERS | 1 -
block/sed-opal.c | 124 +++++++++++++++++++++++++++----------------------------
2 files changed, 60 insertions(+), 65 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-02-15 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 21:45 Jon Derrick [this message]
2017-02-15 21:45 ` [PATCHv4 1/4] block/sed: Use ssize_t on atom parsers to return errors Jon Derrick
2017-02-16 14:33 ` Christoph Hellwig
2017-02-15 21:45 ` [PATCHv4 2/4] block/sed: Add helper to qualify response tokens Jon Derrick
2017-02-16 14:40 ` Christoph Hellwig
2017-02-15 21:45 ` [PATCHv4 3/4] block/sed: Check received header lengths Jon Derrick
2017-02-16 14:40 ` Christoph Hellwig
2017-02-15 21:45 ` [PATCHv4 4/4] MAINTAINERS: Remove powerpc's opal match Jon Derrick
2017-02-15 23:55 ` Andrew Donnellan
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=1487195159-12599-1-git-send-email-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rafael.antognolli@intel.com \
--cc=scott.bauer@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 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).