Show a cover letter.

GET /api/covers/53015/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 53015,
    "url": "http://patches.dpdk.org/api/covers/53015/?format=api",
    "web_url": "http://patches.dpdk.org/cover/53015/",
    "project": {
        "id": 1,
        "url": "http://patches.dpdk.org/api/projects/1/?format=api",
        "name": "DPDK",
        "link_name": "dpdk",
        "list_id": "dev.dpdk.org",
        "list_email": "dev@dpdk.org",
        "web_url": "http://core.dpdk.org",
        "scm_url": "git://dpdk.org/dpdk",
        "webscm_url": "http://git.dpdk.org/dpdk"
    },
    "msgid": "<20190423174334.19612-1-herakliusz.lipiec@intel.com>",
    "date": "2019-04-23T17:43:26",
    "name": "[v2,0/8] ipc: fix possible memleaks",
    "submitter": {
        "id": 742,
        "url": "http://patches.dpdk.org/api/people/742/?format=api",
        "name": "Lipiec, Herakliusz",
        "email": "herakliusz.lipiec@intel.com"
    },
    "mbox": "http://patches.dpdk.org/cover/53015/mbox/",
    "series": [
        {
            "id": 4432,
            "url": "http://patches.dpdk.org/api/series/4432/?format=api",
            "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=4432",
            "date": "2019-04-23T17:43:26",
            "name": "ipc: fix possible memleaks",
            "version": 2,
            "mbox": "http://patches.dpdk.org/series/4432/mbox/"
        }
    ],
    "comments": "http://patches.dpdk.org/api/covers/53015/comments/",
    "headers": {
        "X-Mailer": "git-send-email 2.17.2",
        "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
        "Precedence": "list",
        "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
        "Date": "Tue, 23 Apr 2019 18:43:26 +0100",
        "X-Mailman-Version": "2.1.15",
        "Delivered-To": "patchwork@dpdk.org",
        "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
        "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
        "X-Amp-Result": "SKIPPED(no attachment in message)",
        "Cc": "dev@dpdk.org,\n\tHerakliusz Lipiec <herakliusz.lipiec@intel.com>",
        "To": "",
        "Errors-To": "dev-bounces@dpdk.org",
        "References": "<20190417143822.21276-1-herakliusz.lipiec@intel.com>",
        "Sender": "\"dev\" <dev-bounces@dpdk.org>",
        "From": "Herakliusz Lipiec <herakliusz.lipiec@intel.com>",
        "Return-Path": "<dev-bounces@dpdk.org>",
        "X-IronPort-AV": "E=Sophos;i=\"5.60,386,1549958400\"; d=\"scan'208\";a=\"226004713\"",
        "List-Post": "<mailto:dev@dpdk.org>",
        "Received": [
            "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 687021B0F8;\n\tTue, 23 Apr 2019 19:43:24 +0200 (CEST)",
            "from mga05.intel.com (mga05.intel.com [192.55.52.43])\n\tby dpdk.org (Postfix) with ESMTP id 4D46B5F72\n\tfor <dev@dpdk.org>; Tue, 23 Apr 2019 19:43:23 +0200 (CEST)",
            "from orsmga001.jf.intel.com ([10.7.209.18])\n\tby fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t23 Apr 2019 10:43:22 -0700",
            "from silpixa00399499.ir.intel.com (HELO\n\tsilpixa00399499.ger.corp.intel.com) ([10.237.222.133])\n\tby orsmga001.jf.intel.com with ESMTP; 23 Apr 2019 10:43:19 -0700"
        ],
        "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
        "X-Amp-File-Uploaded": "False",
        "Subject": "[dpdk-dev] [PATCH v2 0/8] ipc: fix possible memleaks",
        "In-Reply-To": "<20190417143822.21276-1-herakliusz.lipiec@intel.com>",
        "Message-Id": "<20190423174334.19612-1-herakliusz.lipiec@intel.com>",
        "X-ExtLoop1": "1",
        "X-BeenThere": "dev@dpdk.org",
        "X-Original-To": "patchwork@dpdk.org"
    },
    "content": "When sending multiple requests, rte_mp_request_sync\ncan succeed sending a few of those requests, but then\nfail on a later one and in the end return with rc=-1.\nThe upper layers - e.g. device hotplug - currently\nhandles this case as if no messages were sent and no\nmemory for response buffers was allocated, which is\nnot true. Fixed by always initializing message buffer\nto NULL and calling free everytime rte_mp_request_sync\nis used.\n\nv2:\n- resending as patchset to make it easier to review it.\n- changed commit message as requested.\n- added bugzilla id.\nBugzilla ID: 228\n\nHerakliusz Lipiec (8):\n  ipc: fix rte_mp_request_sync memleak\n  ipc: fix hotplug memleak\n  ipc: fix vdev memleak\n  ipc: fix vfio memleak\n  ipc: fix pdump memleak\n  ipc: fix tap pmd memleak\n  ipc: fix net/mlx4 memleak\n  ipc: fix net/mlx5 memleak\n\n drivers/bus/vdev/vdev.c                 | 3 +--\n drivers/net/mlx4/mlx4_mp.c              | 4 +++-\n drivers/net/mlx5/mlx5_mp.c              | 4 +++-\n drivers/net/tap/rte_eth_tap.c           | 2 ++\n lib/librte_eal/common/eal_common_proc.c | 6 +++---\n lib/librte_eal/common/hotplug_mp.c      | 2 ++\n lib/librte_eal/common/include/rte_eal.h | 3 ++-\n lib/librte_eal/linux/eal/eal_vfio.c     | 8 ++++----\n lib/librte_pdump/rte_pdump.c            | 2 +-\n 9 files changed, 21 insertions(+), 13 deletions(-)"
}