All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: linux-kernel@vger.kernel.org,
	Stefano Stabellini <stefano@aporeto.com>,
	dan.carpenter@oracle.com, boris.ostrovsky@oracle.com,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Ron Minnich <rminnich@sandia.gov>,
	Latchesar Ionkov <lucho@ionkov.net>,
	v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH] xen/9pfs: initialize len to 0 to detect xenbus_read errors
Date: Tue, 18 Apr 2017 10:09:59 +0200	[thread overview]
Message-ID: <ea260cd6-eec3-6511-2353-e333c6151663@suse.com> (raw)
In-Reply-To: <1492106276-13505-1-git-send-email-sstabellini@kernel.org>

On 13/04/17 19:57, Stefano Stabellini wrote:
> In order to use "len" to check for xenbus_read errors properly, we need
> to initialize len to 0 before passing it to xenbus_read.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: dan.carpenter@oracle.com
> CC: jgross@suse.com
> CC: boris.ostrovsky@oracle.com
> CC: Eric Van Hensbergen <ericvh@gmail.com>
> CC: Ron Minnich <rminnich@sandia.gov>
> CC: Latchesar Ionkov <lucho@ionkov.net>
> CC: v9fs-developer@lists.sourceforge.net

Committed to xen/tip for-linus-4.12


Thanks,

Juergen

WARNING: multiple messages have this Message-ID (diff)
From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: Latchesar Ionkov <lucho@ionkov.net>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	linux-kernel@vger.kernel.org,
	Stefano Stabellini <stefano@aporeto.com>,
	v9fs-developer@lists.sourceforge.net,
	Ron Minnich <rminnich@sandia.gov>,
	boris.ostrovsky@oracle.com, dan.carpenter@oracle.com
Subject: Re: [PATCH] xen/9pfs: initialize len to 0 to detect xenbus_read errors
Date: Tue, 18 Apr 2017 10:09:59 +0200	[thread overview]
Message-ID: <ea260cd6-eec3-6511-2353-e333c6151663@suse.com> (raw)
In-Reply-To: <1492106276-13505-1-git-send-email-sstabellini@kernel.org>

On 13/04/17 19:57, Stefano Stabellini wrote:
> In order to use "len" to check for xenbus_read errors properly, we need
> to initialize len to 0 before passing it to xenbus_read.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: dan.carpenter@oracle.com
> CC: jgross@suse.com
> CC: boris.ostrovsky@oracle.com
> CC: Eric Van Hensbergen <ericvh@gmail.com>
> CC: Ron Minnich <rminnich@sandia.gov>
> CC: Latchesar Ionkov <lucho@ionkov.net>
> CC: v9fs-developer@lists.sourceforge.net

Committed to xen/tip for-linus-4.12


Thanks,

Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-04-18  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 17:57 [PATCH] xen/9pfs: initialize len to 0 to detect xenbus_read errors Stefano Stabellini
2017-04-18  8:09 ` Juergen Gross [this message]
2017-04-18  8:09   ` Juergen Gross
  -- strict thread matches above, loose matches on Subject: below --
2017-04-13 17:57 Stefano Stabellini

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=ea260cd6-eec3-6511-2353-e333c6151663@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dan.carpenter@oracle.com \
    --cc=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=rminnich@sandia.gov \
    --cc=sstabellini@kernel.org \
    --cc=stefano@aporeto.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    --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.