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 143FDA0C43 for ; Fri, 1 Oct 2021 08:47:56 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 01A4640040; Fri, 1 Oct 2021 08:47:56 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id B20ED41109 for ; Fri, 1 Oct 2021 08:47:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633070874; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=K2jl5QVApKjf0iR6N6W001qytCWu8z+wugZpJw0ZHBs=; b=LdJOxUZDjAyDxbV6v6oV31aOeYrG732aSkm6Zx/+w9HrjEGL29qPPDd5p/Ss9AlBySJ7uE 0FZ7BSsMEt7mJVvqE5SMol6X8RZmlL1VHlOZPCwyR+/tZGQBfFr4gH2QaMw1ARAHB+nGBK 8l6GRf0Egc1O6nFW6ib8ZDy4+5uJEFg= Received: from mail-lf1-f72.google.com (mail-lf1-f72.google.com [209.85.167.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-114-e1t1KhViO_aEsnVyc7BITQ-1; Fri, 01 Oct 2021 02:47:51 -0400 X-MC-Unique: e1t1KhViO_aEsnVyc7BITQ-1 Received: by mail-lf1-f72.google.com with SMTP id v2-20020ac25582000000b003fd1c161a31so2111471lfg.15 for ; Thu, 30 Sep 2021 23:47:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=K2jl5QVApKjf0iR6N6W001qytCWu8z+wugZpJw0ZHBs=; b=Zh/LO24/Zqju7nNsgKIt9lK3f+6g9l0xrpYlQFHcvH6J6yJ5yMajQVnpbOvOCROelR wKHZcPh7H82r+eKP+Uf4tfDY4XqynxgESn89APhgK1/sFfocqE+DUQnUwhwVJAvvBvRJ 6faEB7V/reiQ13CTE+x9PhJqStmKIvl1PnSJTKwygu/YexAxQdxscvr00IDZkIo+D7hz 2J6ozEah2wLWk1d7Xrl9cNNlOKK0msOoy2Ek0nEAxFT5tO5s08ac2JVMJarDRS1mZyLH h88SuJORVtCV4eiIKbJpm2aaZckAaOrlCa/k9yFDUcAw7OM777ZrRdqFIJsiVAwdB6P3 BVmA== X-Gm-Message-State: AOAM530qrdCt43CQwRcB3499U+KR5EfeUHlA1V+hm508NxU5lKRne5CA 6StneIcbxY7nifLU+YEdlsnI0gIhYibLFaW7I+L7R1WdRy//nILr3InemXg3me37JUxKwWUDyJi xusPy0TCJ3iPxJdzO78ieI1U= X-Received: by 2002:a2e:9a98:: with SMTP id p24mr10395847lji.55.1633070869527; Thu, 30 Sep 2021 23:47:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyba8WnEAhSIAj7usKokyaYunwnm9wSlLD9Y11J9b++ZGViNNUY5s13WuILv4tfBAYZZazzRc6pgMOvQrufn10= X-Received: by 2002:a2e:9a98:: with SMTP id p24mr10395825lji.55.1633070869290; Thu, 30 Sep 2021 23:47:49 -0700 (PDT) MIME-Version: 1.0 References: <20210917082313.21934-1-david.marchand@redhat.com> <20210917082313.21934-2-david.marchand@redhat.com> In-Reply-To: From: David Marchand Date: Fri, 1 Oct 2021 08:47:38 +0200 Message-ID: To: Long Li Cc: "dev@dpdk.org" , "aconole@redhat.com" , "zhihongx.peng@intel.com" , "stable@dpdk.org" , Stephen Hemminger 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" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-stable] [PATCH 1/3] bus/vmbus: fix leak on device scan X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Thu, Sep 30, 2021 at 9:14 PM Long Li wrote: > > rte_device name only points at some location where the name is stored. > > In general this storage is in the bus object or (in some buses) the dev= arg that > > resulted in the rte_device object creation. > > > > If we won't store the name in the bus object, then we lose the ability = to > > release the name later. > > This is probably fine as long as we never release rte_vmbus_device obje= cts > > which is the case atm. > > But I don't understand why vmbus should be an exception when comparing > > to other buses. > > I don=E2=80=99t understand why you want to put a name there if it's never= used outside vmbus_scan_one(). Since you don't care about releasing rte_vmbus_device objects, I'll rework as you suggest. --=20 David Marchand