From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3E1BEA0548; Mon, 14 Jun 2021 11:11:59 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AC7464067A; Mon, 14 Jun 2021 11:11:57 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id DE4004003F for ; Mon, 14 Jun 2021 11:11:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623661914; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=IQOGuTfRII8FU7WvJCu93s0itUzJ0fobtyR3u+R9/lw=; b=GkPyoIExpEs9x+OpNp7gaTfDA07lbhAeoH7ifvpaakeKocF7HubzXsNhgh30we+89mMo57 23juYrrofOkd1QaTJy2redrzaHS8dDsTMUK5rgUDM03kC5/YS0AAmFhHiKHL4Y2DMnIfAE +snG9+J0vliynyhTlVKOUVdyweYNSzI= Received: from mail-ua1-f72.google.com (mail-ua1-f72.google.com [209.85.222.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-245-S4y9TecYMs2wNq_myX-rwQ-1; Mon, 14 Jun 2021 05:11:53 -0400 X-MC-Unique: S4y9TecYMs2wNq_myX-rwQ-1 Received: by mail-ua1-f72.google.com with SMTP id g17-20020ab072d10000b029024b77c1dbb6so5879297uap.1 for ; Mon, 14 Jun 2021 02:11:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IQOGuTfRII8FU7WvJCu93s0itUzJ0fobtyR3u+R9/lw=; b=gcyqy4bFOEJrPLnpvVHsVCqiA5+To50YSCk0JY2oS1G1jqwBnTS4mArUz6KxFQjvq6 k0p7ApLG01SpUcS0vK+vxBNIWLlqmJbI1eXsKGgkgYc+aviOs+7RyAH2uqbHqVCbXD5D QOU6G0g3Sc1H5SOmfA/oM/VAOzHTh/EeXogY+BO7CISBXRdixtnYhBa1dRpyqo7WVBJf 2ywzDJkT9ticZ6629jQEjlnyK18cqmkhwR4xdeQ6ZVjdAGTne6XRv3T4lY6XJC+isYvS OgvsSoMZdnNNtWV2VtPrskmSqntQtOyGb4Q8FknZVX3QcjqQYGWgj85CnnXpT2q57579 5y4Q== X-Gm-Message-State: AOAM533JJ2QJFamm3uzpNCKnBuLrAR9oOwIA1z5JYI+idiT9sFTneHBO m9uo+M//73Tr4afhPeV1vKkLe+32jwBhO0KCAXaxXicd87GaA+sAP/LusHd6M6oBs3leacMtSSo X5W+Rd0Iru2QmSTkLzRM= X-Received: by 2002:a05:6102:243c:: with SMTP id l28mr4180323vsi.27.1623661912704; Mon, 14 Jun 2021 02:11:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxrbWdT4T723TaT6bqQ3RgjZthbctmfT3nLhv8dpOApZkgGj/aafbv4PQ09JDT2iLiqOdzbpZBOsvtvNSPta6w= X-Received: by 2002:a05:6102:243c:: with SMTP id l28mr4180319vsi.27.1623661912528; Mon, 14 Jun 2021 02:11:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Mon, 14 Jun 2021 11:11:41 +0200 Message-ID: To: Owen Hilyard Cc: dev , dpdklab , Gaetan Rivet Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] Memory leak in rte_pci_scan X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Jun 8, 2021 at 8:48 PM Owen Hilyard wrote: > > Hello All, > > As part of the community lab's work to deploy static analysis tools, we've > been doing test runs of the various tools. One of the problems we found is > that rte_pci_scan leaks 214368 Bytes every time it is run. There are also I suspect the "leak" is on pci device objects that are not released unless hot(un)plugging. Cc: Gaetan. > numerous (180856) instances of the error message "EAL: recvmsg failed, Bad > file descriptor". Attached is the log from running the fast-tests suite > with ASAN enabled, and a 10-second timeout. The real timeout seems to be > the timeout argument multiplied by 10, making this really a 100-second > timeout. It is attached as a google drive link since the log itself is too > large for the mailing list. Those logs come from the mp channel. At cleanup the rte_mp_handle control thread is sleeping on the mp socket. The thread serving rte_eal_cleanup shutdowns this socket fd, and the control thread will spew the log messages you saw. I'll send a patch. -- David Marchand