atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
> On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote:
> >> - ASSERT(atomic_read(>t_ref) > 0);
> >> - atomic_inc(>t_ref);
> >> + ASSERT(refcount_read(>t_ref) > 0);
> >> + refcount_inc(>t_ref);
> >
> > With strict refcount semantics refcount_inc should
> On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote:
> >> - ASSERT(atomic_read(>t_ref) > 0);
> >> - atomic_inc(>t_ref);
> >> + ASSERT(refcount_read(>t_ref) > 0);
> >> + refcount_inc(>t_ref);
> >
> > With strict refcount semantics refcount_inc should check that
> > the count
On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote:
>> - ASSERT(atomic_read(>t_ref) > 0);
>> - atomic_inc(>t_ref);
>> + ASSERT(refcount_read(>t_ref) > 0);
>> + refcount_inc(>t_ref);
>
> With strict refcount semantics refcount_inc should check that
> the
On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote:
>> - ASSERT(atomic_read(>t_ref) > 0);
>> - atomic_inc(>t_ref);
>> + ASSERT(refcount_read(>t_ref) > 0);
>> + refcount_inc(>t_ref);
>
> With strict refcount semantics refcount_inc should check that
> the count is larger than
> - ASSERT(atomic_read(>t_ref) > 0);
> - atomic_inc(>t_ref);
> + ASSERT(refcount_read(>t_ref) > 0);
> + refcount_inc(>t_ref);
With strict refcount semantics refcount_inc should check that
the count is larger than 0, otherwise we'd need to use
recount_inc_not_zero or whatever
> - ASSERT(atomic_read(>t_ref) > 0);
> - atomic_inc(>t_ref);
> + ASSERT(refcount_read(>t_ref) > 0);
> + refcount_inc(>t_ref);
With strict refcount semantics refcount_inc should check that
the count is larger than 0, otherwise we'd need to use
recount_inc_not_zero or whatever
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
14 matches
Mail list logo