All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: Gregory Farnum <greg@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH 2/3] libceph: define mds_alloc_msg() method
Date: Mon, 04 Mar 2013 13:37:18 -0600	[thread overview]
Message-ID: <5134F7EE.4090407@inktank.com> (raw)
In-Reply-To: <CAPYLRziQhNS1GcXUyhyrY=4YC0A4xW9YhPYYAbQFQJk9JkTAww@mail.gmail.com>

On 03/04/2013 01:05 PM, Gregory Farnum wrote:
> This looks like a faithful reshuffling to me.
> 
> But...
> On Mon, Mar 4, 2013 at 10:12 AM, Alex Elder <elder@inktank.com> wrote:
>> diff --git a/net/ceph/messenger.c b/net/ceph/messenger.c
>> index 6ec6051..c7d4278 100644
>> --- a/net/ceph/messenger.c
>> +++ b/net/ceph/messenger.c
>> @@ -2804,55 +2804,34 @@ static int ceph_alloc_middle(struct
>> ceph_connection *con, struct ceph_msg *msg)
>>  static int ceph_con_in_msg_alloc(struct ceph_connection *con, int *skip)
>>  {
>>         struct ceph_msg_header *hdr = &con->in_hdr;
>> -       int type = le16_to_cpu(hdr->type);
>> -       int front_len = le32_to_cpu(hdr->front_len);
>>         int middle_len = le32_to_cpu(hdr->middle_len);
>>         struct ceph_msg *msg;
>>         int ret = 0;
>>
>>         BUG_ON(con->in_msg != NULL);
>> +       BUG_ON(!con->ops->alloc_msg);
>>
>> -       if (con->ops->alloc_msg) {
>> -               mutex_unlock(&con->mutex);
>> -               msg = con->ops->alloc_msg(con, hdr, skip);
>> -               mutex_lock(&con->mutex);
>> -               if (con->state != CON_STATE_OPEN) {
>> -                       if (msg)
>> -                               ceph_msg_put(msg);
>> -                       return -EAGAIN;
>> -               }
>> -               con->in_msg = msg;
>> -               if (con->in_msg) {
>> -                       con->in_msg->con = con->ops->get(con);
>> -                       BUG_ON(con->in_msg->con == NULL);
>> -               }
>> -               if (*skip) {
>> -                       con->in_msg = NULL;
>> -                       return 0;
>> -               }
>> -               if (!con->in_msg) {
>> -                       con->error_msg =
>> -                               "error allocating memory for incoming message";
>> -                       return -ENOMEM;
>> -               }
>> -       }
>> -       if (!con->in_msg) {
>> -               mutex_unlock(&con->mutex);
>> -               msg = ceph_msg_new(type, front_len, GFP_NOFS, false);
>> -               mutex_lock(&con->mutex);
>> -               if (!msg) {
>> -                       pr_err("unable to allocate msg type %d len %d\n",
>> -                              type, front_len);
>> -                       return -ENOMEM;
>> -               }
>> -               if (con->state != CON_STATE_OPEN) {
>> +       mutex_unlock(&con->mutex);
>> +       msg = con->ops->alloc_msg(con, hdr, skip);
>> +       mutex_lock(&con->mutex);
>> +       if (con->state != CON_STATE_OPEN) {
>> +               if (msg)
>>                         ceph_msg_put(msg);
>> -                       return -EAGAIN;
>> -               }
>> -               con->in_msg = msg;
>> +               return -EAGAIN;
>> +       }
>> +       con->in_msg = msg;
>> +       if (con->in_msg) {
>>                 con->in_msg->con = con->ops->get(con);
>>                 BUG_ON(con->in_msg->con == NULL);
>> -               con->in_msg->page_alignment = le16_to_cpu(hdr->data_off);
>> +       }
>> +       if (*skip) {
>> +               con->in_msg = NULL;
>> +               return 0;
> 
> This looks like a memory leak to me? I'm not familiar with the skip
> infrastructure; is there something that cleans up those messages in
> the background, or should this actually be a BUG_ON?

It looks that way to me too, but the con->ops->get(con) call before
it makes it a little tricky.  I will investigate and get back
to you, and if it is a leak I'll insert a fix for it ahead of this
in the series.

I really appreciate your reviewing these.

					-Alex


  reply	other threads:[~2013-03-04 19:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 18:05 OSD Data Read/Write Separation Patches Alex Elder
2013-03-04 18:08 ` [PATCH 0/3] libceph: a few cleanups Alex Elder
2013-03-04 18:09   ` [PATCH 1/3] libceph: use (void *) for untyped data in osd ops Alex Elder
2013-03-04 18:09   ` [PATCH 2/3] libceph: kill ceph_msg->pagelist_count Alex Elder
2013-03-04 18:09   ` [PATCH 3/3] libceph: rename ceph_calc_object_layout() Alex Elder
2013-03-05  1:49   ` [PATCH 0/3] libceph: a few cleanups Josh Durgin
2013-03-04 18:10 ` [PATCH 0/3] libceph: simplify incoming message allocation Alex Elder
2013-03-04 18:12   ` [PATCH 1/3] libceph: drop mutex while allocating a message Alex Elder
2013-03-04 19:07     ` Gregory Farnum
2013-03-04 19:25       ` Alex Elder
2013-03-04 19:39         ` Gregory Farnum
2013-03-04 19:52           ` Alex Elder
2013-03-04 18:12   ` [PATCH 2/3] libceph: define mds_alloc_msg() method Alex Elder
2013-03-04 19:05     ` Gregory Farnum
2013-03-04 19:37       ` Alex Elder [this message]
2013-03-04 18:12   ` [PATCH 3/3] libceph: no need for alignment for mds message Alex Elder
2013-03-04 19:09     ` Gregory Farnum
2013-03-04 18:14 ` [PATCH 0/3] ceph: assign message data fields consistently Alex Elder
2013-03-04 18:15   ` [PATCH 1/3] ceph: use calc_pages_for() in start_read() Alex Elder
2013-03-04 18:15   ` [PATCH 2/3] ceph: simplify ceph_sync_write() page_align calculation Alex Elder
2013-03-04 18:15   ` [PATCH 3/3] libceph: don't assign page info in ceph_osdc_new_request() Alex Elder
2013-03-05  1:55   ` [PATCH 0/3] ceph: assign message data fields consistently Josh Durgin
2013-03-04 18:16 ` [PATCH 0/3] libceph: distinguish osd request read and write data Alex Elder
2013-03-04 18:17   ` [PATCH 1/3] libceph: separate osd request data info Alex Elder
2013-03-05  2:13     ` Josh Durgin
2013-03-04 18:18   ` [PATCH 2/3] libceph: distinguish page and bio requests Alex Elder
2013-03-05  2:14     ` Josh Durgin
2013-03-04 18:18   ` [PATCH 3/3] libceph: separate read and write data Alex Elder
2013-03-05  2:15     ` Josh Durgin

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=5134F7EE.4090407@inktank.com \
    --to=elder@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.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.