| /linux-6.12.1/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.12.1/lib/ |
| D | Kconfig.kcsan | 37 The compiler instruments plain compound read-write operations
39 distinguish them from other plain accesses. This is currently
199 plain accesses by default (depending on !KCSAN_STRICT) reduce the
216 bool "Assume that plain aligned writes up to word size are atomic"
220 Assume that plain aligned writes up to word size are atomic by
223 races due to conflicts where the only plain accesses are aligned
224 writes up to word size: conflicts between marked reads and plain
226 notice that data races between two conflicting plain aligned writes
234 additional filtering. Conflicting marked atomic reads and plain
236 plain reads and marked writes to result in "unknown origin" reports.
[all …]
|
| D | test_printf.c | 302 plain(void) in plain() function
759 plain(); in test_pointer()
|
| /linux-6.12.1/tools/memory-model/litmus-tests/ |
| D | dep+plain.litmus | 1 C dep+plain
6 * This litmus test demonstrates that in LKMM, plain accesses
|
| /linux-6.12.1/drivers/gpu/drm/ci/xfails/ |
| D | rockchip-rk3399-fails.txt | 58 kms_flip@plain-flip-fb-recreate,Fail
59 kms_flip@plain-flip-fb-recreate-interruptible,Fail
60 kms_flip@plain-flip-ts-check,Fail
61 kms_flip@plain-flip-ts-check-interruptible,Fail
|
| D | vkms-none-flakes.txt | 34 kms_flip@plain-flip-fb-recreate-interruptible
41 kms_flip@plain-flip-ts-check
48 kms_flip@plain-flip-ts-check-interruptible
|
| D | virtio_gpu-none-fails.txt | 153 kms_flip@plain-flip-fb-recreate,Fail
154 kms_flip@plain-flip-fb-recreate-interruptible,Fail
155 kms_flip@plain-flip-ts-check,Fail
156 kms_flip@plain-flip-ts-check-interruptible,Fail
|
| /linux-6.12.1/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.12.1/tools/memory-model/Documentation/ |
| D | access-marking.txt | 39 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
45 preferable to data_race(), which in turn is usually preferable to plain
50 KCSAN will complain about many types of data races involving plain
60 data_race() and even plain C-language accesses is preferable to
91 concurrently with updates to x. Then using plain C-language writes
101 In theory, plain C-language loads can also be used for this use case.
125 In theory, plain C-language loads can also be used for this use case.
146 In theory, plain C-language loads can also be used for this use case.
172 Here are some example situations where plain C-language accesses should
196 by default, refraining from flagging plain C-language stores:
[all …]
|
| D | explanation.txt | 933 Plain-coherence: This requires that plain memory accesses
940 "rcu" and "plain-coherence" axioms are specific to the LKMM.
2171 accesses such as x or y = 0 are simply called "plain" accesses.
2173 Early versions of the LKMM had nothing to say about plain accesses.
2175 by plain accesses are not concurrently read or written by any other
2177 of transformations or optimizations of code containing plain accesses,
2203 But since P0's load from x is a plain access, the compiler may decide
2225 doesn't try to predict all possible outcomes of code containing plain
2238 3. at least one of them is plain,
2350 are plain. Now, although we have not said so explicitly, up to this
[all …]
|
| /linux-6.12.1/tools/memory-model/ |
| D | linux-kernel.cat | 176 (* Warn about plain writes and marked accesses in the same region *)
186 (* Boundaries for lifetimes of plain accesses *)
194 (* Visibility and executes-before for plain accesses *)
204 (* Coherence requirements for plain accesses *)
208 empty (wr-incoh | rw-incoh | ww-incoh) as plain-coherence
|
| D | linux-kernel.bell | 75 (* Compute marked and plain memory accesses *)
80 (* Redefine dependencies to include those carried through plain accesses *)
|
| /linux-6.12.1/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.12.1/tools/testing/selftests/bpf/progs/ |
| D | local_kptr_stash.c | 53 struct plain_local __kptr *plain; member
146 res = bpf_kptr_xchg(&mapval->plain, res); in stash_plain()
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | kcsan.rst | 134 * ``CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC``: Assume that plain aligned writes
137 causes KCSAN to not report data races due to conflicts where the only plain
202 *plain access*; they *conflict* if both access the same memory location, and at
263 compiler instrumenting plain accesses. For each instrumented plain access:
274 To detect data races between plain and marked accesses, KCSAN also annotates
286 Each plain memory access for which a watchpoint is set up, is also selected for
322 "prefetch" accesses. Also recall that watchpoints are only set up for plain
|
| /linux-6.12.1/crypto/ |
| D | ccm.c | 169 static int crypto_ccm_auth(struct aead_request *req, struct scatterlist *plain, in crypto_ccm_auth() argument
216 if (plain) in crypto_ccm_auth()
217 sg_chain(sg, 2, plain); in crypto_ccm_auth()
218 plain = sg; in crypto_ccm_auth()
222 ahash_request_set_crypt(ahreq, plain, odata, cryptlen); in crypto_ccm_auth()
|
| /linux-6.12.1/drivers/gpu/drm/radeon/ |
| D | Kconfig | 32 run the Radeon in plain VGA mode.
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-numa | 14 characteristics instead of plain NUMA systems where
|
| /linux-6.12.1/Documentation/core-api/ |
| D | protection-keys.rst | 93 behavior of a plain mprotect(). For instance if you do this::
116 the plain mprotect() permissions are violated.
|
| /linux-6.12.1/Documentation/process/ |
| 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.12.1/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…
|
| /linux-6.12.1/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.12.1/Documentation/hwmon/ |
| D | asb100.rst | 31 3 (i.e. one setting controls both.) If you have a plain ASB100, the PWM
|
| /linux-6.12.1/Documentation/networking/ |
| D | mptcp.rst | 49 *option* field. In that case, the connection will be "downgraded" to plain TCP,
154 MPTCP listen sockets will create "plain" *accepted* TCP sockets if the
|
| 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
|