ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Joseph Qi <jiangqi903@gmail.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2/o2hb: check len for bio_add_page() to avoid getting incorrect bio
Date: Thu, 29 Mar 2018 09:33:18 +0800	[thread overview]
Message-ID: <8a6155f9-9f50-9c48-74f9-9d586b7b8fb2@gmail.com> (raw)
In-Reply-To: <5ABC3EBE.5020807@huawei.com>



On 18/3/29 09:17, piaojun wrote:
> We need check len for bio_add_page() to make sure the bio has been set up
> correctly, otherwise we may submit incorrect data to device.
> 
> Signed-off-by: Jun Piao <piaojun@huawei.com>
> Reviewed-by: Yiwen Jiang <jiangyiwen@huawei.com>
> Reviewed-by: Changwei Ge <ge.changwei@h3c.com>

Acked-by: Joseph Qi <jiangqi903@gmail.com>
> ---
>  fs/ocfs2/cluster/heartbeat.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/ocfs2/cluster/heartbeat.c b/fs/ocfs2/cluster/heartbeat.c
> index ea8c551..91a8889 100644
> --- a/fs/ocfs2/cluster/heartbeat.c
> +++ b/fs/ocfs2/cluster/heartbeat.c
> @@ -570,7 +570,16 @@ static struct bio *o2hb_setup_one_bio(struct o2hb_region *reg,
>  		     current_page, vec_len, vec_start);
> 
>  		len = bio_add_page(bio, page, vec_len, vec_start);
> -		if (len != vec_len) break;
> +		if (len != vec_len) {
> +			mlog(ML_ERROR, "Adding page[%d] to bio failed, "
> +			     "page %p, len %d, vec_len %u, vec_start %u, "
> +			     "bi_sector %llu\n", current_page, page, len,
> +			     vec_len, vec_start,
> +			     (unsigned long long)bio->bi_iter.bi_sector);
> +			bio_put(bio);
> +			bio = ERR_PTR(-EIO);
> +			return bio;
> +		}
> 
>  		cs += vec_len / (PAGE_SIZE/spp);
>  		vec_start = 0;
> 

      reply	other threads:[~2018-03-29  1:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  1:17 [Ocfs2-devel] [PATCH v2] ocfs2/o2hb: check len for bio_add_page() to avoid getting incorrect bio piaojun
2018-03-29  1:33 ` Joseph Qi [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=8a6155f9-9f50-9c48-74f9-9d586b7b8fb2@gmail.com \
    --to=jiangqi903@gmail.com \
    --cc=ocfs2-devel@oss.oracle.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).