Lines Matching refs:zero

304     char zero = 0;

311 if (put_user(zero, log->ubuf + new_pos)) {
738 /* do_check() starts with zero-sized stack in struct bpf_verifier_state to
741 * Note there is a non-zero 'parent' pointer inside bpf_verifier_state
1041 /* Mark the 'variable offset' part of a register as zero. This should be
1707 /* The dst will be zero extended, so won't be sub-register anymore. */
1858 * Load from any other memory can be zero extended.
2239 /* Does this register contain a constant zero? */
2376 /* when we zero initialize stack slots mark them as such */
2423 /* set if the fact that we're writing a zero is used to let any
2526 /* any access_size read into register is zero extended,
2987 /* A non zero info.ctx_field_size indicates that this field is a
2990 * access than actual ctx access size. A zero info.ctx_field_size
3430 /* BPF architecture zero extends alu32 ops into 64-bit registesr */
3783 * case, we know the offset is zero.
3889 /* b/h/w load zero-extends, mark upper bits as known 0 */
3962 verbose(env, "invalid zero-sized read\n");
4109 /* Allow zero-byte read from NULL, regardless of pointer type */
4472 * zero register offset.
5405 verbose(env, "get_local_storage() doesn't support non-zero flags\n");
5800 * a consequence, do not need to simulate the zero-truncation either).
6071 /* something was added to pkt_ptr, set range to zero */
6126 /* something was added to pkt_ptr, set range to zero */
6604 * 1) src_reg might be zero, so the sign bit of the result is
6608 * 3) the signed bounds cross zero, so they tell us nothing
6634 * 1) src_reg might be zero, so the sign bit of the result is
6638 * 3) the signed bounds cross zero, so they tell us nothing
6862 /* ALU32 ops are zero extended into 64bit register */
7095 verbose(env, "div by zero\n");
7400 /* If pointer is valid tests against zero will fail so we can
7595 /* This uses zero as "not present in table"; luckily the zero opcode,
7636 * have been known-zero, because we don't allow pointer
8605 /* set the size kernel expects so loader can zero
8718 /* Need to zero it in case the userspace may
9139 * it will be safe with zero-initialized stack.
10329 * [0, off) and [off, end) to new locations, so the patched range stays zero
12362 for verification purposes, so set it back to zero before returning