From: David Marchand <david.marchand@redhat.com>
To: Xueming Li <xuemingl@nvidia.com>, Gaetan Rivet <grive@u256.net>
Cc: dpdk stable <stable@dpdk.org>, dev <dev@dpdk.org>,
Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [PATCH] devargs: fix leak on hotplug failure
Date: Thu, 12 May 2022 09:06:23 +0200 [thread overview]
Message-ID: <CAJFAV8ywLwaObbWmPC+uhgngiB-SiiELDJRKtkYmmyAOF0fuRw@mail.gmail.com> (raw)
In-Reply-To: <20220414112756.26119-1-david.marchand@redhat.com>
On Thu, Apr 14, 2022 at 1:28 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Caught by ASan, if a secondary process tried to attach a device with an
> incorrect driver name, devargs was leaked.
>
> Fixes: 64051bb1f144 ("devargs: unify scratch buffer storage")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Review please?
--
David Marchand
next prev parent reply other threads:[~2022-05-12 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 11:27 David Marchand
2022-05-12 7:06 ` David Marchand [this message]
2022-05-19 16:21 ` David Marchand
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=CAJFAV8ywLwaObbWmPC+uhgngiB-SiiELDJRKtkYmmyAOF0fuRw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=mdr@ashroe.eu \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).