From: Juergen Gross <jgross@suse.com>
To: David Vrabel <david.vrabel@citrix.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xen.org,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com
Cc: stable@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v2 2/2] xen/scsiback: avoid warnings when adding multiple LUNs to a domain
Date: Mon, 8 Feb 2016 17:50:45 +0100 [thread overview]
Message-ID: <56B8C765.4000707@suse.com> (raw)
In-Reply-To: <56B8C65C.1060901@citrix.com>
On 08/02/16 17:46, David Vrabel wrote:
> On 08/02/16 14:30, 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
>
> Avoiding warnings doesn't seem like a viable candidate for stable. Is
> there more to this patch than the description suggests?
No.
Should I resend without the Cc: stable?
Juergen
next prev parent reply other threads:[~2016-02-08 16:50 UTC|newest]
Thread overview: 7+ 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 ` [PATCH v2 2/2] xen/scsiback: avoid warnings when adding multiple LUNs to a domain Juergen Gross
2016-02-08 15:44 ` Boris Ostrovsky
2016-02-08 16:46 ` [Xen-devel] " David Vrabel
2016-02-08 16:50 ` Juergen Gross [this message]
2016-02-08 16:52 ` 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=56B8C765.4000707@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox