lp://staging/ubuntu/vivid/iucode-tool
- Get this branch:
- bzr branch lp://staging/ubuntu/vivid/iucode-tool
Branch merges
Branch information
- Owner:
- Ubuntu branches
- Status:
- Mature
Recent revisions
- 12. By Henrique de Moraes Holschuh
-
* New upstream release
+ Fix issues found by the Coverity static checker:
+ CID 72165: An off-by-one error caused an out-of-bounds write to a
buffer while loading large microcode data files in ascii format
+ CID 72163: The code could attempt to close an already closed file
descriptor in certain conditions when processing directories
+ CID 72161: Stop memory leak in error path when loading microcode
data files
+ CID 72159, 72164, 72166, 72167, 72168, 72169: Cosmetic issues
that could not cause problems at runtime
* debian/control: bump standards version to 3.9.6 - 11. By Henrique de Moraes Holschuh
-
* New upstream release
+ Don't output duplicates for microcodes with extended signatures
to the same file or to the kernel
+ When writing an early initramfs, pad its trailer with zeros to
the next 1024-byte boundary. This is done so that the next
initramfs segment will be better aligned, just in case. The
entire cpio medatada overhead is now exactly 1024 bytes
+ Manpage style fixes: use iucode_tool consistently, groff formatting
+ Refuse to load ridiculously large data files (limit set to 1GiB)
* debian/lintian- override: override hyphen- used-as- minus-sign
as iucode-tool(8) now uses proper groff hyphens, but not in
a way the lintian test can detect.
* debian/rules: remove autoconf-1.14 autogenerated files on clean - 10. By Henrique de Moraes Holschuh
-
* New upstream release
+ Properly check microcode metadata date to be valid packed BCD in
strict mode
+ Do not assume a non-zero microcode Total Size field to be valid, it
is valid only when the Data Size field is non-zero. Fortunately,
Intel always set reserved fields to zero on released microcode, so
this bug was never (and is unlikely to ever be) triggered
+ Linux kernel bug workaround: when generating the early initramfs
archive, append NULs to the microcode data file name to pad the
start of the microcode data inside the initramfs archive to a
16-byte boundary. Document this issue on the manpage, the
workaround is only effective if the start of our early initramfs
cpio segment is 16-byte aligned in the final initramfs archive
+ Fix several cosmetic and minor code issues
+ Manpage fixes and enhancements
* debian/control: add debian/master branch information to Vcs-Git field
* debian/control: bump standards-version to 3.9.5 - 9. By Henrique de Moraes Holschuh
-
* New upstream maintenance release
+ Mention iucode-tool's new home at gitorious in documentation
+ Warn user when --scan-system fails due to errors such as a lack
of permission to access the cpuid devices
+ Use the libc optimized memcmp() to compare microcode
+ Minor manpage updates
+ --strict-checks now verifies that the microcode update date
is not utterly insane
* debian/control: update for new upstream location at Gitorious - 8. By Henrique de Moraes Holschuh
-
* New upstream maintenance release
+ Fix several cosmetic code issues
+ Manpage updates
+ Make it clear that the output order of microcodes is not stabilized
+ Make it clear that iucode_tool always break links when writing a
data file, and that it doesn't replace files atomically, so they
can get corrupted/lost if iucode-tool is interrupted while writing
+ Reword several notes for better readability
+ Use openat() when loading from a directory and when creating files in
a directory. Thus, iucode-tool will read/write to the same directory
even while racing another process that is trying to rename it while
iucode-tool is already running - 7. By Henrique de Moraes Holschuh
-
* New upstream release
+ Add verbose title to manpage iucode_tool(8)
+ Add support to write an early initramfs archive for Linux v3.9
* install iucode-tool symlinks to iucode_tool (closes: #689128) - 6. By Henrique de Moraes Holschuh
-
* New upstream release
+ Document missing -W, --write-named option in iucode_tool(8)
manpage (closes: #687963)
+ Print the number of unique signatures in verbose mode
+ Add loose date-based filtering (--loose-date-filtering option),
which is useful when trying to select microcode for very old
processors
+ Skip empty files and directories instead of aborting with an
error
+ Add an option to default to an empty selection (-s!)
+ Ensure that microcodes with the same metadata have the same
opaque data (payload) when in --strict-checks mode (default)
* Update debian/copyright to match upstream's - 5. By Henrique de Moraes Holschuh
-
* New upstream release
+ Fix regression introduced in 0.8.2 that caused all microcodes
to be selected by --scan-system on a box with unsupported
processors (e.g. non-Intel)
+ Update README: Intel has some microcode update information in
some public processor specification update documents - 4. By Henrique de Moraes Holschuh
-
* New upstream release
+ Update documentation and manpages for the new microcode
update interface in Linux v3.6.
+ Fail safe when --scan-system cannot access the cpuid driver:
instead of not selecting anything, still select all microcodes
if no other microcode selection option was used (closes: #683178)
* debian/control: add X-Vcs-* fields - 3. By Henrique de Moraes Holschuh
-
* New upstream release
+ inform user with an error message if cpuid driver is missing, and
--scan-system was requested
+ manpage updates
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/ubuntu/wily/iucode-tool