Home
last modified time | relevance | path

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

123456789

/linux/lib/
H A DKconfig.kcsan173 conflicting access is of unknown origin. This type of race is
205 If enabled and a conflicting write is observed via a watchpoint, but
220 notice that data races between two conflicting plain aligned writes
228 additional filtering. Conflicting marked atomic reads and plain
236 accesses, conflicting marked atomic reads and plain writes will not
238 due to two conflicting plain writes will be reported (aligned and
/linux/arch/x86/mm/pat/
H A Dmemtype_interval.c25 * physical memory areas. Without proper tracking, conflicting memory
83 pr_info("x86/PAT: %s:%d conflicting memory types %Lx-%Lx %s<->%s\n", in memtype_check_conflict()
/linux/kernel/kcsan/
H A Dreport.c181 * 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()
H A Dkcsan.h56 * due to two conflicting ASSERT type accesses, then both will be
/linux/drivers/char/mwave/
H A Dsmapi.c291 "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/include/uapi/linux/
H A Dlibc-compat.h10 * conflict with userspace definitions. If a UAPI header has such conflicting
31 * (d) Back in the UAPI header with the conflicting definitions, guard the
H A Dcoredump.h91 * @COREDUMP_MARK_CONFLICTING: the provided coredump_ack mask has conflicting options
/linux/arch/x86/include/asm/
H A Dagp.h11 * region is mapped uncacheable. Make sure there are no conflicting
/linux/scripts/kconfig/tests/transitional/
H A D__init__.py11 - User-set NEW values take precedence over conflicting OLD transitional values
/linux/drivers/gpu/drm/vgem/
H A Dvgem_fence.c99 * completion. Note that if a conflicting fence is already on the dma-buf (i.e.
138 /* Check for a conflicting fence */ in vgem_fence_attach_ioctl()
/linux/drivers/mfd/
H A Dintel-lpss.h18 * Some DSDTs have an unused GEXP ACPI device conflicting with I2C4 resources.
/linux/security/apparmor/
H A Ddomain.c31 static const char * const CONFLICTING_ATTACH_STR = "conflicting profile attachments";
33 "conflicting profile attachments - ix fallback";
35 "conflicting profile attachments - ux fallback";
695 * Currently this is only conflicting attachments, but other in profile_transition()
725 /* Force audit on conflicting attachment fallback in profile_transition()
1068 info = "conflicting target types"; in build_change_hat()
1131 } else { /* conflicting change type */ in change_hat()
1132 info = "conflicting targets types"; in change_hat()
/linux/Documentation/userspace-api/media/dvb/
H A Ddmx-start.rst59 - This error code indicates that there are conflicting requests.
H A Ddmx-set-pes-filter.rst58 - This error code indicates that there are conflicting requests.
H A Ddmx-fwrite.rst64 - This error code indicates that there are conflicting requests. The
/linux/lib/lzo/
H A Dlzodefs.h33 #error "conflicting endian definitions"
/linux/drivers/md/dm-vdo/
H A Dstatus-codes.h39 /* parameters have conflicting values */
H A Dstatus-codes.c23 { "VDO_PARAMETER_MISMATCH", "Parameters have conflicting values" },
/linux/fs/overlayfs/
H A Dparams.c893 pr_err("conflicting options: metacopy=on,redirect_dir=%s\n", in ovl_fs_params_verify()
918 pr_err("conflicting options: nfs_export=on,index=off\n"); in ovl_fs_params_verify()
936 pr_err("conflicting options: nfs_export=on,metacopy=on\n"); in ovl_fs_params_verify()
969 pr_err("conflicting options: userxattr,redirect_dir=%s\n", in ovl_fs_params_verify()
974 pr_err("conflicting options: userxattr,metacopy=on\n"); in ovl_fs_params_verify()
/linux/Documentation/admin-guide/perf/
H A Dqcom_l2_pmu.rst20 are specified, the conflicting events cannot be counted at the same time.
/linux/tools/include/nolibc/
H A Dcrt.h42 /* silence potential warning: conflicting types for 'main' */ in _start_c()
/linux/fs/nfsd/
H A Dlockd.c61 /* this error can indicate a presence of a conflicting in nlm_fopen()
/linux/drivers/gpio/
H A Dgpio-winbond.c206 * struct winbond_gpio_port_conflict - possibly conflicting device information
207 * @name: device name (NULL means no conflicting device defined)
531 /* is there a possible conflicting device defined? */ in winbond_gpio_configure_port()
/linux/tools/include/uapi/linux/
H A Dcoredump.h91 * @COREDUMP_MARK_CONFLICTING: the provided coredump_ack mask has conflicting options
/linux/drivers/pci/
H A Dvgaarb.c259 * 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()
733 * that is, we come up with conflicting devices and let the arbiter's

123456789