I'd like to understand the difference in threat model for running reordering every boot vs once per host, at kernel installation time.
What additional level of tangible mitigation does this provide? Especially if you do not reboot often unless it's absolutely required. I would argue with everyone coming out of the woodwork with grievances about kernel reordering, little harm would come by commenting it out in /etc/rc and not worrying about it anymore. That said, reordering has worked reliably for me on small VMs with 256 MB of RAM and compact storage, so I surmise there are multiple different and possibly independent causes of these issues. If this issue is truly widespread and not limited to a few users, one approach would be a publicly-available spreadsheet to collect these issues and narrow it down by architecture, storage, RAM, etc. to look for patterns. Regards Lloyd Andy Bradford wrote: > Thus said Terry Cocksworth on Sat, 23 May 2026 14:04:06 -0000: > > > There are no substantial signs that too little storage is the problem. > > One way to test this hypothesis is to create a filesystem that > intentionally has too little storage and see if the behavior changes. > > Andy > >
