Re: [PATCH 03/17] qcow2: Avoid feature name extension on small cluster size

2020-02-09 Thread Alberto Garcia
On Fri 31 Jan 2020 06:44:22 PM CET, Eric Blake wrote: > As the feature name table can be quite large (over 9k if all 64 bits > of all three feature fields have names; a mere 8 features leaves only > 8 bytes for a backing file name in a 512-byte cluster), it is unwise > to emit this optional header

Re: [PATCH 03/17] qcow2: Avoid feature name extension on small cluster size

2020-02-04 Thread Vladimir Sementsov-Ogievskiy
31.01.2020 20:44, Eric Blake wrote: As the feature name table can be quite large (over 9k if all 64 bits of all three feature fields have names; a mere 8 features leaves only 8 bytes for a backing file name in a 512-byte cluster), it is unwise to emit this optional header in images with small clu

[PATCH 03/17] qcow2: Avoid feature name extension on small cluster size

2020-01-31 Thread Eric Blake
As the feature name table can be quite large (over 9k if all 64 bits of all three feature fields have names; a mere 8 features leaves only 8 bytes for a backing file name in a 512-byte cluster), it is unwise to emit this optional header in images with small cluster sizes. Update iotest 036 to skip