diff options
author | Eric Blake <eblake@redhat.com> | 2020-06-08 13:26:38 -0500 |
---|---|---|
committer | Eric Blake <eblake@redhat.com> | 2020-06-10 12:58:59 -0500 |
commit | 5c86bdf1208916ece0b87e1151c9b48ee54faa3e (patch) | |
tree | aa6dd351f3173b3c5136a69f44b2d1c4688a55b4 /default-configs/microblazeel-softmmu.mak | |
parent | 5c4fe018c025740fef4a0a4421e8162db0c3eefd (diff) |
block: Call attention to truncation of long NBD exports
Commit 93676c88 relaxed our NBD client code to request export names up
to the NBD protocol maximum of 4096 bytes without NUL terminator, even
though the block layer can't store anything longer than 4096 bytes
including NUL terminator for display to the user. Since this means
there are some export names where we have to truncate things, we can
at least try to make the truncation a bit more obvious for the user.
Note that in spite of the truncated display name, we can still
communicate with an NBD server using such a long export name; this was
deemed nicer than refusing to even connect to such a server (since the
server may not be under our control, and since determining our actual
length limits gets tricky when nbd://host:port/export and
nbd+unix:///export?socket=/path are themselves variable-length
expansions beyond the export name but count towards the block layer
name length).
Reported-by: Xueqiang Wei <xuwei@redhat.com>
Fixes: https://bugzilla.redhat.com/1843684
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-Id: <20200610163741.3745251-3-eblake@redhat.com>
Diffstat (limited to 'default-configs/microblazeel-softmmu.mak')
0 files changed, 0 insertions, 0 deletions