On Tue, 18 Jul 2017, Reshetova, Elena wrote:
> > On Tue, 18 Jul 2017, Reshetova, Elena wrote:
> >
> > > > On Tue, 18 Jul 2017, Elena Reshetova wrote:
> > > >
> > > > > The below script can be used to detect potential misusage
> > > > > of atomic_t type and API for reference counting purposes.
>
> On Tue, 18 Jul 2017, Reshetova, Elena wrote:
>
> > > On Tue, 18 Jul 2017, Elena Reshetova wrote:
> > >
> > > > The below script can be used to detect potential misusage
> > > > of atomic_t type and API for reference counting purposes.
> > > > Now when we have a dedicated refcount_t type and API
On Tue, 18 Jul 2017, Reshetova, Elena wrote:
> > On Tue, 18 Jul 2017, Elena Reshetova wrote:
> >
> > > The below script can be used to detect potential misusage
> > > of atomic_t type and API for reference counting purposes.
> > > Now when we have a dedicated refcount_t type and API with
> > > s
> On Tue, 18 Jul 2017, Elena Reshetova wrote:
>
> > The below script can be used to detect potential misusage
> > of atomic_t type and API for reference counting purposes.
> > Now when we have a dedicated refcount_t type and API with
> > security protection implemented, people should be using it
>
On Tue, 18 Jul 2017, Elena Reshetova wrote:
> The below script can be used to detect potential misusage
> of atomic_t type and API for reference counting purposes.
> Now when we have a dedicated refcount_t type and API with
> security protection implemented, people should be using it
> instead.
The below script can be used to detect potential misusage
of atomic_t type and API for reference counting purposes.
Now when we have a dedicated refcount_t type and API with
security protection implemented, people should be using it
instead.
Currently it still reports many occurences since we are
6 matches
Mail list logo