fio is a tool that will spawn a number of threads or processes doing a
particular type of io action as specified by the user. fio takes a
number of global parameters, each inherited by the thread unless
otherwise parameters given to them overriding that setting is given.
The typical use of fio is to write a job file matching the io load
one wants to simulate.
=========================
Fixes since v2.11
-----------------
* The default Travis-CI configuration specifies newer P4 and GitLFS.
* The character width table has been updated to match Unicode 9.0
* Update the isatty() emulation for Windows by updating the previous
hack that depended on internals of (older) MSVC runtime.
* "git rev-parse --symbolic" failed with a more recent notation like
"HEAD^-1" and "HEAD^!".
* An empty directory in a working tree that can simply be nuked used
to interfere while merging or cherry-picking a change to create a
submodule directory there, which has been fixed..
* The code in "git push" to compute if any commit being pushed in the
superproject binds a commit in a submodule that hasn't been pushed
out was overly inefficient, making it unusable even for a small
project that does not have any submodule but have a reasonable
number of refs.
* "git push --dry-run --recurse-submodule=on-demand" wasn't
"--dry-run" in the submodules.
* The output from "git worktree list" was made in readdir() order,
and was unstable.
* mergetool.<tool>.trustExitCode configuration variable did not apply
to built-in tools, but now it does.
* "git p4" LFS support was broken when LFS stores an empty blob.
* Fix a corner case in merge-recursive regression that crept in
during 2.10 development cycle.
* Update the error messages from the dumb-http client when it fails
to obtain loose objects; we used to give sensible error message
only upon 404 but we now forbid unexpected redirects that needs to
be reported with something sensible.
* When diff.renames configuration is on (and with Git 2.9 and later,
it is enabled by default, which made it worse), "git stash"
misbehaved if a file is removed and another file with a very
similar content is added.
* "git diff --no-index" did not take "--no-abbrev" option.
* "git difftool --dir-diff" had a minor regression when started from
a subdirectory, which has been fixed.
* "git commit --allow-empty --only" (no pathspec) with dirty index
ought to be an acceptable way to create a new commit that does not
change any paths, but it was forbidden, perhaps because nobody
needed it so far.
* A pathname that begins with "//" or "\\" on Windows is special but
path normalization logic was unaware of it.
* "git pull --rebase", when there is no new commits on our side since
we forked from the upstream, should be able to fast-forward without
invoking "git rebase", but it didn't.
* The way to specify hotkeys to "xxdiff" that is used by "git
mergetool" has been modernized to match recent versions of xxdiff.
* Unlike "git am --abort", "git cherry-pick --abort" moved HEAD back
to where cherry-pick started while picking multiple changes, when
the cherry-pick stopped to ask for help from the user, and the user
did "git reset --hard" to a different commit in order to re-attempt
the operation.
* Code cleanup in shallow boundary computation.
* A recent update to receive-pack to make it easier to drop garbage
objects made it clear that GIT_ALTERNATE_OBJECT_DIRECTORIES cannot
have a pathname with a colon in it (no surprise!), and this in turn
made it impossible to push into a repository at such a path. This
has been fixed by introducing a quoting mechanism used when
appending such a path to the colon-separated list.
* The function usage_msg_opt() has been updated to say "fatal:"
before the custom message programs give, when they want to die
with a message about wrong command line options followed by the
standard usage string.
* "git index-pack --stdin" needs an access to an existing repository,
but "git index-pack file.pack" to generate an .idx file that
corresponds to a packfile does not.
* Fix for NDEBUG builds.
* A lazy "git push" without refspec did not internally use a fully
specified refspec to perform 'current', 'simple', or 'upstream'
push, causing unnecessary "ambiguous ref" errors.
* "git p4" misbehaved when swapping a directory and a symbolic link.
* Even though an fix was attempted in Git 2.9.3 days, but running
"git difftool --dir-diff" from a subdirectory never worked. This
has been fixed.
* "git p4" that tracks multile p4 paths imported a single changelist
that touches files in these multiple paths as one commit, followed
by many empty commits. This has been fixed.
* A potential but unlikely buffer overflow in Windows port has been
fixed.
* When the http server gives an incomplete response to a smart-http
rpc call, it could lead to client waiting for a full response that
will never come. Teach the client side to notice this condition
and abort the transfer.
* Some platforms no longer understand "latin-1" that is still seen in
the wild in e-mail headers; replace them with "iso-8859-1" that is
more widely known when conversion fails from/to it.
* Update the procedure to generate "tags" for developer support.
* Update the definition of the MacOSX test environment used by
TravisCI.
* A few git-svn updates.
* Compression setting for producing packfiles were spread across
three codepaths, one of which did not honor any configuration.
Unify these so that all of them honor core.compression and
pack.compression variables the same way.
* "git fast-import" sometimes mishandled while rebalancing notes
tree, which has been fixed.
* Recent update to the default abbreviation length that auto-scales
lacked documentation update, which has been corrected.
* Leakage of lockfiles in the config subsystem has been fixed.
* It is natural that "git gc --auto" may not attempt to pack
everything into a single pack, and there is no point in warning
when the user has configured the system to use the pack bitmap,
leading to disabling further "gc".
* "git archive" did not read the standard configuration files, and
failed to notice a file that is marked as binary via the userdiff
driver configuration.
* "git blame --porcelain" misidentified the "previous" <commit, path>
pair (aka "source") when contents came from two or more files.
* "git rebase -i" with a recent update started showing an incorrect
count when squashing more than 10 commits.
* "git <cmd> @{push}" on a detached HEAD used to segfault; it has
been corrected to error out with a message.
* Tighten a test to avoid mistaking an extended ERE regexp engine as
a PRE regexp engine.
* Typing ^C to pager, which usually does not kill it, killed Git and
took the pager down as a collateral damage in certain process-tree
structure. This has been fixed.
---------------------------------------------
0.56 January 30, 2017
Removed all test files using 'scripts/modulemaker' as first step in
diagnosing problem reported in
https://rt.cpan.org/Ticket/Display.html?id=111637. No changes in
functionality.
* Use internal harfbuzz and graphite2
LibreOffice 5.3.0 requires harfbuzz with graphite2 support.
Enabling graphite2 in fonts/harfbuzz breaks graphics/librsvg, so
I cannot enable graphite2 in fonts/harfbuzz.
* Explicitly specify static libraries of harfbuzz and graphite2
with path to fix a linking of libvcllo.so
* Add some comments to patches
Changelog:
Highlights
LibreOffice 5.3 offers a number of interesting new features in
every area: a new cross-platform text layout engine that uses
HarfBuzz for consistent text layout on all platforms, with significant
advantages across languages and alphabets; a revised Help menu,
with new quick links to user guides and community support forums,
for an improved user experience; and better import/export filters
to new and legacy MS Office documents.
Writer now supports Table Styles, for applying formatting to a
table which is preserved when you make edits to it; a new Page Deck
in the sidebar lets the user quickly customise page settings without
having to go through a separate dialog box; and a new Go to Page
Box makes it possible to jump to another page in the document with
just a few keystrokes.
Calc provides a new set of default cell styles, with greater variety
and better names than in previous releases; in fresh installations,
"enable wildcards in formulas" is now the default option, rather
than regular expressions, to improve compatibility with other
spreadsheet software; and a new text entry box lets the user narrow
down the functions he is looking for, and simplifies the search
for the right one.
Impress now opens with a template selector, to get the user off to
a quick start; and a new Slide Properties Deck is now available in
the sidebar while in slide master mode.
libzmf is a library that parses the file format of Zoner Callisto/Draw
documents. Currently it only understands documents created by Zoner
Draw version 4 and 5.
Changelog:
http://www.oracle.com/technetwork/java/javase/8u121-relnotes-3315208.html
core-libs/javax.naming
Improved protection for JNDI remote class loading
Remote class loading via JNDI object factories stored in naming and directory services is disabled by default. To enable remote class loading by the RMI Registry or COS Naming service provider, set the following system property to the string "true", as appropriate:
com.sun.jndi.rmi.object.trustURLCodebase
com.sun.jndi.cosnaming.object.trustURLCodebase
JDK-8158997 (not public)
security-libs/java.security
jarsigner -verbose -verify should print the algorithms used to sign the jar
The jarsigner tool has been enhanced to show details of the algorithms and keys used to generate a signed JAR file and will also provide an indication if any of them are considered weak.
Specifically, when "jarsigner -verify -verbose filename.jar" is called, a separate section is printed out showing information of the signature and timestamp (if it exists) inside the signed JAR file, even if it is treated as unsigned for various reasons. If any algorithm or key used is considered weak, as specified in the Security property, jdk.jar.disabledAlgorithms, it will be labeled with "(weak)".
For example:
- Signed by "CN=weak_signer"
Digest algorithm: MD2 (weak)
Signature algorithm: MD2withRSA (weak), 512-bit key (weak)
Timestamped by "CN=strong_tsa" on Mon Sep 26 08:59:39 CST 2016
Timestamp digest algorithm: SHA-256
Timestamp signature algorithm: SHA256withRSA, 2048-bit key
See JDK-8163304
New Features
core-libs/java.io:serialization
Serialization Filter Configuration
Serialization Filtering introduces a new mechanism which allows incoming streams of object-serialization data to be filtered in order to improve both security and robustness. Every ObjectInputStream applies a filter, if configured, to the stream contents during deserialization. Filters are set using either a system property or a configured security property. The value of the "jdk.serialFilter" patterns are described in JEP 290 Serialization Filtering and in <JRE>/lib/security/java.security. Filter actions are logged to the 'java.io.serialization' logger, if enabled.
See JDK-8155760
core-libs/java.rmi
RMI Better constraint checking
RMI Registry and Distributed Garbage Collection use the mechanisms of JEP 290 Serialization Filtering to improve service robustness.
RMI Registry and DGC implement built-in white-list filters for the typical classes expected to be used with each service.
Additional filter patterns can be configured using either a system property or a security property. The "sun.rmi.registry.registryFilter" and "sun.rmi.transport.dgcFilter" property pattern syntax is described in JEP 290 and in <JRE>/lib/security/java.security.
JDK-8156802 (not public)
security-libs
Add mechanism to allow non-default root CAs to not be subject to algorithm restrictions
*New certpath constraint: jdkCA*
In the java.security file, an additional constraint named "jdkCA" is added to the jdk.certpath.disabledAlgorithms property. This constraint prohibits the specified algorithm only if the algorithm is used in a certificate chain that terminates at a marked trust anchor in the lib/security/cacerts keystore. If the jdkCA constraint is not set, then all chains using the specified algorithm are restricted. jdkCA may only be used once in a DisabledAlgorithm expression.
Example: To apply this constraint to SHA-1 certificates, include the following: SHA1 jdkCA
See JDK-8140422
Changes
tools/javadoc(tool)
New --allow-script-in-comments option for javadoc
The javadoc tool will now reject any occurrences of JavaScript code in the javadoc documentation comments and command-line options, unless the command-line option, --allow-script-in-comments is specified.
With the --allow-script-in-comments option, the javadoc tool will preserve JavaScript code in documentation comments and command-line options. An error will be given by the javadoc tool if JavaScript code is found and the command-line option is not set.
JDK-8138725 (not public)
security-libs/javax.xml.crypto
Increase the minimum key length to 1024 for XML Signatures
The secure validation mode of the XML Signature implementation has been enhanced to restrict RSA and DSA keys less than 1024 bits by default as they are no longer secure enough for digital signatures. Additionally, a new security property named jdk.xml.dsig.SecureValidationPolicy has been added to the java.security file and can be used to control the different restrictions enforced when the secure validation mode is enabled.
The secure validation mode is enabled either by setting the xml signature property org.jcp.xml.dsig.secureValidation to true with the javax.xml.crypto.XMLCryptoContext.setProperty method, or by running the code with a SecurityManager.
If an XML Signature is generated or validated with a weak RSA or DSA key, an XMLSignatureException will be thrown with the message, "RSA keys less than 1024 bits are forbidden when secure validation is enabled" or "DSA keys less than 1024 bits are forbidden when secure validation is enabled."
JDK-8140353 (not public)
docs/release_notes
Restrict certificates with DSA keys less than 1024 bits.
DSA keys less than 1024 bits are not strong enough and should be restricted in certification path building and validation. Accordingly, DSA keys less than 1024 bits have been deactivated by default by adding "DSA keySize < 1024" to the "jdk.certpath.disabledAlgorithms" security property. Applications can update this restriction in the security property ("jdk.certpath.disabledAlgorithms") and permit smaller key sizes if really needed (for example, "DSA keySize < 768").
JDK-8139565 (not public)
security-libs
More checks added to DER encoding parsing code
More checks are added to the DER encoding parsing code to catch various encoding errors. In addition, signatures which contain constructed inparsing. Note that signatures generated using JDK default providers are not affected by this change.
JDK-8168714 (not public)
core-libs/java.net
Additional access restrictions for URLClassLoader.newInstance
Class loaders created by the java.net.URLClasslasses from a list of given URLs. If the calling code does not have access to one or more of the URLs and the URL artifacts that can be accessed do not contain the required class, then a ClassNotFoundException, or similar, will be thrown. Previously, a Sege can be disabled by setting the jdk.net.URLClassPath.disableRestrictedPermissions system property.
JDK-8151934 (not public)
core-libs/java.util.logging
A new configurable property in logging.properties java.util.logging.FileHandler.maxLocks
A new "java.util.logging.FileHandler.maxLocks" configurable property is added to java.util.logging.FileHandler.
This new logging property can be defined in the logging configuration file and makes it possible to configure the maximum number of concurrent log file locks a FileHandler can handle. The default value is 100.
In a highly concurrent environment where multiple (more than 101) standalone client applications are using the JDK Logging API with FileHandler simultaneously, it may happen that the default limit of 100 is reached, resulting in a failure to acquire FileHandler file locks and causing an IO Exception to be thrown. In such a case, the new logging property can be used to increase the maximum number of locks before deploying the application.
If not overridden, the default value of maxLocks (100) remains unchanged. See java.util.logging.LogManager and java.util.logging.FileHandler API documentation for more details.
See JDK-8153955
Bug Fixes
The following are some of the notable bug fixes included in this release:
client-libs/javax.swing
Trackpad scrolling of text on OS X 10.12 Sierra is very fast
The MouseWheelEvent.getWheelRotation() method returned rounded native NSEvent deltaX/Y events on Mac OS X. The latest macOS Sierra 10.12 produces very small NSEvent deltaX/Y values so rounding and summing them leads to the huge value returned from the MouseWheelEvent.getWheelRotation(). The JDK-8166591 fix accumulates NSEvent deltaX/Y and the MouseWheelEvent.getWheelRotation() method returns non-zero values only when the accumulated value exceeds a threshold and zero value. This is compliant with the MouseWheelEvent.getWheelRotation() specification (https://docs.oracle.com/javase/8/docs/api/java/awt/event/MouseWheelEvent.html#getWheelRotation):
"Returns the number of "clicks" the mouse wheel was rotated, as an integer. A partial rotation may occur if the mouse supports a high-resolution wheel. In this case, the method returns zero until a full "click" has been accumulated."
For the precise wheel rotation values, use the MouseWheelEvent.getPreciseWheelRotation() method instead.
See JDK-8166591
This release also contains fixes for security vulnerabilities described in the Oracle Java SE Critical Patch Update Advisory. For a more complete list of the bug fixes included in this release, see the JDK 8u121 Bug Fixes page.
Known Issues
deploy/packager
javapackager and fx:deploy bundle the whole JDK instead of JRE
There is a known bug in the Java Packager for Mac where the entire JDK may be bundled with the application bundle resulting in an unusually large bundle. The work around is to use the bundler option -Bruntime option. For example: -Bruntime=JavaAppletPlugin.plugin sets where the JavaAppletPlugin.plugin for the desired JRE to bundle is located in the current directory.
See JDK-8166835
install/install
Java Installation will fail for non-admin users with UAC off
The Java installation on Windows will fail without warning or prompting, for non-admin users with User Access Control (UAC) disabled. The installer will leave a directory, jds<number>.tmp, in the %TEMP% directory.
JDK-8161460 (not public)
This module implements utility functions for expanding embedded
variables in a string. Variable references are embedded in strings in
a similar form to the Bourne shell, namely, in the form $NAME or
${NAME}. In the former case, the NAME must consist of a capital letter
or underscore, and may be followed by zero or more capital letters,
digits or underscores. In the latter case, the name can consist of any
characters, but will be terminated by the first close brace character
'}'.
This is a regularly-scheduled quarterly feature release.
1.1. commands
commands: config option to control bundle compression level
crecord: add an experimental option for space key to move cursor down
crecord: rewrite status line text (BC)
diff: add experimental support for more git-diff extended diff features
graft: support grafting changes to new file in renamed directory (issue5436)
help: show help for disabled extensions (issue5228)
help: update help for 'hg update' which was misleading (issue5427)
merge: fix crash on criss cross merge with dir move and delete (issue5020)
summary: add evolution "troubles" information to summary output
summary: use the same labels as log command in "parent: " line
templates: display evolution "troubles" in command line style
1.2. core
changelog: keep track of file end in appender (issue5444)
dispatch: stop supporting non-use of @command (API)
hook: do not redirect stdout/err/in to ui while running in-process hooks (BC)
httppeer: advertise and support application/mercurial-0.2
localrepo: experimental support for non-zlib revlog compression
manifest: add bundlemanifestlog support
manifest: add unionmanifestlog support
manifest: make revlog verification optional
patch: add experimental config knob for displaying the index header
patch: add similarity config knob in experimental section
patch: add label for coloring the index extended header
patch: add label for coloring the similarity extended header
profiling: make statprof the default profiler (BC)
profiling: use vendored statprof and upstream enhancements (BC)
revlog: REVIDX_EXTSTORED flag
revlog: add clone method
revlog: ensure that flags do not overflow 2 bytes
revlog: flag processor
revlog: inline start() and end() for perf reasons
revlog: make compressed size comparisons consistent
revlog: merge hash checking subfunctions
revlog: move decompress() from module to revlog class (API)
revlog: optimize _chunkraw when startrev==endrev
revlog: pass revlog flags to addrevision
revlog: reorder index accessors to match data structure order
revlog: use compression engine API for compression
revlog: use compression engine APIs for decompression
revset: add regular expression support to 'desc'
revset: make children() not look at p2 if null (issue5439)
run-tests: forward Python USER_BASE from site (issue5425)
server: move cmdutil.service() to new module (API)
templatekw: force noprefix=False to insure diffstat consistency (issue4755)
ui: check EOF of getpass() response read from command-server channel
ui: do not translate empty configsource() to 'none' (API)
ui: factor out ui.load() to create a ui without loading configs (API)
util: compression APIs to support revlog compression and decompression
util: declare wire protocol support of compression engines
wireproto: advertise supported media types and compression formats
wireproto: only advertise HTTP-specific capabilities to HTTP peers (BC)
wireproto: perform chunking and compression at protocol layer (API)
1.3. extensions
convert: add config option to control storing original revision
convert: add config option to copy extra keys from Git commits
convert: config option for git rename limit
convert: config option to control Git committer actions
rebase: calculate ancestors for --base separately (issue5420)
rebase: check for conflicts before continuing
rebase: fail-fast the pull if working dir is not clean (BC)
shelve: allow multiple shelves with --patch and --stat
shelve: choose a legal shelve name when no name is passed (issue5112)
shelve: make --keep option survive user intervention (issue5431)
shelve: make unshelve not crash when there are missing files (issue4176)
1.4. hgweb
hgweb: link to raw-file on annotation page (BC)
hgweb: make log streams compatible with command server
hgweb: restore ascending iteration on revs in filelog web command
hgweb: support Content Security Policy
1.5. chg
chg: send type information via S channel (BC)
chg: support long socket path
chgserver: make S channel support pager request
chgserver: override runcommand
1.6. Behavior Changes
chg: send type information via S channel (BC)
crecord: rewrite status line text (BC)
hgweb: link to raw-file on annotation page (BC)
hook: do not redirect stdout/err/in to ui while running in-process hooks (BC)
profiling: make statprof the default profiler (BC)
profiling: use vendored statprof and upstream enhancements (BC)
rebase: fail-fast the pull if working dir is not clean (BC)
wireproto: only advertise HTTP-specific capabilities to HTTP peers (BC)
1.7. Internal API Changes
bookmarks: make bookmarks.comparebookmarks accept binary nodes (API)
bookmarks: rename 'compare()' to 'comparebookmarks()' (API)
revlog: move decompress() from module to revlog class (API)
server: move cmdutil.service() to new module (API)
ui: do not translate empty configsource() to 'none' (API)
ui: factor out ui.load() to create a ui without loading configs (API)
util: remove compressors dict (API)
util: remove decompressors dict (API)
wireproto: perform chunking and compression at protocol layer (API)
dispatch: stop supporting non-use of @command (API)
-------------------------------------
(from RELEASE-NOTE, some 170 lines, sorry)
-----------------------------------------
E2fsprogs 1.43.4 (January 31, 2017)
===================================
Fix e2fsck to require that the system.data extended attribute is
always present even for files smaller than 60 bytes, to be consistent
with the kernel.
Fix a bug which was causing mke2fs -d and fuse2fs to improperly handle
Posix ACL's.
Fix a bug which could cause mke2fs -d to fail if there is an
zero-length file in source directory tree.
Clarify the default for the "proceed?" question printed by mke2fs and
tune2fs. (Addresses Debian Bug: #852727)
Debugfs will now display project quota information.
Debugfs's do_set_xattr now uses C strings to parse extended attribute
values, and will print the extended attributes using either C strings
or hex bytes when using debugfs's do_get_xattr command. It will now
allow developers to see the contents of the system.data extended
attribute.
Fix a bug in mke2fs where I/O errors weren't getting properly reported
to the user.
Fix multiblock writes in the unaligned Direct I/O fallback code.
(Which is rarely needed on Linux systems, but which is required on
Freebsd systems.)
Make sure the default mke2fs.conf file includes the uninit_bg feature
flag. (Which was accidentally dropped in v1.43).
Fix a bug in resize2fs when operating on very large file systems which
have a block size different from the VM page size.
If the reported device size is absurdly large, mke2fs will now report
an error instead looping forever or crashing.
Fix various Coverity warnings and other memory leaks in fuse2fs and
extended attribute manipulation functions.
Replace a test file but which had a "non-commercial use-only"
copyright permission file with a newer version from the Cyrus imapd
package which now has a 4-clause BSD license, which was making some
lawyers nervous, even though the test file in question was only used
in lib/et's regression testing and was never included in any compiled
binary. (Addresses Debian Bug: #840733)
Stop installing mkfs.ext4dev and fsck.ext4dev
Update Chinese, Czech, Polish, Serbian, and Spanish translations and
add the Finnish and Malay translation. (Addresses-Debian-Bug: #774379)
Update various man pages (Addresses-Debian-Bug: #852726)
Programming notes
-----------------
Fix more FreeBSD-11 compatibility bugs, including some unmasked by
FreeBSD 11-rc2.
Fix the Mac build.
Fix build failure on RHEL 5.x systems caused by an old version of
libmagic.
Fix a number of bugs reported by ASAN that can cause some (mostly
harmless) memory dereferences beyond allocated memory.
E2fsprogs 1.43.3 (September 4, 2016)
====================================
Fix e2fsck's handling of timestamps on 32-bit systems.
E2fsck will now check, and if necessary repair the extra isize fields
in the inode and superblock.
Fix crashes on architectures such as sparc64 that are sensitive to
unaligned pointer derferences in the journal recovery code when
journal checksums are enabled.
Programming notes
-----------------
Support reproducible builds by not capturing the build directory into
the mk_cmds and compile_et scripts. Also fix debian build rules to
ensure build reproducibility.
Fix debian build rules to ensure build reproducibility and to avoid
hiding the linker flags for e2fsck.static so the build hardening log
scanner can properly audit the build.
Fix compatibility with FreeBSD's pmake and teach the configure script
to force the creation of pmake-compatible Makefiles if the
FORCE_NATIVE_MAKE environment variable is set to a non-empty value.
E2fsprogs 1.43.2 (September 1, 2016)
====================================
Fix resize2fs so it will not crash if there is an extended attribute
block but it doesn't need to migate any blocks during an off-line
resize
Fix a crash when mke2fs or debugfs tries to copy in a directory
hierarchy containing an empty directory
Mke2fs will now use a larger journal by default for filesystems
greater than 128 GB. (1GB instead of 128 MB.)
Fix an alignment bug in e2fsck which caused sparc64 architectures to
crash when replaying the journal on file systems with a 64-bit block
number.
Clarify the message printed by tune2fs message when the user needs to
run e2fsck so it's clear that the -f flag to e2fsck is needed to
force a full e2fsck scan. (Addresses Debian Bug: #828022)
Fix a bug in e2fsck caused by a power failure during e2fsck's journal
replay could leave the file system in a state where if the file system
is mounted without doing a full e2fsck scan, the file system could get
corrupted
Fix the logic in e2fsck which decides when to repair legacy negative
timestamp encodings.
Add a command to debugfs to copy the inode structure from one inode to
another.
Fix a typo in debugfs's stat command when printing out the dtime field
on file systems with an extended timestamp.
Fix big endian bugs in the e2undo program. (Addresses Red Hat Bug
#1344636)
Debugfs's logdump can now properly handle journals larger than 2GB.
Avoid installing the man page for fuse2fs if it has not been built.
Update the Catalan, Chinese, Danish, Dutch, French, German, Polish,
Swedish, Ukrainian translations and added new translations for
Hugarian and Serbian.
Programming notes
-----------------
Fix portability problems in fuse2fs. Previously it wouldn't build on
systems with older glibc versions where clock_gettime() is only
available in the librt library, and if libintl is not bundled into the
C library.
Remove complicated logic which caused a static code analyzer to flag a
false positive. (A static code analyzer also found a valid bug in
deciding when to repair a legacy negative timestamp encoding, so
eliminating false positives is important.)
Fixed a bug where the ext2fs library cloud provoke when a
extfs2_zero_blocks() is used (via fallocation, initializing a file
system, uninitialized uninitialized inode table blocks) after a
different file system which also used ext2fs_zero_blocks().
Enable the unix_io manager in the ext2fs library so it can accept the
use of a file descriptor. This is helpful in cases where the file
descriptor comes from temporary file created using O_TMPFILE, or
passed in from a unix domain socket.
Fix a Windows64 portability bug.
