From: Tommi Virtanen <tommi.virtanen@dreamhost.com>
To: Henry C Chang <henry.cy.chang@gmail.com>
Cc: ceph-devel@vger.kernel.org,
Henry C Chang <henry_c_chang@tcloudcomputing.com>
Subject: Re: [PATCH] libceph: fix ceph_msg_new error path
Date: Tue, 3 May 2011 09:46:37 -0700 [thread overview]
Message-ID: <20110503164637.GD20739@dreamer> (raw)
In-Reply-To: <20110503161431.GA20739@dreamer>
On Tue, May 03, 2011 at 09:14:31AM -0700, Tommi Virtanen wrote:
> On Tue, May 03, 2011 at 02:29:56AM +0000, Henry C Chang wrote:
> > If memory allocation failed, calling ceph_msg_put() will cause GPF
> > since some of ceph_msg variables are not initialized first.
> >
> > Fix Bug #970.
>
> Looks good and explains the symptoms perfectly. Committed to
> ceph-client.git as 56f63aeb6360fb3ba9584bd5b094d55283a9e332.
> Thanks!
I backed that out in favor of Sage's commits to for-linus. Sorry about
the confusion.
--
:(){ :|:&};:
prev parent reply other threads:[~2011-05-03 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 2:29 [PATCH] libceph: fix ceph_msg_new error path Henry C Chang
2011-05-03 16:08 ` Sage Weil
2011-05-03 16:14 ` Tommi Virtanen
2011-05-03 16:46 ` Tommi Virtanen [this message]
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=20110503164637.GD20739@dreamer \
--to=tommi.virtanen@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=henry.cy.chang@gmail.com \
--cc=henry_c_chang@tcloudcomputing.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.