Home
last modified time | relevance | path

Searched full:markings (Results 1 – 25 of 25) sorted by relevance

/linux-6.14.4/net/netfilter/
Dxt_CONNSECMARK.c3 * This module is used to copy security markings from packets
4 * to connections, and restore security markings from connections
DKconfig128 This option enables security markings to be applied to
862 The CONNSECMARK target copies security markings from packets
863 to connections, and restores security markings from connections
/linux-6.14.4/Documentation/core-api/
Dasm-annotations.rst110 most frequent markings**. They are used for functions with standard calling
115 ``SYM_FUNC_START_WEAK`` and ``SYM_FUNC_START_WEAK_NOALIGN`` markings are
/linux-6.14.4/arch/arm/kernel/
Delf.c98 * *this column has no architectural effect: NX markings are ignored by
/linux-6.14.4/Documentation/devicetree/bindings/iio/adc/
Dmicrochip,mcp3564.yaml86 The device address is part of the device markings to avoid
/linux-6.14.4/net/ipv4/
Dtcp_rate.c54 * heuristics. We don't want spurious RTOs or loss markings to cause in tcp_rate_skb_sent()
/linux-6.14.4/Documentation/admin-guide/blockdev/
Dparide.rst93 installation floppy. Alternatively, you can look at the markings on
/linux-6.14.4/security/
Dcommoncap.c319 * affects the security markings on that inode, and if it is, should
335 * cap_inode_killpriv - Erase the security markings on an inode
340 * Erase the privilege-enhancing security markings on an inode.
/linux-6.14.4/arch/x86/include/asm/
Delf.h283 * *this column has no architectural effect: NX markings are ignored by
/linux-6.14.4/samples/bpf/
Dhbm.c372 // ECN CE markings in run_bpf_prog()
/linux-6.14.4/arch/arm64/boot/dts/rockchip/
Drk3326-gameforce-chi.dts765 * is an 8-pin SOIC with no markings located right next to the left ADC
/linux-6.14.4/Documentation/security/
Dcredentials.rst227 File Markings
/linux-6.14.4/include/linux/
Dpage-flags.h542 * Private page markings that may be used by the filesystem that owns the page in PAGEFLAG()
Drcupdate.h503 * multiple pointers markings to match different RCU implementations
Diommu.h25 * markings, and certain devices are capable of issuing transactions marked as
/linux-6.14.4/drivers/iio/adc/
Dmcp3564.c1120 * The device address is part of the device markings to avoid in mcp3564_config()
/linux-6.14.4/kernel/bpf/
Dverifier.c2113 /* The register can already have a range from prior markings. in reg_is_init_pkt_pointer()
4084 * No further markings in parent are necessary in backtrack_insn()
4384 * because precision markings in current non-checkpointed state are in mark_all_scalars_precise()
4464 * In the former case, precise markings in current state are completely
4466 * checkpointed ("old") state precise markings are important, and if old
4470 * markings and any required parent states' precise markings are enforced
4474 * actually matters is any of the precise markings propagated into current
4477 * markings set or not.
4486 * what we mentioned above about state comparison ignoring precise markings
4488 * markings *at will* during instruction verification process. But as verifier
[all …]
/linux-6.14.4/net/wireless/
Dutil.c991 * corresponding L2 markings. in cfg80211_classify8021d()
/linux-6.14.4/drivers/hwmon/
Dlm90.c2140 * Note: Multiple chips with different markings labeled as in lm90_detect_maxim()
/linux-6.14.4/drivers/dma/
Dste_dma40.c84 /* Bit markings for allocation map */
/linux-6.14.4/Documentation/
Dmemory-barriers.txt1814 volatile markings, the compiler would be well within its rights to
/linux-6.14.4/drivers/bluetooth/
Dbtusb.c2525 * - 0x7558: IC markings FR3191AHAL 749H15143 (HCI rev/sub-version: 0x0709) in btusb_setup_csr()
/linux-6.14.4/Documentation/translations/sp_SP/
Dmemory-barriers.txt1886 hay markings volátiles, el compilador estaría en su derecho de
/linux-6.14.4/drivers/scsi/
Dscsi_debug.c6293 ramp[510] = 0x55; /* magic partition markings */ in sdebug_build_parts()
/linux-6.14.4/scripts/
Dcheckpatch.pl4193 # check for old HOTPLUG __dev<foo> section markings