Lines Matching refs:kref_put
65 2) When you are done with a pointer, you must call kref_put()::
67 kref_put(&data->refcount, data_release);
77 where a kref_put() cannot occur during the kref_get(), and the
95 kref_put(&data->refcount, data_release);
112 kref_put(&data->refcount, data_release);
120 kref_put(&data->refcount, data_release);
125 data, the kref_put() handles knowing when the data is not referenced
131 In the above example, kref_put() will be called 2 times in both success
161 kref_put(&obj->ref, obj_cleanup);
207 kref_put(&entry->refcount, release_entry);
211 The kref_put() return value is useful if you do not want to hold the
214 pointless to do so). You could use kref_put() as follows::
218 /* All work is done after the return from kref_put(). */
224 if (kref_put(&entry->refcount, release_entry)) {
265 kref_put(&entry->refcount, release_entry);
268 Which is useful to remove the mutex lock around kref_put() in put_entry(), but
316 kref_put(&entry->refcount, release_entry_rcu);