Home
last modified time | relevance | path

Searched refs:corruption (Results 1 – 8 of 8) sorted by relevance

/linux-4.19.296/include/linux/
Dbug.h73 bool corruption = unlikely(condition); \
74 if (corruption) { \
81 corruption; \
/linux-4.19.296/drivers/ras/
DKconfig25 correctly, including avoiding data corruption, whereas Availability
29 data corruption.
/linux-4.19.296/drivers/memstick/core/
DKconfig14 in most cases result in data corruption.
/linux-4.19.296/fs/ubifs/
Drecovery.c698 int corruption = first_non_ff(buf, len); in ubifs_recover_leb() local
705 lnum, offs, corruption); in ubifs_recover_leb()
707 offs += corruption; in ubifs_recover_leb()
708 buf += corruption; in ubifs_recover_leb()
/linux-4.19.296/lib/
DKconfig.debug731 corruption, especially if it appears in 'struct thread_info'
961 corruption or other issues.
1007 bool "Detect stack corruption on calls to schedule()"
1015 data corruption or a sporadic crash at a later stage once the region
1659 accessed by the cpu in a way that could cause data corruption. For
1990 bool "Trigger a BUG when data corruption is detected"
1994 data corruption in kernel memory structures when they get checked
/linux-4.19.296/drivers/pci/controller/
DKconfig263 This can lead to data corruption if drivers perform concurrent
/linux-4.19.296/fs/affs/
DChanges34 - fix for a possible bitmap corruption
/linux-4.19.296/drivers/gpio/
DKconfig35 since setting an incorrect value could cause stack corruption.