All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurence Oberman <loberman@redhat.com>
To: Bart Van Assche <bart.vanassche@wdc.com>,
	Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/7] dm: Fix the second dec_pending() argument in __split_and_process_bio()
Date: Thu, 10 Aug 2017 10:28:18 -0400	[thread overview]
Message-ID: <1502375298.8615.3.camel@redhat.com> (raw)
In-Reply-To: <20170809183216.526-2-bart.vanassche@wdc.com>

On Wed, 2017-08-09 at 11:32 -0700, Bart Van Assche wrote:
> Detected by sparse.
> 
> Fixes: commit 4e4cbee93d56 ("block: switch bios to blk_status_t")
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Laurence Oberman <loberman@redhat.com>
> ---
>  drivers/md/dm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
> index 2edbcc2d7d3f..8298670757e9 100644
> --- a/drivers/md/dm.c
> +++ b/drivers/md/dm.c
> @@ -1523,7 +1523,7 @@ static void __split_and_process_bio(struct
> mapped_device *md,
>  	}
>  
>  	/* drop the extra reference count */
> -	dec_pending(ci.io, error);
> +	dec_pending(ci.io, errno_to_blk_status(error));
>  }
>  /*-----------------------------------------------------------------
>   * CRUD END

Hello Bart

I applied and tested all patches except patch 2/7 (as discussed)
I also still have the prior patch in place you sent me.

I built a new kernel on 4.13-rc3

The soft lockups are gone for me with 10 parallel writes.
I also have not seen a hard lockup so far.

What is important to note is that if I use the [none] scheduler I am
still stable but I will sporadically get the      ******
"[38071.773471] device-mapper: multipath: blk_get_request() returned
-11 - requeuing
"

However that is not unexpected I guess.

The ( requeuing messages) do NOT show up with [mq-deadline] which is
all I was testing with last night and yesterday. So when I said they
are gone, that was specifically for [mq-deadline]

Patches look good and are helping. I will circle back and patch and
test on Ming's kernel.

For the series except PATCH2/7 and including

[PATCH] block: Make blk_mq_delay_kick_requeue_list() rerun the queue at
a quiet time


Tested-by: Laurence Oberman <loberman@redhat.com>

Thanks
Laurence




--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  parent reply	other threads:[~2017-08-10 14:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 18:32 [PATCH 0/7] Device mapper and dm-mpath fixes Bart Van Assche
2017-08-09 18:32 ` [PATCH 1/7] dm: Fix the second dec_pending() argument in __split_and_process_bio() Bart Van Assche
2017-08-10  9:28   ` Christoph Hellwig
2017-08-10 14:28   ` Laurence Oberman [this message]
2017-08-10 15:02     ` Bart Van Assche
2017-08-09 18:32 ` [PATCH 2/7] dm: Fix printk() rate limiting code Bart Van Assche
2017-08-09 18:32 ` [PATCH 3/7] dm-mpath: Do not lock up a CPU with requeuing activity Bart Van Assche
2017-08-09 18:32   ` Bart Van Assche
2017-08-10  9:29   ` Christoph Hellwig
2017-08-09 18:32 ` [PATCH 4/7] dm-mpath: Avoid that building with W=1 causes gcc 7 to complain about fall-through Bart Van Assche
2017-08-10  9:29   ` Christoph Hellwig
2017-08-09 18:32 ` [PATCH 5/7] dm-mpath: Complain about unsupported __multipath_map_bio() return values Bart Van Assche
2017-08-10  9:29   ` Christoph Hellwig
2017-08-09 18:32 ` [PATCH 6/7] dm-mpath: Retry BLK_STS_RESOURCE errors Bart Van Assche
2017-08-10  9:30   ` Christoph Hellwig
2017-08-09 18:32 ` [PATCH 7/7] dm-mpath: Make the dm-sq requeuing behavior consistent with the dm-mq behavior Bart Van Assche
2017-08-10  9:30   ` Christoph Hellwig
2017-08-09 21:49 ` [PATCH 0/7] Device mapper and dm-mpath fixes Mike Snitzer

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=1502375298.8615.3.camel@redhat.com \
    --to=loberman@redhat.com \
    --cc=bart.vanassche@wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.