rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Hou Tao <houtao1@huawei.com>
Cc: Yufen Yu <yuyufen@huawei.com>,
	axboe@kernel.dk, linux-block@vger.kernel.org, hch@lst.de,
	zhengchuan@huawei.com, yi.zhang@huawei.com, paulmck@kernel.org,
	joel@joelfernandes.org, rcu@vger.kernel.org
Subject: Re: [PATCH] block: make sure last_lookup set as NULL after part deleted
Date: Fri, 3 Jan 2020 16:17:45 +0800	[thread overview]
Message-ID: <20200103081745.GA11275@ming.t460p> (raw)
In-Reply-To: <ea362a86-d2de-7dfe-c826-d59e8b5068c3@huawei.com>

On Fri, Jan 03, 2020 at 03:35:42PM +0800, Hou Tao wrote:
> Hi,
> 
> On 2020/1/3 12:18, Ming Lei wrote:
> > On Fri, Jan 03, 2020 at 11:06:25AM +0800, Hou Tao wrote:
> >> Hi,
> >>
> >> On 2020/1/2 9:23, Ming Lei wrote:
> >>> On Tue, Dec 31, 2019 at 10:55:47PM +0800, Hou Tao wrote:
> >>>> Hi,
> >>>>
> snip
> 
> >> We have got a seemingly better solution: caching the index of last_lookup in tbl->part[]
> >> instead of caching the pointer itself, so we can ensure the validity of returned pointer
> >> by ensuring it's not NULL in tbl->part[] as does when last_lookup is NULL or 0.
> > 
> > Thinking of the problem further, looks we don't need to hold ref for
> > .last_lookup.
> > 
> > What we need is to make sure the partition's ref is increased just
> > before assigning .last_lookup, so how about something like the following?
> > 
> The approach will work for the above case, but it will not work for the following case:
> 
> when blk_account_io_done() releases the last ref-counter of last_lookup and calls call_rcu(),
> and then a RCU read gets the to-be-freed hd-struct.
> 
> blk_account_io_done
>   rcu_read_lock()
>   // the last ref of last_lookup
>   hd_struct_put()
>     call_rcu
> 
>                               rcu_read_lock
>                               read last_lookup
> 
>     free()
>                               // use-after-free ?
>                               hd_struct_try_get

We may avoid that by clearing partition pointer after killing the
partition, how about the following change?

diff --git a/block/blk-core.c b/block/blk-core.c
index 089e890ab208..79599f5fd5b7 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -1365,18 +1365,6 @@ void blk_account_io_start(struct request *rq, bool new_io)
 		part_stat_inc(part, merges[rw]);
 	} else {
 		part = disk_map_sector_rcu(rq->rq_disk, blk_rq_pos(rq));
-		if (!hd_struct_try_get(part)) {
-			/*
-			 * The partition is already being removed,
-			 * the request will be accounted on the disk only
-			 *
-			 * We take a reference on disk->part0 although that
-			 * partition will never be deleted, so we can treat
-			 * it as any other partition.
-			 */
-			part = &rq->rq_disk->part0;
-			hd_struct_get(part);
-		}
 		part_inc_in_flight(rq->q, part, rw);
 		rq->part = part;
 	}
diff --git a/block/genhd.c b/block/genhd.c
index ff6268970ddc..e3dec90b1f43 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -286,17 +286,21 @@ struct hd_struct *disk_map_sector_rcu(struct gendisk *disk, sector_t sector)
 	ptbl = rcu_dereference(disk->part_tbl);
 
 	part = rcu_dereference(ptbl->last_lookup);
-	if (part && sector_in_part(part, sector))
+	if (part && sector_in_part(part, sector) && hd_struct_try_get(part))
 		return part;
 
 	for (i = 1; i < ptbl->len; i++) {
 		part = rcu_dereference(ptbl->part[i]);
 
 		if (part && sector_in_part(part, sector)) {
+                       if (!hd_struct_try_get(part))
+                               goto exit;
 			rcu_assign_pointer(ptbl->last_lookup, part);
 			return part;
 		}
 	}
+ exit:
+	hd_struct_get(&disk->part0);
 	return &disk->part0;
 }
 EXPORT_SYMBOL_GPL(disk_map_sector_rcu);
diff --git a/block/partition-generic.c b/block/partition-generic.c
index 1d20c9cf213f..9ef6c13d5650 100644
--- a/block/partition-generic.c
+++ b/block/partition-generic.c
@@ -283,8 +283,8 @@ void delete_partition(struct gendisk *disk, int partno)
 	if (!part)
 		return;
 
-	rcu_assign_pointer(ptbl->part[partno], NULL);
-	rcu_assign_pointer(ptbl->last_lookup, NULL);
+	get_device(disk_to_dev(disk));
+
 	kobject_put(part->holder_dir);
 	device_del(part_to_dev(part));
 
@@ -296,6 +296,15 @@ void delete_partition(struct gendisk *disk, int partno)
 	 */
 	blk_invalidate_devt(part_devt(part));
 	hd_struct_kill(part);
+
+	/*
+	 * clear partition pointers after this partition is killed, then
+	 * IO path can't re-assign ->last_lookup any more
+	 */
+	rcu_assign_pointer(ptbl->part[partno], NULL);
+	rcu_assign_pointer(ptbl->last_lookup, NULL);
+
+	put_device(disk_to_dev(disk));
 }
 
 static ssize_t whole_disk_show(struct device *dev,

Thanks,
Ming


  reply	other threads:[~2020-01-03  8:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191231110945.10857-1-yuyufen@huawei.com>
2019-12-31 14:55 ` [PATCH] block: make sure last_lookup set as NULL after part deleted Hou Tao
2019-12-31 23:11   ` Paul E. McKenney
2020-01-01  2:33     ` htbegin
2020-01-01  3:39       ` htbegin
2020-01-03 23:45     ` Joel Fernandes
2020-01-04  9:16       ` Hou Tao
2020-01-02  1:23   ` Ming Lei
2020-01-03  3:06     ` Hou Tao
2020-01-03  4:18       ` Ming Lei
2020-01-03  7:35         ` Hou Tao
2020-01-03  8:17           ` Ming Lei [this message]
2020-01-03 12:03             ` Yufen Yu
2020-01-03 15:16               ` Ming Lei
2020-01-06  7:39                 ` Yufen Yu
2020-01-06  8:11                   ` Ming Lei
2020-01-06  9:41                     ` Hou Tao
2020-01-06 10:05                       ` Ming Lei
2020-01-07 11:40                         ` Hou Tao
2020-01-08  3:19                           ` Ming Lei
2020-01-03 12:43   ` Yufen Yu

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=20200103081745.GA11275@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=houtao1@huawei.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-block@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=yi.zhang@huawei.com \
    --cc=yuyufen@huawei.com \
    --cc=zhengchuan@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).