| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
5.15 was released, update a few TODOs that were dependent on 5.15 being
properly released.
Re-generate all configs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not pretend writes are atomic. While this may currently be a
prevailing preference in the community, it does hide more interesting
bugs [1].
Since we moderate data races anyway, and are still drowning in data
races, a few more won't hurt.
What it does help with, however, is getting better signals about harmful
data races. Most of the read/write data races provide weak signals, but
write/write data races should provide a stronger harmfulness signal [1],
which will help us in selecting data races to investigate further.
[1] https://googleprojectzero.blogspot.com/2021/10/how-simple-linux-kernel-memory.html
|
| |
|
|
|
| |
CONFIG_KCSAN_DEBUG no longer exists, remove it. Older kernels will set
it to 'n' by default.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The new CONFIG_KCSAN_PERMISSIVE is now supported in mainline:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa829778b16f15266fefe2640f04931b16ce39c0
Select it in the default syzbot config.
The configs were updated manually, because we should wait until
v5.15-rc1 is out (mainline is still in the merge window), at which
point we can update upstream's commit hash for syz-kconf and regenerate
all configs.
|
| |
|
|
|
|
|
| |
Restore the default kernel config value for
CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC
Fixes: cc97498cfe89 ("tools/syz-kconf: don't enable configs implicitly")
|
|
|
Add config fragments for the new config generation system.
Update #2171
|
