xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	linux-block@vger.kernel.org
Cc: damien.lemoal@wdc.com, linux-btrace@vger.kernel.org,
	linux-scsi@vger.kernel.org, konrad.wilk@oracle.com,
	yuchao0@huawei.com, colyli@suse.de, linux-bcache@vger.kernel.org,
	jaegeuk@kernel.org, xen-devel@lists.xenproject.org,
	kent.overstreet@gmail.com, roger.pau@citrix.com
Subject: Re: [Xen-devel] [PATCH V5 0/9] block: use right accessor to read nr_sects
Date: Wed, 21 Aug 2019 08:20:24 -0700	[thread overview]
Message-ID: <1aaf1d56-c1a2-957c-28b6-048f9965f412@acm.org> (raw)
In-Reply-To: <20190821061423.3408-1-chaitanya.kulkarni@wdc.com>

On 8/20/19 11:14 PM, Chaitanya Kulkarni wrote:
> In the blk-zoned, bcache, f2fs, target-pscsi, xen and blktrace
> implementation block device->hd_part->number of sectors field is
> accessed directly without any appropriate locking or accessor function.
> There is an existing accessor function present in the in
> include/linux/genhd.h which should be used to read the
> bdev->hd_part->nr_sects.

For the entire series:

Reviewed-by: Bart Van Assche <bvanassche@acm.org>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2019-08-21 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21  6:14 [Xen-devel] [PATCH V5 0/9] block: use right accessor to read nr_sects Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 1/9] block: add a helper function to read nr_setcs Chaitanya Kulkarni
2019-08-21 15:18   ` Bart Van Assche
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 2/9] blk-zoned: update blkdev_nr_zones() with helper Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 3/9] blk-zoned: update blkdev_report_zone() " Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 4/9] blk-zoned: update blkdev_reset_zones() " Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 5/9] bcache: update cached_dev_init() " Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 6/9] f2fs: use helper in init_blkz_info() Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [PATCH V5 7/9] blktrace: use helper in blk_trace_setup_lba() Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [COMPILE TESTED PATCH V5 8/9] target/pscsi: use helper in pscsi_get_blocks() Chaitanya Kulkarni
2019-08-21  6:14 ` [Xen-devel] [COMPILE TESTED PATCH V5 9/9] xen/blkback: use helper in vbd_sz() Chaitanya Kulkarni
2019-08-21 15:20 ` Bart Van Assche [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=1aaf1d56-c1a2-957c-28b6-048f9965f412@acm.org \
    --to=bvanassche@acm.org \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=colyli@suse.de \
    --cc=damien.lemoal@wdc.com \
    --cc=jaegeuk@kernel.org \
    --cc=kent.overstreet@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrace@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=yuchao0@huawei.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).