public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Denis ChengRq <crquan@gmail•com>,
	Jens Axboe <jens.axboe@oracle•com>, Tejun Heo <tj@kernel•org>,
	Andre Noll <maan@systemlinux•org>
Subject: Re: linux-next: manual merge of the md tree
Date: Wed, 15 Oct 2008 21:52:38 +1100	[thread overview]
Message-ID: <18677.52086.914687.271000@notabene.brown> (raw)
In-Reply-To: message from Stephen Rothwell on Wednesday October 15

On Wednesday October 15, sfr@canb•auug.org.au wrote:
> Hi Neil,
> 
> Today's linux-next merge of the md tree got a conflict in
> drivers/md/linear.c between commits
> c9959059161ddd7bf4670cf47367033d6b2f79c4 ("block: fix diskstats access")
> and 6feef531f55cf4a20fd9eb39f5352e5745203603 ("block: mark bio_split_pool
> static") from Linus' tree and commit
> 2bc5b53551d8246e18562fa8e0cf5fe64b5f8184 ("md: linear: Represent
> dev_info->size and dev_info->offset in sectors") from the md tree.
> 
> Just overlapping changes.  I fixed it up (see below).

Thanks.
I pushed out a new for-next just a couple of hours before I got this
email which resolves that, so the conflict should disappear in your
next merge.

NeilBrown


> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb•auug.org.au
> http://www.canb.auug.org.au/~sfr/
> 
> diff --cc drivers/md/linear.c
> index b9cbee68,9b0c5b0..0000000
> --- a/drivers/md/linear.c
> +++ b/drivers/md/linear.c
> @@@ -317,33 -307,29 +307,33 @@@ static int linear_make_request (struct 
>   	const int rw = bio_data_dir(bio);
>   	mddev_t *mddev = q->queuedata;
>   	dev_info_t *tmp_dev;
> - 	sector_t block;
>  +	int cpu;
>   
>   	if (unlikely(bio_barrier(bio))) {
>   		bio_endio(bio, -EOPNOTSUPP);
>   		return 0;
>   	}
>   
>  -	disk_stat_inc(mddev->gendisk, ios[rw]);
>  -	disk_stat_add(mddev->gendisk, sectors[rw], bio_sectors(bio));
>  +	cpu = part_stat_lock();
>  +	part_stat_inc(cpu, &mddev->gendisk->part0, ios[rw]);
>  +	part_stat_add(cpu, &mddev->gendisk->part0, sectors[rw],
>  +		      bio_sectors(bio));
>  +	part_stat_unlock();
>   
>   	tmp_dev = which_dev(mddev, bio->bi_sector);
> - 	block = bio->bi_sector >> 1;
>       
> - 	if (unlikely(block >= (tmp_dev->size + tmp_dev->offset)
> - 		     || block < tmp_dev->offset)) {
> + 	if (unlikely(bio->bi_sector >= (tmp_dev->num_sectors +
> + 					tmp_dev->start_sector)
> + 		     || (bio->bi_sector <
> + 			 tmp_dev->start_sector))) {
>   		char b[BDEVNAME_SIZE];
>   
> - 		printk("linear_make_request: Block %llu out of bounds on "
> - 			"dev %s size %llu offset %llu\n",
> - 			(unsigned long long)block,
> + 		printk("linear_make_request: Sector %llu out of bounds on "
> + 			"dev %s: %llu sectors, offset %llu\n",
> + 			(unsigned long long)bio->bi_sector,
>   			bdevname(tmp_dev->rdev->bdev, b),
> - 			(unsigned long long)tmp_dev->size,
> - 		        (unsigned long long)tmp_dev->offset);
> + 			(unsigned long long)tmp_dev->num_sectors,
> + 			(unsigned long long)tmp_dev->start_sector);
>   		bio_io_error(bio);
>   		return 0;
>   	}
> @@@ -353,8 -339,9 +343,9 @@@
>   		 * split it.
>   		 */
>   		struct bio_pair *bp;
>  -		bp = bio_split(bio, bio_split_pool,
>  +		bp = bio_split(bio,
> - 			       ((tmp_dev->offset + tmp_dev->size)<<1) - bio->bi_sector);
> + 			       tmp_dev->start_sector + tmp_dev->num_sectors
> + 			       - bio->bi_sector);
>   		if (linear_make_request(q, &bp->bio1))
>   			generic_make_request(&bp->bio1);
>   		if (linear_make_request(q, &bp->bio2))
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-10-15 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  8:34 linux-next: manual merge of the md tree Stephen Rothwell
2008-10-15 10:52 ` Neil Brown [this message]
2008-10-16  6:07   ` Stephen Rothwell
2008-10-16  6:13     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-10-15  8:41 Stephen Rothwell

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=18677.52086.914687.271000@notabene.brown \
    --to=neilb@suse$(echo .)de \
    --cc=crquan@gmail$(echo .)com \
    --cc=jens.axboe@oracle$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=maan@systemlinux$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tj@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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