Prevent faulty logs from nested setupFS calls #15540
Merged
Conversation
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
Signed-off-by: Joas Schilling <[email protected]>
rullzer
approved these changes
May 21, 2019
Member
rullzer
left a comment
rullzer
left a comment
There was a problem hiding this comment.
Makes sense...
@icewind1991 please also have a look
skjnldsv
approved these changes
Jun 21, 2019
Member
Author
|
/backport to stable16 |
Member
Author
|
/backport to stable15 |
Member
Author
|
/backport to stable14 |
nickvergessen
deleted the
bugfix/noid/prevent-faulty-logs-from-nested-setupFS-calls
branch
|
backport to stable16 in #16029 |
|
backport to stable15 in #16030 |
|
backport to stable14 in #16031 |
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.
Fix nextcloud/ransomware_protection#46
The question is whether nested setupFS calls should even happen, but I cant judge that.
cc @Schmuuu