From: "Hu, Jiayu" <jiayu.hu@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev <dev@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>,
"Ding, Xuan" <xuan.ding@intel.com>,
"Jiang, Cheng1" <cheng1.jiang@intel.com>,
"Pai G, Sunil" <sunil.pai.g@intel.com>
Subject: RE: [PATCH v2] vhost: add runtime locking check in unsafe APIs
Date: Wed, 11 May 2022 07:49:16 +0000 [thread overview]
Message-ID: <270b5b8673464460bdfd87b1f4bd9929@intel.com> (raw)
In-Reply-To: <CAJFAV8zSfcPQwBA1=6B76CgWcp0jkZ_U5i2OGxac52+Ary9arQ@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Wednesday, May 11, 2022 3:35 PM
> To: Maxime Coquelin <maxime.coquelin@redhat.com>
> Cc: dev <dev@dpdk.org>; Xia, Chenbo <chenbo.xia@intel.com>; Ding, Xuan
> <xuan.ding@intel.com>; Hu, Jiayu <jiayu.hu@intel.com>; Jiang, Cheng1
> <cheng1.jiang@intel.com>; Pai G, Sunil <sunil.pai.g@intel.com>
> Subject: Re: [PATCH v2] vhost: add runtime locking check in unsafe APIs
>
> On Wed, May 11, 2022 at 8:58 AM Maxime Coquelin
> <maxime.coquelin@redhat.com> wrote:
> >
> > This patch adds runtime checks in unsafe Vhost async APIs, to ensure
> > the access lock is taken.
> >
> > The detection won't work every time, as another thread could take the
> > lock, but it would help to detect misuse of these unsafe API.
> >
> > Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Reviewed-by: Jiayu Hu <jiayu.hu@intel.com>
Thanks,
Jiayu
>
>
> --
> David Marchand
next prev parent reply other threads:[~2022-05-11 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 6:58 Maxime Coquelin
2022-05-11 7:35 ` David Marchand
2022-05-11 7:49 ` Hu, Jiayu [this message]
2022-05-11 13:58 ` Xia, Chenbo
2022-05-17 13:23 ` Maxime Coquelin
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=270b5b8673464460bdfd87b1f4bd9929@intel.com \
--to=jiayu.hu@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cheng1.jiang@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=sunil.pai.g@intel.com \
--cc=xuan.ding@intel.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).