libappfuse: use an explicit buffer size

This patch makes lookup_name use an explicit buffer size, rather than
"whatever the union happens to give me." I don't know if it's the
correct size, but having a 0-length array in this sort of configuration
seems fragile, and will be a compilation error when
https://android-review.googlesource.com/#/c/platform/bionic/+/449363/
goes in.

Bug: 12231437
Test: Builds with the mentioned patch applied to Bionic
Change-Id: I5793c906b7c2417e9a58aa907ef11c282027edb2
This commit is contained in:
George Burgess IV 2017-08-02 14:00:53 -07:00
parent ceb7814c86
commit 87533581be
1 changed files with 1 additions and 1 deletions

View File

@ -54,7 +54,7 @@ struct FuseRequest : public FuseMessage<FuseRequest> {
// for FUSE_READ
fuse_read_in read_in;
// for FUSE_LOOKUP
char lookup_name[0];
char lookup_name[kFuseMaxWrite];
};
void Reset(uint32_t data_length, uint32_t opcode, uint64_t unique);
};