| /kernel/linux/linux-5.10/net/sunrpc/auth_gss/ |
| D | gss_krb5_seqnum.c | 49 unsigned char *plain; in krb5_make_seq_num() local
52 plain = kmalloc(8, GFP_NOFS); 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 …]
|
| /kernel/linux/linux-6.6/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()
248 pr_info("could not allocate plain buffer\n"); 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()
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 17 1. Plain C-language accesses (unmarked), for example, "a = b;"
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.
156 Plain C-language stores can also be used for this use case. However,
[all …]
|
| D | explanation.txt | 33 25. PLAIN ACCESSES AND DATA RACES
933 Plain-coherence: This requires that plain memory accesses
940 "rcu" and "plain-coherence" axioms are specific to the LKMM.
1032 the w-post-bounded relation defined below in the PLAIN ACCESSES AND
2164 PLAIN ACCESSES AND DATA RACES
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
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | Kconfig.kcsan | 197 bool "Assume that plain aligned writes up to word size are atomic"
200 Assume that plain aligned writes up to word size are atomic by
203 races due to conflicts where the only plain accesses are aligned
204 writes up to word size: conflicts between marked reads and plain
206 notice that data races between two conflicting plain aligned writes
213 additional filtering. Conflicting marked atomic reads and plain
215 plain reads and marked writes to result in "unknown origin" reports.
221 accesses, conflicting marked atomic reads and plain writes will not
223 due to two conflicting plain writes will be reported (aligned and
|
| D | test_printf.c | 231 pr_warn("crng possibly not yet initialized. plain 'p' buffer contains \"%s\"", in plain_format()
271 pr_warn("crng possibly not yet initialized. plain 'p' buffer contains \"%s\"", in plain_hash_to_buffer()
300 plain(void) in plain() function
306 pr_warn("plain 'p' does not appear to be hashed\n"); in plain()
313 pr_warn("hashing plain 'p' has unexpected format\n"); in plain()
326 * to be called after plain(). in test_hashed()
675 plain(); in test_pointer()
|
| /kernel/linux/linux-5.10/tools/memory-model/ |
| D | linux-kernel.cat | 71 let to-w = rwdep | (overwrite & int) | (addr ; [Plain] ; wmb)
160 (* Plain accesses and data races *)
163 (* Warn about plain writes and marked accesses in the same region *)
164 let mixed-accesses = ([Plain & W] ; (po-loc \ barrier) ; [Marked]) |
165 ([Marked] ; (po-loc \ barrier) ; [Plain & W])
173 (* Boundaries for lifetimes of plain accesses *)
181 (* Visibility and executes-before for plain accesses *)
189 let pre-race = ext & ((Plain * M) | ((M \ IW) * Plain))
191 (* Coherence requirements for plain accesses *)
195 empty (wr-incoh | rw-incoh | ww-incoh) as plain-coherence
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ci/xfails/ |
| D | rockchip-rk3399-fails.txt | 13 kms_flip@plain-flip-fb-recreate,Fail
14 kms_flip@plain-flip-fb-recreate-interruptible,Fail
15 kms_flip@plain-flip-ts-check,Fail
16 kms_flip@plain-flip-ts-check-interruptible,Fail
|
| /kernel/linux/linux-6.6/tools/memory-model/ |
| D | linux-kernel.cat | 83 let to-w = rwdep | (overwrite & int) | (addr ; [Plain] ; wmb)
173 (* Plain accesses and data races *)
176 (* Warn about plain writes and marked accesses in the same region *)
177 let mixed-accesses = ([Plain & W] ; (po-loc \ barrier) ; [Marked]) |
178 ([Marked] ; (po-loc \ barrier) ; [Plain & W])
186 (* Boundaries for lifetimes of plain accesses *)
194 (* Visibility and executes-before for plain accesses *)
202 let pre-race = ext & ((Plain * M) | ((M \ IW) * Plain))
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 *)
78 let Plain = M \ Marked
80 (* Redefine dependencies to include those carried through plain accesses *)
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | kcsan.rst | 136 * ``CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC``: Assume that plain aligned writes
139 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
193 least one is a write. For a more thorough discussion and definition, see `"Plain
196 .. _"Plain Accesses and Data Races" in the LKMM: https://git.kernel.org/pub/scm/linux/kernel/git/to…
209 assumes that as long as a plain access is not observed to race with another
253 compiler instrumenting plain accesses. For each instrumented plain access:
264 To detect data races between plain and marked accesses, KCSAN also annotates
|
| /kernel/linux/linux-6.6/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
193 least one is a write. For a more thorough discussion and definition, see `"Plain
196 .. _"Plain Accesses and Data Races" in the LKMM: https://git.kernel.org/pub/scm/linux/kernel/git/to…
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
|
| /kernel/linux/linux-6.6/kernel/kcsan/ |
| D | permissive.h | 44 * Rules here are only for plain read accesses, so that we still report in kcsan_ignore_data_race()
45 * data races between plain read-write accesses. in kcsan_ignore_data_race()
67 * than 1 bit changed, the plain accesses are safe despite the presence in kcsan_ignore_data_race()
|
| /kernel/linux/linux-5.10/tools/memory-model/Documentation/ |
| D | explanation.txt | 32 24. PLAIN ACCESSES AND DATA RACES
880 Plain-coherence: This requires that plain memory accesses
887 "rcu" and "plain-coherence" axioms are specific to the LKMM.
1920 PLAIN ACCESSES AND DATA RACES
1927 accesses such as x or y = 0 are simply called "plain" accesses.
1929 Early versions of the LKMM had nothing to say about plain accesses.
1931 by plain accesses are not concurrently read or written by any other
1933 of transformations or optimizations of code containing plain accesses,
1959 But since P0's load from x is a plain access, the compiler may decide
1981 doesn't try to predict all possible outcomes of code containing plain
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/tools/memory-model/litmus-tests/ |
| D | dep+plain.litmus | 1 C dep+plain
6 * This litmus test demonstrates that in LKMM, plain accesses
|
| /kernel/linux/linux-5.10/include/uapi/linux/netfilter/ |
| D | nfnetlink_osf.h | 94 * plain numeric value. Can also be made as plain numeric value which
|
| /kernel/linux/linux-6.6/include/uapi/linux/netfilter/ |
| D | nfnetlink_osf.h | 94 * plain numeric value. Can also be made as plain numeric value which
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | faraday,ftpci100.txt | 5 plain and dual PCI. The plain version embeds a cascading interrupt controller
50 The plain variant has 128MiB of non-prefetchable memory space, whereas the
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/ |
| D | local_kptr_stash.c | 26 struct plain_local __kptr *plain; member
91 res = bpf_kptr_xchg(&mapval->plain, res); in stash_plain()
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | protection-keys.rst | 77 behavior of a plain mprotect(). For instance if you do this::
100 the plain mprotect() permissions are violated.
|
| /kernel/linux/linux-6.6/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.
|