windows: fix some crashes, change handling of invalid paths; lex: add better error detection; accurate: fix out of bounds writes#1793
Merged
BareosBot merged 27 commits intobareos:masterfrom Jun 20, 2024
Conversation
9708140 to
5b40ea3
Compare
219655b to
9c03a19
Compare
Contributor
|
This has fixed issues encountered in support ticket 75261. |
5d68c76 to
0799099
Compare
sebsura
commented
May 16, 2024
sebsura
commented
May 16, 2024
0799099 to
9859d90
Compare
pstorz
previously requested changes
May 28, 2024
Member
pstorz
left a comment
There was a problem hiding this comment.
Please see comments,
The accurate-lmdb tests still fail as already talked about.
...s/source/manually_added_config_directive_descriptions/fd-client-MaximumWorkersPerJob.rst.inc
Outdated
Show resolved
Hide resolved
Our win32-cross toolchain does not handle thread_local correctly. This can load to crashes because it may free the storage before destructing the object inside the storage. See here for reference: https://sourceforge.net/p/mingw-w64/bugs/727/ This is extremely easy to reproduce if run in a debugger (gdb in my case). In the wild this does not happen 100%. As such thread_local was replaced by a manually managed pthread_key.
In the trace of one customer we saw the fd try to add a single file multiple times! This is a work around for that.
62672c2 to
79e8c54
Compare
pstorz
approved these changes
Jun 18, 2024
Add simple tests that check that accurate does not do weird things even if the database has inconsistencies.
Adds a systemtest that checks some parser behaviours. This needs to be a systemtest as some parser errors lead to aborts/exits and cannot be run in unit tests as such.
Also print how many files are expected to be sent
Since we are supposed to send pktsiz many bytes, we should also print that number in case we did not send everything, otherwise we may run into situations where message_length == sent bytes != pktsiz (which happened at a customer) and the message does not make sense anymore.
79e8c54 to
b0b20b8
Compare
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thank you for contributing to the Bareos Project!
This PR contains the following changes:
/usr/bin/sendmailon windowsSHGetFolderPathbySHGetKnownFolderPathPlease check
If you have any questions or problems, please give a comment in the PR.
Helpful documentation and best practices
Checklist for the reviewer of the PR (will be processed by the Bareos team)
Make sure you check/merge the PR using
devtools/pr-toolto have some simple automated checks run and a proper changelog record added.General
Source code quality
Tests