| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| remove-arrows.patch | commit e39fb5b9e590c6616459c15b5d95fbc09fb077d6 Get rid of the arrows in our debug messages. They're not *that* useful, and the code is clever and problematic. Resolves github issue #124 Signed-off-by: Peter Jones <pjones@redhat.com> diff --git a/src/linux-acpi-root.c b/src/linux-acpi-root.c index 06e69ee..30728de 100644 |
Peter Jones <pjones@redhat.com> | no | 2019-02-21 | ||
| fix-gcc9-werror-format-guid.patch | dp.h: make format_guid() handle misaligned guid pointers safely.diff --git a/src/dp.h b/src/dp.h index aa4e390..20cb608 100644 |
Peter Jones <pjones@redhat.com> | yes | debian upstream | upstream, https://github.com/rhboot/efivar/commit/b98ba8921010d03f46704a476c69861515deb1ca | 2019-01-07 |
| fix-gcc9-werrors.patch | Fix all the places -Werror=address-of-packed-member catches. | Peter Jones <pjones@redhat.com> | yes | debian upstream | upstream, https://github.com/rhboot/efivar/commit/c3c553db85ff10890209d0fe48fb4856ad68e4e0 | 2019-02-21 |
| ucs2.h-remove-unused-variable.patch | [PATCH] ucs2.h: remove unused variable The const uint16_t pointer is not used since now the two bytes of the UCS-2 chars are checked to know if is the termination of the string. |
Javier Martinez Canillas <javierm@redhat.com> | no | 2019-03-05 | ||
| ucs2.h-fix-logic-that-checks-for-UCS-2-string-termin.patch | [PATCH] ucs2.h: fix logic that checks for UCS-2 string termination Currently the loop to count the lenght of the UCS-2 string ends if either of the two bytes are 0, but 0 is a valid value for UCS-2 character codes. So only break the loop when 0 is the value for both UCS-2 char bytes. |
Javier Martinez Canillas <javierm@redhat.com> | no | 2019-03-05 | ||
| guids.S-Include-cet.h-when-CET-is-enabled.patch | [PATCH] guids.S: Include <cet.h> when CET is enabled Intel Control-flow Enforcement Technology (CET): https://software.intel.com/en-us/articles/intel-sdm contains shadow stack (SHSTK) and indirect branch tracking (IBT). When CET is enabled, ELF object files must be marked with .note.gnu.property section. CET enabled GCC provides a header file, <cet.h>, which can be included in assembly files to generate the CET marker automatically. |
"H.J. Lu" <hjl.tools@gmail.com> | no | 2020-03-01 | ||
| Always-initialize-any-variable-we-use-with-sscanf-s-.patch | [PATCH] Always initialize any variable we use with sscanf's %n =================================================================== |
Peter Jones <pjones@redhat.com> | no | upstream,https://github.com/rhboot/efivar/commit/5dc12cc56c79d293cf68d12a0b84373a785745e7 | 2019-05-28 | |
| 0001-Fix-the-error-path-in-set_disk_and_part_name.patch | [PATCH] Fix the error path in set_disk_and_part_name() [ dannf: Context adjustments due to upstream whitespace cleanup; Included to simplify the application of 0003-Try-even-harder-to-find-disk-device-symlinks-in-sysf.patch ] =================================================================== |
Peter Jones <pjones@redhat.com> | yes | upstream | upstream, https://github.com/rhboot/efivar/commit/22bc0866e941cbfe57de6522db51e9cf2c6b3ff1 | 2019-10-02 |
| 0002-sysfs-parsers-make-all-the-sys-block-link-parsers-wo.patch | [PATCH] sysfs parsers: make all the /sys/block link parsers work the same way Apparently I wrote some of these one way and some the other, and the one special case where everything was "current+sz" instead of some form of "current += pos; sz += pos; ...; return sz;" or the subtraction version. Make them all the same, where possible. [ dannf: Restrict to just linux-nvme.c; Context adjustments due to upstream whitespace cleanup; drop call to dbgmk() call - it didn't exist in v37; included to simplify application of later patches in series ] =================================================================== |
Peter Jones <pjones@redhat.com> | yes | upstream | upstream, https://github.com/rhboot/efivar/commit/4718694094647b981b74453445d000b0296b6544 | 2019-10-15 |
| 0003-Try-even-harder-to-find-disk-device-symlinks-in-sysf.patch | [PATCH] Try even harder to find disk device symlinks in sysfs. Today's realization is that the thing encoded into the structure of sysfs is, in the best case, the dependency graph of the makefile targets to build a device driver. In the case of nvme-fabric, or really wherever the kernel has class_create() and device_create() in the same function, there's an extra level of indirection. Anyway, in this patch we stop pretending sysfs isn't completely absurd, and just try adding "/device" in the middle of the driver symlink path, until we actually either get ENOENT on the device symlink or find a device symlink that actually has a driver symlink under it. [ dannf: Context adjustments due to upstream whitespace cleanup; Adjust to omit efi_error_pop() call that didn't exist in v37; included to simplify application of later patches in series ] =================================================================== |
Peter Jones <pjones@redhat.com> | yes | upstream | upstream, https://github.com/rhboot/efivar/commit/c9c1424d0e09bf33b747d37c43177c63367b1290 | 2019-10-11 |
| 0004-Handle-sys-devices-virtual-nvme-fabrics-nvme-subsyst.patch | [PATCH] Handle /sys/devices/virtual/{nvme-fabrics,nvme-subsystem} devices [ dannf: Context adjustments due to upstream whitespace cleanup and dbgmk() calls; drop new calls to dbgmk() - it didn't exist in v37 ] =================================================================== |
Peter Jones <pjones@redhat.com> | yes | upstream | upstream, https://github.com/rhboot/efivar/commit/c41da0bdce04ab0f99b992d51ff6fd0ab55d040a | 2019-10-02 |
| 0005-Fix-variable-sz-uninitialized-error.patch | [PATCH 2/2] Fix variable 'sz' uninitialized error To fix the error: external/efivar/src/linux-virtual-root.c:66:4: error: variable 'sz' is uninitialized when used here [-Werror,-Wuninitialized] sz += pos1; ^~ external/efivar/src/linux-virtual-root.c:45:12: note: initialize the variable 'sz' to silence this warning ssize_t sz; ^ = 0 1 error generated. =================================================================== |
Chih-Wei Huang <cwhuang@linux.org.tw> | yes | upstream | upstream, https://github.com/rhboot/efivar/commit/9dc04c2fd88b6e0e0fe411885041925d52f71af3 | 2020-01-22 |
| 0006-Fix-parsing-for-nvme-subsystem-devices.patch | [PATCH] Fix parsing for nvme-subsystem devices nvme-subsystem devices have a link that looks like: ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1 However, the current code expects an additional /nvme0/ component, i.e.: ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0/nvme0n1 Fix this by adding a separate branch for parsing nvme-subsystem devices. Resolves github issue #157. [ dannf: Context adjustments due to upstream whitespace cleanup and dbgmk() calls ] =================================================================== |
dann frazier <dann.frazier@canonical.com> | yes | upstream | upstream, https://github.com/rhboot/efivar/commit/4e12f997f8b6af76ef65e7045c232b7d642a1af4 | 2020-08-17 |