| /linux-6.1.9/net/sunrpc/auth_gss/ |
| D | gss_krb5_seqnum.c | 49 unsigned char *plain; in krb5_make_seq_num() local
52 plain = kmalloc(8, GFP_KERNEL); in krb5_make_seq_num()
53 if (!plain) in krb5_make_seq_num()
56 plain[0] = (unsigned char) (seqnum & 0xff); in krb5_make_seq_num()
57 plain[1] = (unsigned char) ((seqnum >> 8) & 0xff); in krb5_make_seq_num()
58 plain[2] = (unsigned char) ((seqnum >> 16) & 0xff); in krb5_make_seq_num()
59 plain[3] = (unsigned char) ((seqnum >> 24) & 0xff); in krb5_make_seq_num()
61 plain[4] = direction; in krb5_make_seq_num()
62 plain[5] = direction; in krb5_make_seq_num()
63 plain[6] = direction; in krb5_make_seq_num()
[all …]
|
| /linux-6.1.9/tools/testing/crypto/chacha20-s390/ |
| D | test-cipher.c | 51 static int test_lib_chacha(u8 *revert, u8 *cipher, u8 *plain) in test_lib_chacha() argument
72 chacha_crypt_arch(chacha_state, cipher, plain, data_size, 20); in test_lib_chacha()
126 static int test_skcipher(char *name, u8 *revert, u8 *cipher, u8 *plain) in test_skcipher() argument
173 sg_init_one(&sk.sginp, plain, data_size); in test_skcipher()
238 u8 *plain = NULL, *revert = NULL; in chacha_s390_test_init() local
246 plain = vmalloc(data_size); in chacha_s390_test_init()
247 if (!plain) { in chacha_s390_test_init()
252 memset(plain, 'a', data_size); in chacha_s390_test_init()
253 get_random_bytes(plain, (data_size > 256 ? 256 : data_size)); in chacha_s390_test_init()
278 16, 1, plain, in chacha_s390_test_init()
[all …]
|
| /linux-6.1.9/lib/ |
| D | Kconfig.kcsan | 36 The compiler instruments plain compound read-write operations
38 distinguish them from other plain accesses. This is currently
198 plain accesses by default (depending on !KCSAN_STRICT) reduce the
215 bool "Assume that plain aligned writes up to word size are atomic"
219 Assume that plain aligned writes up to word size are atomic by
222 races due to conflicts where the only plain accesses are aligned
223 writes up to word size: conflicts between marked reads and plain
225 notice that data races between two conflicting plain aligned writes
233 additional filtering. Conflicting marked atomic reads and plain
235 plain reads and marked writes to result in "unknown origin" reports.
[all …]
|
| D | test_printf.c | 315 plain(void) in plain() function
774 plain(); in test_pointer()
|
| /linux-6.1.9/tools/memory-model/Documentation/ |
| D | access-marking.txt | 33 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
39 preferable to data_race(), which in turn is usually preferable to plain
44 KCSAN will complain about many types of data races involving plain
54 data_race() and even plain C-language accesses is preferable to
85 concurrently with updates to x. Then using plain C-language writes
95 In theory, plain C-language loads can also be used for this use case.
119 In theory, plain C-language loads can also be used for this use case.
140 In theory, plain C-language loads can also be used for this use case.
166 Here are some example situations where plain C-language accesses should
190 by default, refraining from flagging plain C-language stores:
[all …]
|
| D | explanation.txt | 931 Plain-coherence: This requires that plain memory accesses
938 "rcu" and "plain-coherence" axioms are specific to the LKMM.
1984 accesses such as x or y = 0 are simply called "plain" accesses.
1986 Early versions of the LKMM had nothing to say about plain accesses.
1988 by plain accesses are not concurrently read or written by any other
1990 of transformations or optimizations of code containing plain accesses,
2016 But since P0's load from x is a plain access, the compiler may decide
2038 doesn't try to predict all possible outcomes of code containing plain
2051 3. at least one of them is plain,
2163 are plain. Now, although we have not said so explicitly, up to this
[all …]
|
| /linux-6.1.9/Documentation/fb/ |
| D | s3fb.rst | 19 I tested s3fb on Trio64 (plain, V+ and V2/DX) and Virge (plain, VX, DX),
40 hardware, i get best results from plain S3 Trio32 card - about 75 MHz). This
|
| /linux-6.1.9/tools/memory-model/ |
| D | linux-kernel.cat | 163 (* Warn about plain writes and marked accesses in the same region *)
173 (* Boundaries for lifetimes of plain accesses *)
181 (* Visibility and executes-before for plain accesses *)
191 (* Coherence requirements for plain accesses *)
195 empty (wr-incoh | rw-incoh | ww-incoh) as plain-coherence
|
| D | linux-kernel.bell | 81 (* Compute marked and plain memory accesses *)
|
| /linux-6.1.9/net/mac80211/ |
| D | fils_aead.c | 67 const u8 *plain, size_t plain_len, in aes_siv_encrypt() argument
81 addr[num_elem] = plain; in aes_siv_encrypt()
101 tmp = kmemdup(plain, plain_len, GFP_KERNEL); in aes_siv_encrypt()
|
| /linux-6.1.9/Documentation/devicetree/bindings/pci/ |
| D | faraday,ftpci100.yaml | 15 plain and dual PCI. The plain version embeds a cascading interrupt controller
21 The plain variant has 128MiB of non-prefetchable memory space, whereas the
|
| /linux-6.1.9/Documentation/dev-tools/ |
| D | kcsan.rst | 124 * ``CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC``: Assume that plain aligned writes
127 causes KCSAN to not report data races due to conflicts where the only plain
192 *plain access*; they *conflict* if both access the same memory location, and at
253 compiler instrumenting plain accesses. For each instrumented plain access:
264 To detect data races between plain and marked accesses, KCSAN also annotates
276 Each plain memory access for which a watchpoint is set up, is also selected for
312 "prefetch" accesses. Also recall that watchpoints are only set up for plain
|
| /linux-6.1.9/Documentation/core-api/ |
| D | protection-keys.rst | 75 behavior of a plain mprotect(). For instance if you do this::
98 the plain mprotect() permissions are violated.
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-numa | 14 characteristics instead of plain NUMA systems where
|
| /linux-6.1.9/crypto/ |
| D | ccm.c | 168 static int crypto_ccm_auth(struct aead_request *req, struct scatterlist *plain, in crypto_ccm_auth() argument
215 if (plain) in crypto_ccm_auth()
216 sg_chain(sg, 2, plain); in crypto_ccm_auth()
217 plain = sg; in crypto_ccm_auth()
221 ahash_request_set_crypt(ahreq, plain, pctx->odata, cryptlen); in crypto_ccm_auth()
|
| /linux-6.1.9/arch/arm/nwfpe/ |
| D | entry.S | 104 @ plain LDR instruction. Weird, but it seems harmless.
|
| /linux-6.1.9/fs/autofs/ |
| D | Kconfig | 11 transitioned to just plain AUTOFS_FS.
|
| /linux-6.1.9/Documentation/admin-guide/ |
| D | security-bugs.rst | 29 Please send plain text emails without attachments where possible.
34 reproduction steps, and follow it with a proposed fix, all in plain text.
|
| /linux-6.1.9/Documentation/translations/zh_CN/admin-guide/ |
| D | tainted-kernels.rst | 56 `git.kernel.org <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/tools/deb…
|
| D | reporting-regressions.rst | 367 …https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/translation…
|
| /linux-6.1.9/Documentation/translations/zh_TW/admin-guide/ |
| D | tainted-kernels.rst | 59 `git.kernel.org <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/tools/deb…
|
| /linux-6.1.9/Documentation/hwmon/ |
| D | asb100.rst | 31 3 (i.e. one setting controls both.) If you have a plain ASB100, the PWM
|
| /linux-6.1.9/Documentation/networking/ |
| D | ieee802154.rst | 20 - IEEE 802.15.4 layer; We have chosen to use plain Berkeley socket API,
82 code via plain sk_buffs. On skb reception skb->cb must contain additional
|
| /linux-6.1.9/arch/arm/boot/dts/ |
| D | ste-href-family-pinctrl.dtsi | 196 * These are plain GPIO pins used by WLAN
|
| /linux-6.1.9/Documentation/translations/zh_TW/process/ |
| D | email-clients.rst | 36 接收附件，但是附件的內容格式應該是"text/plain"。然而，附件一般是不贊成的，
|