Searched full:freed (Results 1 – 25 of 161) sorted by relevance
1234567
| /Documentation/trace/ |
| D | events-kmem.rst | 64 When a page is freed directly by the caller, the only mm_page_free event
68 When pages are freed in batch, the also mm_page_free_batched is triggered.
70 freed in batch with a page list. Significant amounts of activity here could
90 When the per-CPU list is too full, a number of pages are freed, each one
101 can be allocated and freed on the same CPU through some algorithm change.
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 176 When the allocated memory is no longer needed it must be freed.
178 Objects allocated by `kmalloc` can be freed by `kfree` or `kvfree`. Objects
179 allocated by `kmem_cache_alloc` can be freed with `kmem_cache_free`, `kfree`
185 Memory allocated by `vmalloc` can be freed with `vfree` or `kvfree`.
186 Memory allocated by `kvmalloc` can be freed with `kvfree`.
187 Caches created by `kmem_cache_create` should be freed with
|
| D | debug-objects.rst | 19 - Usage of freed/destroyed objects
157 memory: either statically allocated objects or objects which are freed
174 This function is called before an object is freed.
177 the object can be freed. Free is not allowed for active objects. When
|
| D | assoc_array.rst | 81 script has been applied so that they can be freed later. The freeing is done
190 new object and the old one will be freed automatically.
262 returns ``false``, the object will be freed. If the ``iterator()`` function
509 The metadata blocks don't change otherwise. An old leaf won't be freed
513 metadata blocks don't change otherwise. The old leaf won't be freed until
552 Obsolete blocks and leaves are freed up after an RCU grace period has passed,
|
| /Documentation/sound/designs/ |
| D | jack-controls.rst | 30 Those kcontrols will be freed automatically when the Jack is freed.
|
| /Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 76 reservation must be restored when the huge page is freed. More
225 * freed, the reservation will be restored. */
237 for subpool accounting when the folio is freed.
267 when a huge page that has been instantiated is freed no adjustment is made
274 Huge pages are freed by free_huge_folio(). It is only passed a pointer
276 is freed, reservation accounting may need to be performed. This would
278 reserves, or the page is being freed on an error path where a global
419 be released and the reservation map freed. Before freeing the reservation
420 map, all the individual file_region structures must be freed. In this case
423 after the new file size must be freed. In addition, any file_region entries
[all …]
|
| D | free_page_reporting.rst | 22 page of a sufficiently high order is freed.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-auxiliary | 9 is requested and freed respectively for the PCI SF.
|
| D | sysfs-kernel-slab | 168 has been deactivated and contained free objects that were freed
201 slabs (not objects) are freed by rcu.
210 been freed in a full slab so that it had to added to its node's
230 The free_fastpath file shows how many objects have been freed
241 The free_frozen file shows how many objects have been freed to
253 been freed to a now-empty slab so that it had to be removed from
265 freed back to the page allocator. It can be written to clear
275 The free_slowpath file shows how many objects have been freed
437 are freed and the partial list is sorted so the slabs
|
| /Documentation/bpf/ |
| D | map_cgroup_storage.rst | 134 storage is freed upon detach.
147 shared, then attach type is simply ignored during comparison. Storage is freed
148 only when either the map or the cgroup attached to is being freed. Detaching
|
| /Documentation/driver-api/fpga/ |
| D | fpga-programming.rst | 23 allocated/freed by fpga_image_info_alloc() and freed with
|
| /Documentation/admin-guide/mm/ |
| D | hugetlbpage.rst | 81 returned to the huge page pool when freed by a task. A user with root
210 unused, they are freed back to the kernel's normal page pool.
221 Any free huge pages on the selected nodes will be freed back to the kernel's
229 increased sufficiently, or the surplus huge pages go out of use and are freed--
287 Whether huge pages are allocated and freed via the ``/proc`` interface or
289 NUMA nodes from which huge pages are allocated or freed are controlled by the
307 allocated nor freed on any node not included in the specified <node-list>.
425 As huge pages are allocated to the filesystem and freed, the reserve count
|
| D | concepts.rst | 163 memory management. The pages that can be freed at any time, either
170 buffers cannot be repurposed, and they remain pinned until freed by
220 enough memory will be freed to continue normal operation.
|
| /Documentation/dev-tools/ |
| D | kfence.rst | 137 freed by task 488 on cpu 2 at 33.871358s:
170 freed by task 490 on cpu 1 at 34.175348s:
244 allocated via KFENCE, including those already freed but protected.
289 the object is marked as freed. Any further access to the object causes a fault
290 and KFENCE reports a use-after-free access. Freed objects are inserted at the
291 tail of KFENCE's freelist, so that the least recently freed objects are reused
292 first, and the chances of detecting use-after-frees of recently freed objects
|
| D | kmemleak.rst | 7 with the difference that the orphan objects are not freed but only
69 Memory may be allocated or freed before kmemleak is initialised and
143 won't be freed when kmemleak is disabled, and those objects may occupy
220 block doesn't need to be freed (some cases in the init_call functions),
|
| D | kasan.rst | 213 Freed by task 815:
245 and a stack trace of where the object was freed (in case of a use-after-free
257 partially accessible, freed, or be a part of a redzone. KASAN uses the following
263 like redzones or freed memory (see mm/kasan/kasan.h).
297 Freed by task 136 on cpu 3 at 230.199335s:
336 Generic KASAN is the only mode that delays the reuse of freed objects via
369 reserved to tag freed memory regions.
390 reserved to tag freed memory regions.
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-close.rst | 34 freed. The device configuration remain unchanged.
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-func-close.rst | 34 are freed. The device configuration remain unchanged.
|
| D | request-func-close.rst | 34 are freed once all file descriptors associated with the request are closed
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-close.rst | 34 associated with the file descriptor are freed. However data format
|
| /Documentation/locking/ |
| D | percpu-rw-semaphore.rst | 21 The lock must be freed with percpu_free_rwsem to avoid memory leak.
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 153 When the parent sta_info structure is freed, first free the shadow
201 A shadow variable can be freed just before its parent object is freed,
|
| /Documentation/driver-api/tty/ |
| D | tty_driver.rst | 21 When the driver is about to be freed, tty_driver_kref_put() is called on that.
23 freed.
|
| /Documentation/networking/ |
| D | netdevices.rst | 17 If device has registered successfully, it will be freed on last use
22 private data which gets freed when the network device is freed. If
|
| /Documentation/driver-api/driver-model/ |
| D | devres.rst | 55 devres entry is freed.
100 freed whether initialization fails half-way or the device gets
208 when it is released or destroyed (removed and freed) - no reference
|
1234567