Repository navigation
rrsync: add -log to record every transfer #1153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
initd-it
wants to merge
5
commits into
RsyncProject:master
Choose a base branch
from
initd-it:rrsync-log
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+358
−17
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e2121aa
rrsync: add -log to record every transfer
initd-it d3f7bd9
rrsync: refuse a -log FILE inside DIR
initd-it 6f36e15
rrsync: resolve the -log FILE and refuse it when DIR is /
initd-it 3cd6a4b
rrsync: resolve -log FILE per component and open it before rsync runs
initd-it 7d19e3d
rrsync: fix forced transfer logging
steadytao File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding enforce_root introduces a third mechanism controlling root confinement alongside files_from (filesfrom_owner_walk_active()) and operator_path_resolve. Having three overlapping flags makes the confinement logic inconsistent and harder to reason about or debug later.
Instead of adding a new parameter to ona_open(), it would be cleaner to handle this inside open_log_file() by temporarily setting confine_root = NULL (or files_from = NULL) as exception only for log-files when used with files-from (filesfrom_owner_walk_active returns 1) , then restoring them right after ( same as operator_path_resolve style) .
Note that zeroing confine_root will cause pseudo-paths (Test 2) to fail, which is actually expected. I was already planning to open a separate PR to allow trusted pseudo-paths under --confine-root when operator_path_resolve == 0 (for --log-file, --files-from, etc.), since rejecting them unconditionally on if (confine_root) is a separate bug we need to fix anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@steadytao the pseudo-paths fix are covered here #1169