Searched full:oblivious (Results 1 – 10 of 10) sorted by relevance
46 is to make flock() and fcntl() locks oblivious to each other. Both can
32 ignore them. In the first case, handlers are oblivious to the trigger type, so
45 * important to do because string oblivious code may read past in do_strncpy_from_user()
299 This allows the user to be oblivious about the underlying buffering mechanism
102 rather to let the netfs remain oblivious.
45 * bpf_object in parts of USDT attachment, they are oblivious of each other's46 * existence and libbpf is just oblivious, dealing with bpf_object-specific
313 * oblivious to the format of the directory. Hence we can either get a block
1424 * Linux vfs should be oblivious to changes between v0 and v2. in bnx2x_vf_mbx_acquire()
2991 * provide the routing information and is oblivious of the I/O-APIC
62 * oblivious of the offset.
