| commit | f7bd5bba1b8ce7200600bacee024bce525083f60 | |
| author | Alberto Garcia <berto@igalia.com> | |
| Thu, 3 Sep 2020 16:37:48 +0000 (3 18:37 +0200) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Tue, 15 Sep 2020 09:05:13 +0000 (15 11:05 +0200) | ||
| tree | ab7492da4c45be407d0f1947ffdc45b5880af29e | treesnapshot (tar.gz zip) |
| parent | 184581fa4d8a83c601d967971f8460faeeb742ac | commitdiff |
qcow2: Don't check nb_clusters when removing l2meta from the list
In the past, when a new cluster was allocated the l2meta structure was
a variable in the stack so it was necessary to have a way to tell
whether it had been initialized and contained valid data or not. The
nb_clusters field was used for this purpose. Since commit f50f88b9fe
this is no longer the case, l2meta (nowadays a pointer to a list) is
only allocated when needed and nb_clusters is guaranteed to be > 0 so
this check is unnecessary.
Signed-off-by: Alberto Garcia <berto@igalia.com>
Message-Id: <ab0b67c29c7ba26e598db35f12aa5ab5982539c1.1599150873.git.berto@igalia.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
In the past, when a new cluster was allocated the l2meta structure was
a variable in the stack so it was necessary to have a way to tell
whether it had been initialized and contained valid data or not. The
nb_clusters field was used for this purpose. Since commit f50f88b9fe
this is no longer the case, l2meta (nowadays a pointer to a list) is
only allocated when needed and nb_clusters is guaranteed to be > 0 so
this check is unnecessary.
Signed-off-by: Alberto Garcia <berto@igalia.com>
Message-Id: <ab0b67c29c7ba26e598db35f12aa5ab5982539c1.1599150873.git.berto@igalia.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
| block/qcow2.c | diffblobblamehistory |