| /linux-6.15/lib/ |
| D | Kconfig.kcsan | 173 conflicting access is of unknown origin. This type of race is
211 If enabled and a conflicting write is observed via a watchpoint, but
226 notice that data races between two conflicting plain aligned writes
234 additional filtering. Conflicting marked atomic reads and plain
242 accesses, conflicting marked atomic reads and plain writes will not
244 due to two conflicting plain writes will be reported (aligned and
|
| /linux-6.15/fs/overlayfs/ |
| D | params.c | 876 /* Don't allow explicit specified conflicting combinations */ in ovl_fs_params_verify()
878 pr_err("conflicting options: metacopy=off,verity=%s\n", in ovl_fs_params_verify()
896 pr_err("conflicting options: metacopy=on,redirect_dir=%s\n", in ovl_fs_params_verify()
901 pr_err("conflicting options: verity=%s,redirect_dir=%s\n", in ovl_fs_params_verify()
926 pr_err("conflicting options: nfs_export=on,index=off\n"); in ovl_fs_params_verify()
944 pr_err("conflicting options: nfs_export=on,metacopy=on\n"); in ovl_fs_params_verify()
977 pr_err("conflicting options: userxattr,redirect_dir=%s\n", in ovl_fs_params_verify()
982 pr_err("conflicting options: userxattr,metacopy=on\n"); in ovl_fs_params_verify()
986 pr_err("conflicting options: userxattr,verity=%s\n", in ovl_fs_params_verify()
|
| /linux-6.15/drivers/char/mwave/ |
| D | smapi.c | 291 "smapi::smapi_set_DSP_cfg Disabling conflicting serial port\n"); in smapi_set_DSP_cfg()
312 "smapi::smapi_set_DSP_cfg Disabling conflicting serial port A\n"); in smapi_set_DSP_cfg()
344 "smapi::smapi_set_DSP_cfg Disabling conflicting serial port B\n"); in smapi_set_DSP_cfg()
365 "smapi::smapi_set_DSP_cfg Disabling conflicting serial port B\n"); in smapi_set_DSP_cfg()
399 "smapi::smapi_set_DSP_cfg Disabling conflicting IR port\n"); in smapi_set_DSP_cfg()
426 "smapi::smapi_set_DSP_cfg Disabling conflicting IR port\n"); in smapi_set_DSP_cfg()
|
| /linux-6.15/kernel/kcsan/ |
| D | report.c | 181 * 1. read watchpoint, conflicting write (value_change==TRUE): report; in skip_report()
182 * 2. read watchpoint, conflicting write (value_change==MAYBE): skip; in skip_report()
183 * 3. write watchpoint, conflicting write (value_change==TRUE): report; in skip_report()
184 * 4. write watchpoint, conflicting write (value_change==MAYBE): skip; in skip_report()
185 * 5. write watchpoint, conflicting read (value_change==MAYBE): skip; in skip_report()
186 * 6. write watchpoint, conflicting read (value_change==TRUE): report; in skip_report()
|
| D | kcsan.h | 56 * due to two conflicting ASSERT type accesses, then both will be
|
| /linux-6.15/arch/x86/mm/pat/ |
| D | memtype_interval.c | 25 * physical memory areas. Without proper tracking, conflicting memory
109 pr_info("x86/PAT: %s:%d conflicting memory types %Lx-%Lx %s<->%s\n", in memtype_check_conflict()
|
| /linux-6.15/include/uapi/linux/ |
| D | libc-compat.h | 10 * conflict with userspace definitions. If a UAPI header has such conflicting
31 * (d) Back in the UAPI header with the conflicting definitions, guard the
|
| /linux-6.15/arch/x86/include/asm/ |
| D | agp.h | 11 * region is mapped uncacheable. Make sure there are no conflicting
|
| /linux-6.15/drivers/mfd/ |
| D | intel-lpss.h | 18 * Some DSDTs have an unused GEXP ACPI device conflicting with I2C4 resources.
|
| /linux-6.15/drivers/gpu/drm/vgem/ |
| D | vgem_fence.c | 114 * completion. Note that if a conflicting fence is already on the dma-buf (i.e.
153 /* Check for a conflicting fence */ in vgem_fence_attach_ioctl()
|
| /linux-6.15/Documentation/userspace-api/media/dvb/ |
| D | dmx-start.rst | 59 - This error code indicates that there are conflicting requests.
|
| D | dmx-set-pes-filter.rst | 58 - This error code indicates that there are conflicting requests.
|
| D | dmx-fwrite.rst | 64 - This error code indicates that there are conflicting requests. The
|
| /linux-6.15/security/selinux/ss/ |
| D | conditional.c | 266 * conflicting rules by searching the te_avtab and the in cond_insertf()
287 pr_err("SELinux: too many conflicting type rules.\n"); in cond_insertf()
298 pr_err("SELinux: conflicting type rules.\n"); in cond_insertf()
304 pr_err("SELinux: conflicting type rules when adding type rule for true.\n"); in cond_insertf()
|
| /linux-6.15/Documentation/devicetree/bindings/pci/ |
| D | pci-ep.yaml | 51 potentially conflicting domain numbers may be assigned to endpoint
|
| D | pci.txt | 18 host bridges in the system, otherwise potentially conflicting domain numbers
|
| /linux-6.15/lib/lzo/ |
| D | lzodefs.h | 33 #error "conflicting endian definitions"
|
| /linux-6.15/drivers/md/dm-vdo/ |
| D | status-codes.h | 39 /* parameters have conflicting values */
|
| D | status-codes.c | 23 { "VDO_PARAMETER_MISMATCH", "Parameters have conflicting values" },
|
| /linux-6.15/include/media/ |
| D | v4l2-mediabus.h | 19 * operation to ensure that no conflicting settings are specified when
26 * to avoid conflicting settings.
|
| /linux-6.15/Documentation/admin-guide/perf/ |
| D | qcom_l2_pmu.rst | 20 are specified, the conflicting events cannot be counted at the same time.
|
| /linux-6.15/drivers/staging/media/atomisp/pci/ |
| D | isp2400_input_system_global.h | 136 INPUT_SYSTEM_CFG_FLAG_CONFLICT = 1U << 3 // To mark a conflicting configuration.
|
| /linux-6.15/tools/include/nolibc/ |
| D | crt.h | 37 /* silence potential warning: conflicting types for 'main' */ in _start_c()
|
| /linux-6.15/drivers/gpio/ |
| D | gpio-winbond.c | 206 * struct winbond_gpio_port_conflict - possibly conflicting device information
207 * @name: device name (NULL means no conflicting device defined)
527 /* is there a possible conflicting device defined? */ in winbond_gpio_configure_port()
|
| /linux-6.15/drivers/pci/ |
| D | vgaarb.c | 259 * check if we sit on the same bus as the conflicting device. in __vga_tryget()
271 * return the conflicting entry. in __vga_tryget()
322 * Ok, we got it, everybody conflicting has been disabled, let's in __vga_tryget()
418 * This function will block if some conflicting card is already locking one of
466 * need to attach to the conflicting device. in vga_get()
756 * that is, we come up with conflicting devices and let the arbiter's
|