https://bugzilla.kernel.org/show_bug.cgi?id=199567 --- Comment #3 from Ant (untaintableangel@xxxxxxxxxxxxx) --- Sorry for the delay. OK, so lots of news: I did see a patch in amd-staging-drm-next 354ee4815f52219fcd97d91269917261aac0518a ("drm/amd/display: Fix bug that causes black screen") that sounded ideal but I couldn't apply it cleanly since it's too out of sync. After a git bisect, I was pleasantly surprised that the 3 main patches between rc-1-rc2 for amd/display stuff were all fine. Looks like it's something else entirely. I tested out an ubuntu mainline kernel and it worked fine, so the problem is something different in my custom .config, I guess. Something that has been fine for 4.17-rc1 and kernels before that but suddenly needs to change for rc2 onwards. (Bug still present on 4.17-rc5 btw) last good: 5e747dd9be54be190dd6ebeebf4a4a01ba765625 first bad: 43838a23a05fbd13e47d750d3dfd77001536dd33 commit 43838a23a05fbd13e47d750d3dfd77001536dd33 Author: Theodore Ts'o <tytso@xxxxxxx> Date: Wed Apr 11 13:27:52 2018 -0400 random: fix crng_ready() test The crng_init variable has three states: 0: The CRNG is not initialized at all 1: The CRNG has a small amount of entropy, hopefully good enough for early-boot, non-cryptographical use cases 2: The CRNG is fully initialized and we are sure it is safe for cryptographic use cases. The crng_ready() function should only return true once we are in the last state. This addresses CVE-2018-1108. Reported-by: Jann Horn <jannh@xxxxxxxxxx> Fixes: e192be9d9a30 ("random: replace non-blocking pool...") Cc: stable@xxxxxxxxxx # 4.8+ Signed-off-by: Theodore Ts'o <tytso@xxxxxxx> Reviewed-by: Jann Horn <jannh@xxxxxxxxxx> I'm looking into my config options for RNG/random stuff, but this bug can probably be bounced somewhere more appropriate now :) -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
