All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xen.org,
	konrad.wilk@oracle.com, david.vrabel@citrix.com
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] xen/scsiback: avoid warnings when adding multiple LUNs to a domain
Date: Mon, 8 Feb 2016 10:44:21 -0500	[thread overview]
Message-ID: <56B8B7D5.4090506@oracle.com> (raw)
In-Reply-To: <1454941819-24513-3-git-send-email-jgross@suse.com>



On 02/08/2016 09:30 AM, Juergen Gross wrote:
> When adding more than one LUN to a frontend a warning for a failed
> assignment is issued in dom0 for each already existing LUN. Avoid this
> warning by checking for a LUN already existing when existence is
> allowed (scsiback_do_add_lun() called with try == 1).
>
> As the LUN existence check is needed now for a third time, factor it
> out into a function. This in turn leads to a more or less complete
> rewrite of scsiback_del_translation_entry() which will now return a
> proper error code in case of failure.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Cc: stable@vger.kernel.org

Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

  reply	other threads:[~2016-02-08 15:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 14:30 [PATCH v2 0/2] xen/scsiback: correct two issues Juergen Gross
2016-02-08 14:30 ` [PATCH v2 1/2] xen/scsiback: correct frontend counting Juergen Gross
2016-02-08 14:30 ` Juergen Gross
2016-02-08 14:30 ` [PATCH v2 2/2] xen/scsiback: avoid warnings when adding multiple LUNs to a domain Juergen Gross
2016-02-08 14:30 ` Juergen Gross
2016-02-08 15:44   ` Boris Ostrovsky [this message]
2016-02-08 15:44   ` Boris Ostrovsky
2016-02-08 16:46   ` [Xen-devel] " David Vrabel
2016-02-08 16:50     ` Juergen Gross
2016-02-08 16:52       ` David Vrabel
2016-02-08 16:52       ` David Vrabel
2016-02-08 16:50     ` Juergen Gross
2016-02-08 16:46   ` David Vrabel

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=56B8B7D5.4090506@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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.