> I'm afraid touching the memory management system in the 2.06 grub in > stable releases is out of the question. The fixes involve a ton of > patches and it's not really possible to cherry-pick them and the risk > of regression is significant and out of scope for (only) a stable > release. > > The only way we managed to in Ubuntu was to cherry-pick all the loader > changes from rhboot, and then also cherry-pick the entire 2.12 memory > management changes on top of it, and that caused plenty of regressions > at each point we picked more changes... > > In my opinion, this is not a release critical bug breaking _existing_ > systems, but a request to enable additional hardware currently > unsupported in debian. > > We will eventually backport the 2.12 grub to stable releases in > the upcoming months. We may want to issue it via -backports at first, > but if a security vulnerability comes in, this will eventually land > in a point release.
Thanks for the detailed explanation. A debian-maintained backport of grub-2.12 (through -backports or otherwise) would be very helpful. Is there any chance you would consider doing this for bullseye as well as for bookworm?
