Commit 781b3e5efc3 ("tftp: Do not use priority queue") caused a regression
when fetching files over TFTP whose size is bigger than 65535 * block size.
grub> linux /images/pxeboot/vmlinuz
grub> echo $?
0
grub> initrd /images/pxeboot/initrd.img
error: timeout reading '/images/pxeboot/initr
On Mon, Aug 31, 2020 at 01:43:36PM -0500, Glenn Washburn wrote:
> I just noticed that I have a couple minor non-functional changes that I
> think will make this patch a little better. I had been planning on
> updating my original patch, but since you're picking this up, this is a
> better place to
By default, dm-crypt internally uses an IV that corresponds to 512-byte
sectors, even when a larger sector size is specified. What this means is
that when using a larger sector size, the IV is incremented every sector.
However, the amount the IV is incremented is the number of 512 byte blocks
in a
The main difference with this patch is that sector_size is renamed to
log_sector_size, grub has enough inaccurate or misleading names.
Additionally, rename LOG_SECTOR_SIZE to LUKS_LOG_SECTOR_SIZE and
CRYPT_LOG_SECTOR_SIZE to GRUB_CRYPTODISK_IV_LOG_SIZE and moved to
cryptodisk.h. Also a comment was
