/linux-6.1.9/net/sched/ ! |
D | sch_sfb.c | 89 u32 hashes[2]; member 104 return sfb_skb_cb(skb)->hashes[slot]; in sfb_hash() 142 sfbhash = cb->hashes[0]; in increment_qlen() 146 sfbhash = cb->hashes[1]; in increment_qlen() 328 sfb_skb_cb(skb)->hashes[slot] = sfbhash; in sfb_enqueue() 346 sfb_skb_cb(skb)->hashes[slot] = 0; in sfb_enqueue() 361 sfb_skb_cb(skb)->hashes[slot] = sfbhash; in sfb_enqueue()
|
/linux-6.1.9/drivers/net/usb/ ! |
D | sr9700.c | 264 u8 *hashes = (u8 *)&dev->data; in sr9700_set_multicast() local 268 memset(hashes, 0x00, SR_MCAST_SIZE); in sr9700_set_multicast() 270 hashes[SR_MCAST_SIZE - 1] |= SR_MCAST_ADDR_FLAG; in sr9700_set_multicast() 281 hashes[crc >> 3] |= 1 << (crc & 0x7); in sr9700_set_multicast() 285 sr_write_async(dev, SR_MAR, SR_MCAST_SIZE, hashes); in sr9700_set_multicast()
|
D | dm9601.c | 295 u8 *hashes = (u8 *) & dev->data; in dm9601_set_multicast() local 298 memset(hashes, 0x00, DM_MCAST_SIZE); in dm9601_set_multicast() 299 hashes[DM_MCAST_SIZE - 1] |= 0x80; /* broadcast address */ in dm9601_set_multicast() 311 hashes[crc >> 3] |= 1 << (crc & 0x7); in dm9601_set_multicast() 315 dm_write_async(dev, DM_MCAST_ADDR, DM_MCAST_SIZE, hashes); in dm9601_set_multicast()
|
/linux-6.1.9/Documentation/pcmcia/ ! |
D | devicetable.rst | 10 - product ID strings _and_ hashes of these strings 18 hashes of the string to the macro, e.g. if you want to match the product ID
|
/linux-6.1.9/Documentation/admin-guide/device-mapper/ ! |
D | verity.rst | 51 inaccessible. You can place hashes to the same partition as data, in this 52 case hashes are placed after <num_data_blocks>. 145 If verity hashes are in cache, verify data blocks in kernel tasklet instead 157 After instantiation, all hashes will be verified on-demand during 162 Cryptographic hashes are used to assert the integrity of the device on a 164 into the page cache. Block hashes are stored linearly, aligned to the nearest 181 selected cryptographic digest algorithm. The hashes are linearly-ordered in
|
/linux-6.1.9/fs/xfs/scrub/ ! |
D | dabtree.h | 13 xfs_dahash_t hashes[XFS_DA_NODE_MAXDEPTH]; member
|
D | dabtree.c | 107 if (hash < ds->hashes[level]) in xchk_da_btree_hash() 109 ds->hashes[level] = hash; in xchk_da_btree_hash()
|
/linux-6.1.9/security/apparmor/ ! |
D | Kconfig | 60 bool "Enable introspection of sha1 hashes for loaded profiles" 67 hashes is available to userspace via the apparmor 78 is enabled by default. The generation of sha1 hashes for
|
/linux-6.1.9/Documentation/ABI/testing/ ! |
D | debugfs-turris-mox-rwtm | 10 (since this is intended for SHA-512 hashes).
|
/linux-6.1.9/fs/reiserfs/ ! |
D | Makefile | 10 hashes.o tail_conversion.o journal.o resize.o \
|
D | README | 94 Yura helps with benchmarking, coding hashes, and block pre-allocation
|
/linux-6.1.9/Documentation/devicetree/bindings/crypto/ ! |
D | img-hash.txt | 4 SHA1, SHA224, SHA256 and MD5 hashes
|
/linux-6.1.9/Documentation/virt/kvm/s390/ ! |
D | s390-pv-boot.rst | 22 hashes, to ensure integrity. Afterwards KVM can run the PVM via the 56 The PV header contains the keys and hashes, which the UV will use to
|
/linux-6.1.9/certs/ ! |
D | Makefile | 16 $(AWK) -f $(srctree)/$(src)/check-blacklist-hashes.awk $(CONFIG_SYSTEM_BLACKLIST_HASH_LIST) >&2; \
|
D | Kconfig | 106 If set, this option should be the filename of a list of hashes in the 111 Certificate hashes can be generated with
|
/linux-6.1.9/Documentation/filesystems/ ! |
D | fsverity.rst | 47 (logging file hashes before use). 265 the same order that their hashes are themselves hashed. 359 This section describes how fs-verity hashes the file contents using a 375 level of hashes. Then, the hashes in this first level are grouped 377 these blocks are hashed, producing the second level of hashes. This 519 when the file is, since it contains hashes of the plaintext data. 671 hashed and what to do with those hashes, such as log them, 675 to full file hashes, for those who want the performance and 683 hashes in the Merkle tree, which is stored on-disk? 744 - A way to maintain consistency between the data and hashes, [all …]
|
D | ubifs-authentication.rst | 262 data, the hashes of their parent index nodes thus cover all the file contents 266 Whenever a file is read, UBIFS can verify the hashes from each leaf node up to 319 hashes to index nodes does not change this since each hash will be persisted
|
/linux-6.1.9/security/integrity/ ! |
D | Kconfig | 95 hashes to the .blacklist keyring for powerpc based platforms.
|
/linux-6.1.9/Documentation/networking/ ! |
D | nexthop-group-resilient.rst | 16 hashes to each next hop in the group, and then selects the next hop by 53 algorithm, the range of hashes associated with a next hop must be
|
/linux-6.1.9/tools/perf/Documentation/ ! |
D | perf-script-python.txt | 248 (implemented in Core.py) that implements Perl's 'autovivifying' hashes 249 in Python i.e. with autovivifying hashes, you can assign nested hash 599 dictionary that implements Perl's 'autovivifying' hashes in Python 600 i.e. with autovivifying hashes, you can assign nested hash values
|
/linux-6.1.9/fs/cifs/ ! |
D | Kconfig | 77 man-in-the-middle attacks and stronger crypto hashes, so the use
|
/linux-6.1.9/Documentation/ABI/stable/ ! |
D | sysfs-class-tpm | 106 1.2 chips, PCRs represent SHA-1 hashes, which are 20 bytes
|
/linux-6.1.9/Documentation/timers/ ! |
D | hrtimers.rst | 92 such as radix trees and hashes, we chose the red black tree as the basic
|
/linux-6.1.9/drivers/crypto/ ! |
D | Kconfig | 565 (default), hashes-only, or skciphers-only. 601 Enable hashes/HMAC algorithms only:
|
/linux-6.1.9/Documentation/x86/ ! |
D | intel_txt.rst | 76 hashes, these measurement changes are difficult to assess or
|