Home
last modified time | relevance | path

Searched refs:wipe (Results 1 – 15 of 15) sorted by relevance

/linux-6.15/fs/ocfs2/
H A Dinode.c903 int *wipe) in ocfs2_query_inode_wipe() argument
909 *wipe = 0; in ocfs2_query_inode_wipe()
985 *wipe = 1; in ocfs2_query_inode_wipe()
1008 int wipe, status; in ocfs2_delete_inode() local
1076 status = ocfs2_query_inode_wipe(inode, di_bh, &wipe); in ocfs2_delete_inode()
1077 if (!wipe || status < 0) { in ocfs2_delete_inode()
/linux-6.15/drivers/hid/
H A Dhid-roccat-kone.h155 struct_group(wipe,
H A Dhid-roccat-kone.c866 memset(&event->wipe, 0, sizeof(event->wipe)); in kone_raw_event()
/linux-6.15/Documentation/devicetree/bindings/watchdog/
H A Dti,rti-wdt.yaml46 is supposed to wipe the whole memory region. Surely, if this
/linux-6.15/Documentation/driver-api/nvdimm/
H A Dsecurity.rst32 overwrite <keyid> - wipe the entire nvdimm.
/linux-6.15/drivers/md/
H A Ddm-crypt.c110 int (*wipe)(struct crypt_config *cc); member
1100 .wipe = crypt_iv_lmk_wipe,
1109 .wipe = crypt_iv_tcw_wipe,
1127 .wipe = crypt_iv_elephant_wipe,
2696 if (cc->iv_gen_ops && cc->iv_gen_ops->wipe) { in crypt_wipe_key()
2697 r = cc->iv_gen_ops->wipe(cc); in crypt_wipe_key()
/linux-6.15/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-codec.rst1517 - Slice groups grow in wipe scan pattern from top to bottom.
1536 Specifies a direction of the slice group change for raster and wipe
1546 - Raster scan or wipe right.
1548 - Reverse raster scan or wipe left.
1553 Specifies the size of the first slice group for raster and wipe map.
/linux-6.15/Documentation/admin-guide/
H A Dbcache.rst259 Now we can wipe it::
272 H) Stop/free a registered bcache to wipe and/or recreate it
H A Dkernel-parameters.txt6148 used for systems that do not wipe the RAM, and this command
7301 is set up to not wipe memory. For instance, CONFIG_RESET_ATTACK_MITIGATION
/linux-6.15/Documentation/security/
H A Dself-protection.rst306 syscall return (``CONFIG_GCC_PLUGIN_STACKLEAK``), wipe heap memory on a
H A Dipe.rst46 modify filesystem offline, the attacker could wipe all the xattrs -
/linux-6.15/Documentation/filesystems/
H A Dfscrypt.rst114 FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS ioctl) can wipe a master
128 - The kernel cannot magically wipe copies of the master key(s) that
129 userspace might have as well. Therefore, userspace must wipe all
H A Dproc.rst599 wf wipe on fork
/linux-6.15/Documentation/ABI/stable/
H A Dsysfs-block746 contiguous blocks on storage. This can be used to wipe areas on
/linux-6.15/Documentation/process/
H A Dmaintainer-pgp-guide.rst453 the Admin PIN and the Reset Code (which allows you to completely wipe