zero-filling fuse_session structure if session is not yet initialized #2740
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to fix msan issues like this:
https://github-actions-s3.website.nemax.nebius.cloud/ydb-platform/nbs/Nightly-build-(msan)/12404651235/1/nebius-x86-64-msan/test_data/actions-runner/_work/nbs/nbs/cloud/filestore/tests/fio_index/qemu-kikimr-multishard-nemesis-test/test-results/py3test/chunk4/testing_out_stuff/filestore-vhost.err
it's hard to say how exactly we run into such a situation
most probably se->bufsize actually is initialized but in a way that's not seen by msan
it's surely initialized in virtiofsd/fuse_lowlevel.c::do_init which, together with fuse_session_setparams, should cover all code paths