All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: dm-devel@redhat.com
Cc: sandeen@redhat.com, ejt@redhat.com
Subject: Re: [PATCH v2] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
Date: Fri, 23 May 2014 16:52:38 -0400	[thread overview]
Message-ID: <20140523205237.GA16191@redhat.com> (raw)
In-Reply-To: <20140522183250.GA7799@redhat.com>

On Thu, May 22 2014 at  2:32pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:

> Update the DM thin provisioning target's allocation failure error to be
> consistent with commit a9d6ceb8 ("[SCSI] return ENOSPC on thin
> provisioning failure").
> 
> The DM thin target now returns -ENOSPC rather than -EIO when
> block allocation fails due to the pool being out of data space (and
> the 'error_if_no_space' thin-pool feature is enabled).
> 
> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> ---
>  drivers/md/dm-bio-prison.c |    4 ++--
>  drivers/md/dm-bio-prison.h |    2 +-
>  drivers/md/dm-thin.c       |   35 +++++++++++++++++++++++------------
>  3 files changed, 26 insertions(+), 15 deletions(-)
> 
> v2: update other should_error_unserviceable_bio() callers and dm_cell_error()

Noticed a leak introduced with my v2, but I've now staged what could be
considered v3 in linux-next via linux-dm.git 'for-next' branch, see:

https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=5d7d20909130de87ae4bccee0c9e92105eb7c886

  reply	other threads:[~2014-05-23 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 18:12 [PATCH] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled Mike Snitzer
2014-05-22 18:32 ` [PATCH v2] " Mike Snitzer
2014-05-23 20:52   ` Mike Snitzer [this message]
2014-05-23  8:50 ` [PATCH] " Joe Thornber

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=20140523205237.GA16191@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=sandeen@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.