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 <elena.reshetova@intel.com>
Signed-off-by: Hans Liljestrand <ishkamiel@gmail.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: David Windsor <dwindsor@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
        unsigned char           window;
        struct timer_list       timer, dtimer;
        struct sock             *sk;            /* Backlink to socket */
-       atomic_t                refcount;
+       refcount_t              refcount;
 } ax25_cb;
 
 struct ax25_sock {
        hlist_for_each_entry(__ax25, list, ax25_node)
 
 #define ax25_cb_hold(__ax25) \
-       atomic_inc(&((__ax25)->refcount))
+       refcount_inc(&((__ax25)->refcount))
 
 static __inline__ void ax25_cb_put(ax25_cb *ax25)
 {
-       if (atomic_dec_and_test(&ax25->refcount)) {
+       if (refcount_dec_and_test(&ax25->refcount)) {
                kfree(ax25->digipeat);
                kfree(ax25);
        }
 
        if ((ax25 = kzalloc(sizeof(*ax25), GFP_ATOMIC)) == NULL)
                return NULL;
 
-       atomic_set(&ax25->refcount, 1);
+       refcount_set(&ax25->refcount, 1);
 
        skb_queue_head_init(&ax25->write_queue);
        skb_queue_head_init(&ax25->frag_queue);