From: Jens Axboe <axboe@kernel.dk>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Xiaotian Feng <dfeng@redhat.com>,
Dan Rosenberg <drosenberg@vsecurity.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: Always check length of all iov entries in blk_rq_map_user_iov()
Date: Sun, 13 Nov 2011 19:57:10 +0100 [thread overview]
Message-ID: <4EC01306.5030208@kernel.dk> (raw)
In-Reply-To: <1321210507.18929.293.camel@deadeye>
On 2011-11-13 19:55, Ben Hutchings wrote:
> Even after commit 5478755616ae2ef1ce144dded589b62b2a50d575
> ("block: check for proper length of iov entries earlier ...")
> we still won't check for zero-length entries after an unaligned
> entry. Remove the break-statement, so all entries are checked.
Thanks, that is an oversight. Applied.
--
Jens Axboe
prev parent reply other threads:[~2011-11-13 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 18:55 [PATCH] block: Always check length of all iov entries in blk_rq_map_user_iov() Ben Hutchings
2011-11-13 18:57 ` 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=4EC01306.5030208@kernel.dk \
--to=axboe@kernel.dk \
--cc=ben@decadent.org.uk \
--cc=dan.carpenter@oracle.com \
--cc=dfeng@redhat.com \
--cc=drosenberg@vsecurity.com \
--cc=linux-kernel@vger.kernel.org \
/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