https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #117 from Jens Axboe (axboe@xxxxxxxxx) --- (In reply to Artem S. Tashkinov from comment #87) > Regression testing could be carried out in a VM running on top of a ramdisk > (e.g. tmpfs) to speed up the process. > > I guess someone with a decent amount of persistence and spare time could do > that and test each individual commit between 4.18 and 4.19, however that > doesn't guarantee success since the bug might be hardware related and not > reproducible in a virtual environment. Or it might require obscene amounts > of RAM/disk space which would be difficult, if not impossible to reproduce > in a VM. > > I for one decided to stay on 4.18.x and not upgrade to any more recent > kernels until the regression is identified and dealt with. > > Maybe one day someone will become truly invested in the kernel development > process and we'll have proper QA/QC/unit testing/regression > testing/fuzzying, so that individuals won't have to sacrifice their data and > time because kernel developers are mostly busy with adding new features and > usually not really concerned with performance, security and stability of > their code unless they are pointed at such issues. You obviously have no idea wtf you are talking about, I suggest you go investigate just how much testing is done, continuously, on things like file system and storage. I take personal offense in in claims that developers "are not really concerned with performance and stability of their code". Here's a news flash for you - bugs happen, no matter how much testing is done on something. -- You are receiving this mail because: You are watching the assignee of the bug.
