All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamal Mostafa <kamal@canonical.com>
To: "Yan, Zheng" <zyan@redhat.com>
Cc: kernel-team@lists.ubuntu.com,
	Ceph Development <ceph-devel@vger.kernel.org>,
	Luis Henriques <luis.henriques@canonical.com>
Subject: Re: [BUG] backport commit ebeec2ef4c in ubuntu-vivid.git break cephfs
Date: Thu, 31 Mar 2016 07:39:21 -0700	[thread overview]
Message-ID: <20160331143921.GB18035@whence.com> (raw)
In-Reply-To: <90A03E70-2B8B-4C29-9655-A73D7D4523D5@redhat.com>

On Thu, Mar 31, 2016 at 12:06:42PM +0800, Yan, Zheng wrote:
> ubuntu-vivid git tree includes commit ebeec2ef4c (ceph: fix message
> length computation), but does not contain backport for upstream commit
> 1f041a89b4 (ceph: fix request time stamp encoding). This breaks cephfs
> kernel driver completely. Please add the later commit to your git
> tree.
> 
> Regards
> Yan, Zheng

Hi Yan-

Thanks for letting us know about this.  If that patch is required for
all trees that carry a backport of 777d738 (ceph: fix message length
computation), then we'll need to apply 1f041a89b4 to:

  3.19.y-ckt (stable)
  3.16.y-ckt (stable)
  ubuntu-vivid
  ubuntu-utopic

For our reference, can you point me to a bug report or email thread
which discusses the breakage?

 -Kamal

  reply	other threads:[~2016-03-31 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  4:06 [BUG] backport commit ebeec2ef4c in ubuntu-vivid.git break cephfs Yan, Zheng
2016-03-31 14:39 ` Kamal Mostafa [this message]
2016-04-01  2:01   ` Yan, Zheng
2016-04-01 15:59     ` Kamal Mostafa
2016-04-05 20:32     ` Ilya Dryomov

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=20160331143921.GB18035@whence.com \
    --to=kamal@canonical.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=luis.henriques@canonical.com \
    --cc=zyan@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.