Re: [PATCH 1/2] fs/erofs: Add support for EROFS

2023-07-17 Thread Gao Xiang
Hi Glenn, On 2023/7/17 11:51, Glenn Washburn wrote: On Mon, 17 Jul 2023 00:03:08 +0800 Yifan Zhao wrote: EROFS is a lightweight read-only filesystem designed for performance which has already been widely used in several scenarios, such as Android system partitions, container images, and rootf

[PATCH v3] ieee1275/ofdisk: retry on open and read failure

2023-07-17 Thread Mukesh Kumar Chaurasiya
Sometimes, when booting from a very busy SAN, the access to the disk can fail and then grub will eventually drop to grub prompt. This scenario is more frequent when deploying many machines at the same time using the same SAN. This patch aims to force the ofdisk module to retry the open or read func

backtrace command broken on x86_64-efi in QEMU

2023-07-17 Thread Glenn Washburn
I haven't run this on real hardware, but I would guess it would exhibit the same behavior. Here's the output I get: grub> insmod backtrace grub> backtrace 0x41: 0x0 (0x0,0x0,0x0) Invalid stack frame at 0x41 (0xc2) Glenn ___ Grub-devel mailing list

Re: How to detect the amount of RAM on non-EFI platforms?

2023-07-17 Thread Cyan Yang via Grub-devel
Hi, On 2023/7/14 22:04, Vladimir 'phcoder' Serbinenko wrote: > > Just add an option to consider "reserved" memory as available. User's > choice. Fire you it's a single if. > Thanks for the tip, but I don't think it will work out - if we add up the reserved section, the result will be more than act

Re: backtrace command broken on x86_64-efi in QEMU

2023-07-17 Thread Oskari Pirhonen
On Mon, Jul 17, 2023 at 16:07:09 -0500, Glenn Washburn wrote: > I haven't run this on real hardware, but I would guess it would exhibit > the same behavior. Here's the output I get: > > grub> insmod backtrace > grub> backtrace > 0x41: 0x0 (0x0,0x0,0x0) > Invalid stack frame at 0x41 (0xc2) >

[RFC PATCH] efi: Disable stack smashing protection on grub_efi_init()

2023-07-17 Thread Glenn Washburn
GCC is electing to instrument grub_efi_init() to give it stack smashing protection when configuring with --enable-stack-protector on the x86_64-efi target. In the function prologue, the canary at the top of the stack frame is set to the value of the stack guard. And in the epilogue, the canary is c